Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
We are able to set/update "release-version" and "service-level" for an activation key from hammer as below:
# hammer activation-key update --organization REDHAT --name ak1 --release-version 7.3
But we can not get these values back through hammer,
# hammer activation-key info --organization REDHAT --name ak1
Name: ak1
ID: 1
Description:
Host Limit: Unlimited
Auto Attach: true
Lifecycle Environment: Development
Content View: My_Content_view
Host Collections:
1) ID: 2
Name: host_collection2
Version-Release number of selected component (if applicable):
6.3.1
How reproducible:
Always
Steps to Reproduce:
1. hammer activation-key info --organization REDHAT --name ak1
Actual results:
It doesn't display service level and release version.
Expected results:
It should show release version and service level
Additional info:
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.
https://access.redhat.com/errata/RHSA-2018:2927