Description of problem: Upgrade doc, rhn-satellite-5-upgrade-scenario-1a.txt is missing option to rhn-satellite-activate, --ignore-version-mismatch. This is already documented in rhn-satellite-5-upgrade-scenario-1b.txt Version-Release number of selected component (if applicable): # rpm -q rhn-upgrade rhn-upgrade-5.3.0.16-1.el4sat Actual results: 12. Activate the RHN Satellite: If this is a connected RHN Satellite (i.e., not disconnected): o If the new system is not yet registered to RHN, register it with the rhn_register or rhnreg_ks commands. o Run: rhn-satellite-activate --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> If disconnected, run: rhn-satellite-activate --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> \ --disconnected Expected results: 12. Activate the RHN Satellite: If this is a connected RHN Satellite (i.e., not disconnected): o If the new system is not yet registered to RHN, register it with the rhn_register or rhnreg_ks commands. o Run: rhn-satellite-activate --ignore-version-mismatch --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> If disconnected, run: rhn-satellite-activate --ignore-version-mismatch --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> \ --disconnected
satellite.git, SATELLITE-5.3: 15feb11c8ae2e1ce23f499174eb0dffdfeeec87a
rhn-upgrade-5.3.0.17-1
VERIFIED rpm -q rhn-upgrade rhn-upgrade-5.3.0.20-1.el4sat
12. Activate the RHN Satellite: If this is a connected RHN Satellite (i.e., not disconnected): o If the new system is not yet registered to RHN, register it with the rhn_register or rhnreg_ks commands. o Run: rhn-satellite-activate --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> \ --ignore-version-mismatch If disconnected, run: rhn-satellite-activate --rhn-cert <ABSOLUTE PATH TO *NEW* RHN CERT> \ --disconnected --ignore-version-mismatch verfied in stage
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-1235.html