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.
1. Proposed title of this feature request
- hammer subscription list command should show the start date of the subscriptions
2. What is the nature and description of the request?
On the satellite Web UI under Content >> Red Hat Subscriptions it shows the start date of the subscriptions, but if it is checked through hammer subscription list it doesn’t show the column for the start date.
3. Why does the customer need this? (List the business requirements here)
It is impossible to use automation with Hammer for sharing the information of subscriptions.
4. How would the customer like to achieve this? (List the functional requirements here)
There should be a column of "start date" of the subscriptions in the output of the hammer subscription list command.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
N/A
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I could find
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
N/A
8. Is the sales team involved in this request and do they have any additional input?
No
9. List any affected packages or components.
N/A
10. Would the customer be able to assist in testing this functionality if implemented?
Yes
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/RHBA-2020:1455