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:
The Start Date field is blank for Subscriptions within Content Hosts page in Satellite WebUI
How reproducible: Always
Steps to Reproduce:
1) Navigate to Satellite WebUI -> Hosts -> Content Hosts -> Client_Machine -> Subscriptions -> click on List/Remove or Add.
2) The "Starts" and "Type" field is blank for all Subscriptions
Actual results: The "Starts" and "Type" field is blank for all Subscriptions
Expected results: The "Starts" and "Type" field should not be blank and should be populated accordingly for all Subscriptions
Hi Jayant,
Thank you for reporting the bugzilla.
I see the Version is set to 6.9.0, which indicates that this issue was initially found on 6.9.0. Is that correct?
From a quick scan of the Satellite 6.7, it appears that they are on the older version too.
Hi Anand,
Earlier I tested the same only on Satellite-6.9 and reported the issue. I tested the same scenario in Satellite-6.7 and Satellite-6.8, and could see that the same issue persist on 6.7 and 6.8 version too.
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 (Moderate: Satellite 6.9 Release), 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-2021:1313