Bug 800654

Summary: [RFE] Better way to reset CDS registration
Product: [Retired] Pulp Reporter: Jeff Ortel <jortel>
Component: nodesAssignee: Jay Dobies <jason.dobies>
Status: CLOSED NOTABUG QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mhrivnak, skarmark
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-27 14:50:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeff Ortel 2012-03-06 21:14:00 UTC 
We need a better way to reset CDS registration.  Currently, when a CDS is removed from a pulp server and not in communication with the agent on the CDS, it leaves the CDS in an unusable state.  The CDS won't allow registration because it /thinks/ its already registered.

Currently user have to ssh onto the CDS and delete the /var/lib/pulp-cds/.gofer/secret file manually.

Alternatives:

1. Provide a script on the CDS to clean up registration artifacts.

2. Support a /forced/ registration that requires and alternate form of auth such as user/password.

3. Other?
Comment 1 Jay Dobies 2012-04-02 19:32:01 UTC 
Punting out of sprint 34. This may get realigned to 1.1 but I suspect it will be part of the v2 CDS implementation.
Comment 2 Michael Hrivnak 2013-09-27 14:50:33 UTC 
CDS no longer exists in pulp. Closing.