Red Hat Bugzilla – Bug 809496
Release version: drop-down remains disabled after subscribing to RHEL
Last modified: 2012-06-20 11:12:13 EDT
Created attachment 574878 [details]
The Release version drop-down list in GUI should match the CLI release --list
Description of problem:
After subscribing to the RHEL subscription, the new Release version setting in the System Preferences dialog remains disabled. See attached screenshot.
Version-Release number of selected component (if applicable):
[root@jsefler-r63-workstation ~]# rpm -q subscription-manager-gnome
Steps to Reproduce:
1. Using the GUI and the stage environment, register as stage_test_12 (if on server) or stage_test_27 (if on workstation) and subscribe to the RHEL subscription.
2. on the CLI run...
[root@jsefler-r63-workstation ~]# subscription-manager release --list
3. In the GUI, click the toollbar button for System Preferences and the Release version dropdown menu should list the same values as the CLI, but it remains disabled.
I think this is an artifact of stage not supporting releasever yet. We don't
enable the dropdown if we can't get/set releaseVer, even though we
could populate the list from the CDN.
Look for warnings like:
2012-04-03 12:25:47,892 [WARNING] @preferences.py:99 - Disabling release version dropdown, server does not support release versions.
2012-04-03 12:25:47,893 [WARNING] @preferences.py:78 - Disabling service level dropdown, server does not support service levels.
logged in rhsm.log
As per comment 1 verifying defect using following rpm
Got following message in rhsm.log
2012-04-10 16:26:36,689 [DEBUG] @connection.py:343 - Response status: 200
2012-04-10 16:26:36,689 [WARNING] @preferences.py:98 - Disabling release version dropdown, server does not support release versions.
2012-04-10 16:26:36,690 [WARNING] @preferences.py:78 - Disabling service level dropdown, server does not support service levels.
Resolving defect as verified
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.