[Spacewalk-list] Current packages in 1.6-nightly repo breaks Spacewalk

[Jan Pazdziora]

On Mon, Oct 17, 2011 at 12:55:16PM -0400, Scott Worthington wrote:
> Hello, the current packages in 1.6-nightly (2011-10-17) breaks
> Spacewalk due to a Postgresql table column not existing.
> 
> >Caused by: org.postgresql.util.PSQLException: ERROR: column networks0_.ip6addr does not exist Position: 168
> 
> This is Spacewalk 1.6-nightly on CentOS 6.0 x86_64:
> 
> The nightlys version updates had versions of 1.6.31-1.el6.noarch.  The
> spacewalk-schema file had version 1.6.21-1.el6.noarch.
> 
> I have run spacewalk-schema-upgrade:
> 
> # spacewalk-schema-upgrade
> Schema upgrade: [spacewalk-schema-1.6.19-1.el6] ->
> [spacewalk-schema-1.6.21-1.el6]
> Searching for upgrade path: [spacewalk-schema-1.6.19-1] ->
> [spacewalk-schema-1.6.21-1]
> Searching for upgrade path: [spacewalk-schema-1.6.19] ->
> [spacewalk-schema-1.6.21]
> Your database schema already matches the schema package version
> [spacewalk-schema-1.6].

The issue is -- we do not support rolling upgrades of Spacewalk schema
in nightly. The spacewalk-schema-upgrade tells you that you are on the
1.6 version because there is lower-granularity upgrade path, say from
spacewalk-schema-1.6.19 to spacewalk-schema-1.6.21.

You might want to pick the rpm for 1.6.19 and 1.6.21 and diff their
content and apply the changes manually.

Or just rerun spacewalk-schema, clear the database schema and start
with fresh one.

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat