Bug 790229 - Unregistering consumer on server leaves consumer in bad state
Summary: Unregistering consumer on server leaves consumer in bad state
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jeff Ortel
QA Contact: Preethi Thomas
URL:
Whiteboard:
: 790227 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-13 23:57 UTC by Jason Connor
Modified: 2014-03-31 01:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-27 14:21:05 UTC


Attachments (Terms of Use)

Description Jason Connor 2012-02-13 23:57:48 UTC
Description of problem:
I registered a consumer, unregistered it from the server, and tried to re-register it and got the following:
[root@consumer-2 jconnor]# pulp-consumer consumer register --id consumer-2
error:  A consumer [consumer-2] already registered on this system; Please unregister existing consumer before registering.

How reproducible:
Always

Steps to Reproduce:
1. register consumer
2. unregister consumer via pulp-admin on the server
3. re-register consumer
  
Actual results:
error:  A consumer [consumer-2] already registered on this system; Please unregister existing consumer before registering.

Expected results:
Successful re-registration

Comment 1 Jason Connor 2012-02-14 06:53:05 UTC
you also cannot unregister using pulp-consumer, you have to manually remove /etc/pki/pulp/consumer/cert.pem

Comment 2 Jason Connor 2012-02-14 15:17:27 UTC
This only happens when gofer is not configured or running correctly. However, if gofer is not communication, the consumer should not be unregistered.

Comment 3 Todd Sanders 2012-02-14 16:39:46 UTC
Let's improve the Documentation. Need to reference necessary firewall ports (from install area in UG) in consumer area of UG.

Comment 4 Todd Sanders 2012-02-14 16:40:34 UTC
*** Bug 790227 has been marked as a duplicate of this bug. ***

Comment 5 Michael Hrivnak 2013-09-27 14:21:05 UTC
this seems to have been fixed at some point.


Note You need to log in before you can comment on or make changes to this bug.