Bug 1193208

Summary: 'atomic host upgrade' gives incorrect error after unregistering with subscription-manager
Product: Red Hat Enterprise Linux 7 Reporter: Micah Abbott <miabbott>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED DUPLICATE QA Contact: John Sefler <jsefler>
Severity: low Docs Contact:
Priority: low    
Version: 7.1CC: alikins, bcourt, jhnidek, jsefler, redakkan, wpoteat
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-16 15:30:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Colin Walters 2015-03-17 22:43:27 UTC
Indeed, would make sense.  Adrian, can subman write out the `unconfigured-state=` key again?

Comment 3 John Sefler 2015-03-17 23:43:52 UTC
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.

Comment 8 William Poteat 2016-09-12 14:10:09 UTC
Confirmed bug behavoir as written above on 

rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
Version: 7.2.6-1 (2016-08-18 16:01:03)

Comment 9 Jiri Hnidek 2017-05-30 10:29:27 UTC
It seems this bug is duplicate of 1378495 and it should be already fixed in 7.4 beta. Can anybody confirm?

Comment 10 John Sefler 2017-09-11 14:35:02 UTC
(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.

Comment 11 Rehana 2020-03-16 15:30:22 UTC
Based on comment  10, closing this as a duplicate of 1378495

*** This bug has been marked as a duplicate of bug 1378495 ***