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.
DescriptionVaratharaja Perumal G
2020-08-11 22:31:10 UTC
Description of problem:
The subscription start date is blank in the satellite WebUI host subscription tab.
Version-Release number of selected component (if applicable):
satellite-6.8.0-0.7.beta.el7sat.noarch
How reproducible:
WebUI --> Hosts --> Content Host --> < any host > --> Subscriptions tab --> Add --> we can see the subscriptions blank start date.
Actual results:
Subscription date is blank.
Expected results:
We should be able to see the subscription start date.
Additional info:
Closing this bugzilla as a duplicate of bug 1920860. This one was created first; however, the other has a PR that is currently out for review in the upstream.
*** This bug has been marked as a duplicate of bug 1920860 ***