Red Hat Bugzilla – Bug 834012
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
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.
I've looked into this a bit.
The cli and the gui each check for releaseVer support in different ways. I'm going to open a bug for subman to fix this, and make them both check in the same way (fwiw the way the gui operates will be the way that they will both check).
katello will need to make sure the releaseVer value is always on a consumer.
New bug is https://bugzilla.redhat.com/show_bug.cgi?id=838942 fwiw
Author: Tom McKay <firstname.lastname@example.org>
Date: 2012-08-30 (Thu, 30 Aug 2012)
@Tom: how do I verify this? I don't see a "system preferences" anywhere in the web ui...
taking QE contact.
I had the same issue on CFSE... also a machine with Gnome :)
checked on latest provided SAM 1.2 it looks pretty good (and as expected).
1. import manifest
2. register a system (don't turn on autosubscribe there)
3. via SAM ui go to the system's info and edit the release to: 6.3
4. install subscription-manager-gnome (if it's not there)
5. run subscription-manager-gui
6. refer to the "Preferences" and see that checkbox for "Release version" is enabled and has the value of: 6.3
packages the check was made:
Closing out verified bugs from 1.2. Somehow the errata tool missed them.