Description of problem: Currently if '/usr/bin/oo-admin-yum-validator --oo-version 2.1 --fix-all' is run it will not subscribe a system to the 2.1 channels but instead will report the manual steps required. It is important to note that once the channels are manually subscribed running the command again will set the priorities and excludes as expected.
This is most often noticed on an OpenShift Enterprise 2.0 installation from RHN Classic. When 'ose-upgrade begin' is run to start the upgrade process to 2.1 this command will fail and halt the upgrade until the manual steps are run.
This isn't a bug; oo-admin-yum-validator guarantees appropriate priorities for the repos and make certain that the needed *subscribed* repos/channels are enabled, but it is up to the user (or the ose-upgrade tool) to actually subscribe the appropriate repos/channels. I'm not certain if ose-upgrade still exhibits the described behavior; I'll try to test that today.