Bug 800654 - [RFE] Better way to reset CDS registration
Summary: [RFE] Better way to reset CDS registration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Pulp
Classification: Retired
Component: nodes
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jay Dobies
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-06 21:14 UTC by Jeff Ortel
Modified: 2013-09-27 14:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-27 14:50:33 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.