Red Hat Bugzilla – Bug 834013
SAM is hiding the releaseVer variable from json causing subscription-manager-gui to disable the Release dropdown.
Last modified: 2015-01-04 16:59:31 EST
+++ This bug was initially created as a clone of Bug #834012 +++
Description of problem:
Consumer registered to SAM-1.1 will fail to support the release feature from the subscription-manager-gui due to SAM hiding releasever from the json.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Register a consumer with >= subscription-manager-0.99.19-1
2. Subscribe consumer to RHEL product.
3. In the Subscription Manager gui navigate to system preferences
Release option / drop down is disabled.
Release should be enabled with ability to select from a list of available releases.
[WARNING] @preferences.py:101 - Disabling relea se version dropdown, server does not support release versions.
Command line the 'release' options work and we are able to --set, --list and retrieve current release value.
Please go back and verify the flows in 833539 and 832118 as part of this.
Author: Tom McKay <email@example.com>
Date: 2012-08-30 (Thu, 30 Aug 2012)
@garik - Can you check your production.log for errors about unable to retrieve release versions?
(Note that I am adding code to propagate this error message up to the user.)
@tom: sure thing, i'll reproduce with following scenario:
importing manifest; enabling RHEL 6.2; enable RHEL 6.3; promoting the whole product (with that repos) to some env; register a system; refer to rhsm gui and try to list the "Releases"
in case of fail: i'll will provide with katello-debug logs.
Failed. Following is the scenario:
1. imported manifest (with RHEL product)
2. enabled 6Server; 6.3; 6.2
3. promoted the product to the env
4. register a system (UI - skip the autosubscribe option)
5. refer to the rhsm gui and click preferences.
6. list the "Releases" - *empty* (but selectable/enabled)
Created attachment 621552 [details]
screenshot - empty releases
attached is the screenshot illustrating empty "Releases"
Please attach /var/log/katello/production.log (I'm looking for error messages).
Also, where can I find that version of subscription-manager-gui?
Created attachment 624057 [details]
Please find the whole katello-debug tarball attached.
if you register (as I did in my case) to RHN Classic you will find the proper one from the base RHEL6Server channel.
P.S. and i confirm, it fails the same way as described above: comment#7
After some digging, this is not a regression and the fix submitted is in fact working.
The original BZ was that katello was not sending the system's _current_ release version at all and this was causing sub-mgr-gui to disable the drop down choice in the UI. As you will note, however, the problem you're seeing is not that the UI is disabled but that it has no choices available.
You can confirm the release version is in fact being passed by changing it in the katello System Details to a value and then checking sub-mgr-gui to see that it is reflected there.
As for there being release version choices available in sub-mgr-gui, that comes directly from the CDN and not through katello at all. From the developers: "You need to be 1) registered 2) rhel 3) subscribed to a rhel prod 4) be pointing at a cdn that works 5) that cdn needs the have the 'listing' file mirror 6) various product/content tags need to match." You can confirm this by registering your system, getting it "green" for subscriptions, installing a product w/ yum, and then checking the available releases.
Unless you have further questions, please return this BZ to VERIFIED at your convenience.
So the scenario (after clarifying it more with Tom in irc):
register the system
through Katello GUI change its release to something "6.2 or 6Server"
launch rhsm gui and assure that there is the dropbox with 6.2 choice value in it.
Moving it to VERIFIED as I confirm: that I can see that on RHSM gui.
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.