Recovering from failed/partially applied upgrade

 ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

Is this it?

1 Like

:+1:

so replace #version: tests-passed

With version: cd7ce52138bed391d5efc56366e7a6517a6079e7

Then /var/discourse/launcher rebuild app

1 Like

Just making sure this is correct before i rebuild

  ## Which Git revision should this container use? (default: tests-passed)
  version: cd7ce52138bed391d5efc56366e7a6517a6079e7

do i have to indent it again?

(beware of the indentation)

Now the code looks like this

## Which Git revision should this container use? (default: tests-passed)
   version: cd7ce52138bed391d5efc56366e7a6517a6079e7

Rebuild?

1 Like

Nope first one is good

thanks, Ben

Will rebuild now

Should be aligned with the #

1 Like
## Which Git revision should this container use? (default: tests-passed)
version: cd7ce52138bed391d5efc56366e7a6517a6079e7
1 Like

Like your first one:

1 Like

Ben, It worked! :grin:

Thank you so much for your time & effort in assisting me!

(please PM me so i can send you some coffee or beer money)

2 Likes

The question is whether now that you’ve gotten there you can now upgrade to latest…

1 Like

Great! But wait😅, you’re only halfway through, now you have to edit the app.yml again to version: tests-passed (and/or comment the line)

1 Like

Ok, I’ll sit back down again :rofl:

So add this back to where it was

#version: tests-passed
## Which Git revision should this container use? (default: tests-passed)
#version: tests-passed

Does that look correct to you? Then save?

1 Like

So done that and rebuilt.

Still saying up to date.

Maybe ive put the # in the wrong place, will try again

1 Like

I think you should have
Version: 2.9.0.beta3
(6555f0c11b )

And if so

We Did It Win GIF by HBO Max

2 Likes

2.9.0.beta3

(6555f0c11b)

Funny Thank You GIF by MOODMAN

(please do PM me where i can send you some :beers: money)

2 Likes

Nice work, @Benjamin_D! You rock. That’s great problem solving and great tutelage! You saved the day on this one. :clap: :tada:

4 Likes

Hopefully this should be properly resolved in the next release? DuplicateColumn and multisite:migrate failed - #7 by martin

Well, it appears not to be on the site I’m working on now. :crying_cat_face:

I added some comments at FIX: Check if bookmarkable column exists before adding by martin-brennan · Pull Request #16497 · discourse/discourse · GitHub
though I think it’s some other migration that’s to blame. It seems that it’s trying to populate the fields twice, but I’m not entirely clear.