[Spacewalk-list] 1.6 to 1.7 upgrade bug 869985 reappeared?

[Boyd, Robert]

It would be extremely helpful to update the Wiki pages on upgrades to indicate the maximum jumps which will work. 

In other words -- on the V2.0 page indicate the oldest version that can be directly upgraded to 2.0.  For each release this would be very helpful.   Otherwise it would be normal to assume that one must do the intervening steps.   

I mistakenly went through all of the intervening steps to go from 1.7 to 2.0 -- I would have saved a lot of time if I had known I could go directly.

Robert

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Milan Zazrivec
Sent: Tuesday, August 13, 2013 5:16 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] 1.6 to 1.7 upgrade bug 869985 reappeared?

> If I understand you correct you are saying I can upgrade from 1.6 
> directly to 1.8? I thought it was required to do a step by step 
> upgrade. My objective is to get all the way to 2.0.

Yes, you can upgrade directly from 1.6 to 2.0. There's no need to do the particular steps. If you encounter any problems during the upgrade, feel free to ask here, I'll try to help if I can.

-MZ

> ________________________________________
> From: spacewalk-list-bounces at redhat.com 
> [spacewalk-list-bounces at redhat.com]
> on behalf of Milan Zazrivec [mzazrivec at redhat.com] Sent: Monday, 
> August 12, 2013 9:56 AM
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] 1.6 to 1.7 upgrade bug 869985 reappeared?
> 
> > I am attempting to upgrade from 1.6 to 1.7 and have encountered the
> > following:
> > 
> > 'SPACEWALK-SCHEMA-1.6-TO-SPACEWALK-SCHEMA-1.7/007-RHNPACKAGEGROUP-TR
> > IM.SQ
> > --------------------------------------------------------------------
> > ----- 
> > spacewalk-schema-1.6-to-spacewalk-schema-1.7/007-rhnPackageGroup-tri
> > m.sql
> > 
> > 
> > 77722 rows updated.
> > 
> > update rhnpackagegroup set name = substr(name, 1, length(name)-1)
> > *
> > ERROR at line 1:
> > ORA-00001: unique constraint (SPACEWALK.RHN_PACKAGE_GROUP_NAME_UQ)
> > violated
> > 
> > 
> > This appears to be a bug listed as fixed.
> > https://bugzilla.redhat.com/show_bug.cgi?id=869985
> > 
> > Presuming it is the same issue clearly its not fixed or the repo has 
> > somehow reverted back which seems very unlikely. I am using
> > spacewalk-repo-1.7-5.el5 pulled from 
> > http://yum.spacewalkproject.org/1.7/RHEL/5/x86_64/. Following the 
> > directions at https://fedorahosted.org/spacewalk/wiki/HowToUpgrade17.
> 
> Yes, this bug was fixed for Spacewalk 1.8, i.e. you would not hit this 
> problem when upgrading from any version to Spacewalk 1.8. The problem 
> has not been backported to Spacewalk 1.7 packages, i.e. you either can 
> upgrade to something later or apply that fix manually.
> 
> -Milan Zázrivec
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list