Bug 480382

Summary: Re-enable Schema Upgrades in Satellite 5.3 ISOs
Product: Red Hat Satellite 5 Reporter: Devan Goodwin <dgoodwin>
Component: UpgradesAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED CURRENTRELEASE QA Contact: Steve Salevan <ssalevan>
Severity: medium Docs Contact:
Priority: high    
Version: 530CC: mmraka, mzazrivec
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sat530 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-10 18:53:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 463876    

Description Devan Goodwin 2009-01-16 19:39:31 UTC 
After transitioning the satellite-schema content from svn RELEASE-5.3 branch into new Satellite git, the upgrade scripts there will not build properly and I had to disable them. I'm not fully clear on how the whole upgrade process hangs together so will need someone familiar with it to take a look and get it into a state they're happy with for the long term.

Problem appears to be related to the use of symlinks for the upgrade script directories, which the build tools then try to convert to a patch on top of Spacewalk schema and this process fails.

This content is currently not packaged in the rpms and will need to be re-enabled.
Comment 1 Milan Zázrivec 2009-01-20 19:07:51 UTC 
*** Bug 476015 has been marked as a duplicate of this bug. ***
Comment 2 Milan Zázrivec 2009-01-20 19:18:05 UTC 
Fixed in satellite.git (SATELLITE-5.3 branch):

0e0de392b331184d08cc639bc23341c4590312c0
f8d96aa5fb4eba9630ac5888e2532d4fc4d38f2e
c677ce711a7df6cf87ef819cf925a63d38563294
146a5a398a050f35c55f64b16c9c91b2f0422909
f81c11e828ecf5fa35a1a897e45135d19ff1726c
37b200c8feaad11b3d18fe4f3ac28e1388fb2441
729cc1d39371a95f47aad4584656fa72a7f8081d
0e967dd743f937e1f9d0e39a98b044ed5efd0d4b

Tagged satellite-schema-5.3.0.5-1-sat
Built satellite-schema-5.3.0.5-1.el5sat & satellite-schema-5.3.0.5-1.el4sat
Comment 3 Milan Zázrivec 2009-01-20 19:38:33 UTC 
(In reply to comment #2)
> Tagged satellite-schema-5.3.0.5-1-sat
> Built satellite-schema-5.3.0.5-1.el5sat & satellite-schema-5.3.0.5-1.el4sat

Correct package versions are satellite-schema-5.3.0.6-1.el5sat
and satellite-schema-5.3.0.6-1.el4sat.
Comment 4 Steve Salevan 2009-04-08 17:33:38 UTC 
satellite-schema packages present and schema-upgrade directories present in latest 530 builds.  Moving to VERIFIED, tested on 530-re20090403.2
Comment 5 Michael Mráka 2009-08-07 09:12:22 UTC 
Verified in stage -> RELEASE_PENDING.

# rpm -qa *schema
spacewalk-schema-0.5.20-19.el4sat
satellite-schema-5.3.0.23-1.el4sat
# rpm -qla *schema | grep satellite-schema-5.3 | wc -l
13
Comment 6 Brandon Perkins 2009-09-10 18:53:50 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html