Bug 790229

Summary: Unregistering consumer on server leaves consumer in bad state
Product: [Retired] Pulp Reporter: Jason Connor <jconnor>
Component: user-experienceAssignee: Jeff Ortel <jortel>
Status: CLOSED WORKSFORME QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mhrivnak, mmccune, tsanders
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-27 14:21:05 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 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.