Recovering from failed/partially applied upgrade

[pfaffman (Jay Pfaffman)]

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

[Benjamin_D (Benjamin Decotte)]

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)

[Nick_Tomlinson]

Ok, I’ll sit back down again

So add this back to where it was

#version: tests-passed

[Nick_Tomlinson]

@Benjamin_D

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

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

Does that look correct to you? Then save?

[Nick_Tomlinson]

So done that and rebuilt.

Still saying up to date.

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

[Benjamin_D (Benjamin Decotte)]

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

And if so

[Nick_Tomlinson]

2.9.0.beta3

(6555f0c11b)

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

[pfaffman (Jay Pfaffman)]

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

[luxaritas (Jonathan Romano)]

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

[pfaffman (Jay Pfaffman)]

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

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.