Bug 688983 - unregistering a cds which has consumer associated repos does not redistribute consumers
Summary: unregistering a cds which has consumer associated repos does not redistribute...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: nodes
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Jay Dobies
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 17:56 UTC by Preethi Thomas
Modified: 2012-02-24 20:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Preethi Thomas 2011-03-18 17:56:08 UTC 
[root@preethi ~]# rpm -q pulp
pulp-0.0.151-1.fc14.noarch


unregistering a cds which has consumer associated repos does not redistribute consumers

1. Register cds and associate to a repo 
2. Create a consumer and bind it to the above repo
3. Unregister the cds
4. Check the pulp.repo
Comment 1 Jay Dobies 2011-10-25 19:27:59 UTC 
commit 55dc15d56280f27006c6b61bbd9f231471f8922a
Author: Jay Dobies <jason.dobies>
Date:   Tue Oct 25 15:27:57 2011 -0400

    688983 - Call to unassociate each repo from a CDS before unregistering
    it so that all of the unassociate steps take place

src/pulp/server/api/cds.py
Comment 2 Jeff Ortel 2011-10-27 03:22:25 UTC 
build 0.242-2
Comment 3 Preethi Thomas 2011-12-22 20:03:00 UTC 
fails_qa

looks like this is still not fixed

I still see this in the client pulp.repo


[root@pulpf15-client ~]# cat /etc/yum.repos.d/pulp.repo 
#
# Pulp Repositories
# Managed by Pulp client
#

[f15]
name = f15
enabled = 1
sslverify = 0
gpgcheck = 0
mirrorlist = file:/etc/yum.repos.d/f15.mirrorlist[root@pulpf15-client ~]#
Comment 4 Preethi Thomas 2012-02-24 20:16:51 UTC 
Pulp v1.0 is released
Closed Current Release.
Comment 5 Preethi Thomas 2012-02-24 20:18:00 UTC 
Pulp v1.0 is released.
Note You need to log in before you can comment on or make changes to this bug.