Project

Profile

Help

Issue #666

closed

Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindings

Added by pthomas@redhat.com about 9 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.5
Platform Release:
2.6.2
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:
If you run node bind on a repo that is already bound to the consumer, the repo will show up twice in the bindings

Version-Release number of selected component (if applicable):
[root@rhsm-jenkins ~]# rpm -qa pulp-server
pulp-server-2.5.2-0.3.beta.el6.noarch
[root@rhsm-jenkins ~]#

How reproducible:

Steps to Reproduce:
1.Create / Sync a repo on a node server and bind the repo to a consumer
2.Setup that consumer as the node child
3.Enable and publish that repo from step1 on the node
4. Use node bind to bind that repo to the node child
5. Run consumer list
6. Run node list

Actual results:
[root@rhsm-jenkins ~]# pulp-admin consumer list
--------------------------------------------------------------------
Consumers
--------------------------------------------------------------------

Id: january
Display Name: january
Description: None
Bindings:
Confirmed: rhel6, rhel6, drpm, drpm
Unconfirmed:
Notes:

[root@rhsm-jenkins ~]# pulp-admin node list
--------------------------------------------------------------------
Child Nodes
--------------------------------------------------------------------

Id: january
Display Name: january
Description: None
Bindings:
Additive: rhel6, rhel6, drpm, drpm
Update Strategy: additive
Notes:

[root@rhsm-jenkins ~]#

Expected results:

Additional info:

+ This bug was cloned from Bugzilla Bug #1183069 +

Also available in: Atom PDF