Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Currently if someone has a subscription expire on them, and they go to My Installed Products, they'll see the generic "you have a product without a subscription" message. It'd be nicer if we instead showed a custom string that says they had a subscription expire.
We should also include a status message for expiring subscriptions.
I'd like to talk about how we handle expired subscriptions as well, I'm not sure blanking all data in the table except for saying "Expired" is the best approach, it could be useful to keep the dates there, so they easily know how long ago the subscription expired. It could be beneficial to keep the expired cert around until either they attach a new subscription, or x days have gone by, rather than automatically cleaning up the cert on the next check-in.
Expired Strings:
"1 subscription expired."
"2 subscriptions expired."
Expiring Strings:
"1 subscription expiring."
"2 subscriptions expiring."
Then they could glance down at the table and see when they expired by looking at the date ranges, and click on the subscription for potentially more information.
Matches up with Backlog item - US22516
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Since we are unable to provide this feature at this time,
it has been proposed for the next release of
Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Since Red Hat is unable to address this request at this time,
it has been proposed for the next release of Red Hat Enterprise
Linux.