Description of problem:
When upgrading a 2.0 system to 2.1 that has been registered with RHN, the upgrade step 'begin' will never succeed.
In the begin step, it first checks to ensure the 2.0 channels are enabled, then proceeds to enable the 2.1 channels. However, it cannot enable the 2.1 channel itself and requires manual intervention. After the 2.1 channels are enabled manually and the 2.0 channels disabled, the ose-upgrade begin step then fails because the 2.0 channels are disabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a 2.0 system with RHN
2. Being the upgrade process by `yum updating`, then running `ose-upgrade begin`
Will complain that 2.1 repos need to be enabled manually. After enabling and running the step again, it complains that the 2.0 repositories are not enabled
Enables 2.1 repositories itself, or at least does not fail the check after the 2.1 repositories are enabled.
Install the Openshift according to the pad, then run the following three scenarios.
Scenario 1. run the 'ose-upgrade begin' without $RHN_USER or $RHN_PASSWD
/usr/lib/ruby/site_ruby/1.8/ose-upgrade/host/upgrades/3/rhn/02-new-channels had errors:
$RHN_USER and $RHN_PASS must be defined
--END /usr/lib/ruby/site_ruby/1.8/ose-upgrade/host/upgrades/3/rhn/02-new-channels OUTPUT--
INFO: Setting host step 'begin' status to FAILED
Scenario 2. run the 'ose-upgrade begin' with wrong $RHN_USER or $RHN_PASSWD
Invalid username/password combination
Error Class Code: 2
Error Class Info:
Invalid username and password combination.
If you are using email address as a login, try using your associated
login name instead.
Scenario 3. run the 'ose-upgrade begin' with correct $RHN_USER and $RHN_PASSWD
INFO: Setting host step 'begin' status to COMPLETE
INFO: To continue the upgrade, install a specific upgrade package.
You appear to have an OpenShift Enterprise broker installed;
please install the broker upgrade package to proceed with this upgrade.
# yum install openshift-enterprise-upgrade-broker
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.