[Spacewalk-list] Spacewalk Upgrade Issue

[Jan Pazdziora]

On Fri, Oct 25, 2013 at 03:16:18PM +0200, Jonathan Hoser wrote:
> 
> when upgrading from sw1.8 to sw2.0,
> did you actually go through 1.9?
> (you only stated you followed the todos from howtoupgrade19 -- which
> only does the upgrade things from sw1.9 to sw2.0)
> 
> as such, your db-scheme is probably missing some columns added in the
> 1.9 upgrade:
> 
> >[Thu Oct 24 08:20:32 2013] [error] ProgrammingError: column "org_id" does not exist
> (^^ taken from the logs you send)
> 
> So, give it another go, but FIRST upgrade to 1.9 and then do the upgrade to 2.0.

Nope.

Spacewalk schema upgrades are specifically written in such a way that
if spacewalk-schema-upgrade passes, upgrades across all versions were
done. So if you have Spacewalk 1.5 and run spacewalk-schema-upgrade
while having 2.0 installed, it will list that it will go 1.5 -> 1.6 ->
1.7 -> 1.8 -> 1.9 -> 2.0 and it will do all those steps.

Typically, even the instructions at the latest current

	https://fedorahosted.org/spacewalk/wiki/HowToUpgrade

can be used to skip multiple versions (thou it is only tested going
from the previous version), even if for non-schema things, there
might be some additional steps that you need to do, so it's better
to at least check all the previous HowToUpgrade* documents leading
to the current version to see if something more needs to be done.

But schema, that will always do all the needed steps for you, in one
run.

What will *not* work thou is if you try to upgrade from Spacewalk
nightly. Spacewalk nightly is non-released snapshot, not having all
the changes that the release will have, and when you upgrade from 1.8
nightly (like the OP did), spacewalk-schema-upgrade will assume it is
upgrading from released 1.8 and it will skip all the needed steps
going from the unreleased snapshot to 1.8 proper.

That's why that column org_id is missing in this case. Without
manually inspecting all changes that went to the Spacewalk between
that nightly snapshot and 1.8 and re-running (manually) all the
needed schema upgrade steps, this installation is not upgradable.

-- 
Jan Pazdziora
Principal Software Engineer, Identity Management Engineering, Red Hat