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.
As I recall in discussions with Adrian, it was a conscious decision to leave the origin file alone when the system was unsubscribed and/or unregistered. If we choose to change this, then I suggest two different states...
1. When registered but not subscribed, something like this makes sense to me...
unconfigured-state=A subscription providing ostree content has not been attached to this system.
2. When unregistered, this makes sense to me... (already the initial state before the first invocation of subscription-manager)
unconfigured-state=This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
(In reply to Jiri Hnidek from comment #9)
> It seems this bug is duplicate of 1378495 and it should be already fixed in
> 7.4 beta. Can anybody confirm?
I would agree with you Jiri. Due to the design changes from RFE bug 1378495, subscription-manager register/attach/unregister no longer alters the current --deployed-origin file even when an entitlement provides a content set of type "ostree". Hence I believe this bug 1193208 is no longer relevant. Closing this bug as a dup of 1378495 is reasonable.