https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-03-06T08:09:23ZPulpPulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=20202015-03-06T08:09:23Zskarmark@redhat.comskarmark@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>NEW</i></li><li><strong>Assignee</strong> deleted (<del><i>skarmark@redhat.com</i></del>)</li></ul><p>Reassigning since I still have some QA work to help preethi on my plate. Not sure whether I will be able to get this one fixed. If I get some time during the break, this could be my first PR for Pulp as a community member :).</p> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=27952015-03-20T19:16:16Zbmbouterbmbouter@redhat.com
<ul><li><strong>Severity</strong> changed from <i>High</i> to <i>3. High</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=39192015-05-04T16:05:41Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>jortel@redhat.com</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=40322015-05-04T22:29:33Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/1843" class="external">https://github.com/pulp/pulp/pull/1843</a></p> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=41302015-05-05T22:38:24Zdkliban@redhat.com
<ul><li><strong>Platform Release</strong> set to <i>2.6.2</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=43092015-05-12T14:48:24Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>ASSIGNED</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=43102015-05-12T14:48:37Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>MODIFIED</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=44142015-05-19T00:00:24Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=44512015-05-21T03:21:11Zpthomas@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>6</i></li></ul><p>verified<br>
[root@mgmt12 ~]# rpm -qa pulp-server<br>
pulp-server-2.6.2-0.2.beta.el6.noarch<br>
[root@mgmt12 ~]#</p>
<pre><code>
[root@mgmt12 ~]# pulp-admin rpm consumer bind --repo-id pulp-unit --consumer-id patch
This command may be exited via ctrl+c without affecting the request.
[\]
Running...
Task Succeeded
[root@mgmt12 ~]#
[root@mgmt12 ~]#
[root@mgmt12 ~]# pulp-admin consumer list
+----------------------------------------------------------------------+
Consumers
+----------------------------------------------------------------------+
Id: patch
Display Name: patch
Description: None
Bindings:
Confirmed: pulp-unit, zoo
Unconfirmed:
Notes:
[root@mgmt12 ~]# pulp-admin node repo enable --repo-id pulp-unit
Repository enabled.
Note: Repository [ pulp-unit ] will not be available for node synchronization
until published. See: the 'node repo publish' command.
Warning: enabling with auto-publish may degrade repository synchronization
performance.
[root@mgmt12 ~]# pulp-admin node repo publish --repo-id pulp-unit
This command may be exited via ctrl+c without affecting the request.
[\]
Running...
Publish succeeded.
[root@mgmt12 ~]# pulp-admin node bind --repo-id pulp-unit --node-id patch
Node bind succeeded.
Note: Repository [ pulp-unit ] will be included in node synchronization.
[root@mgmt12 ~]#
[root@mgmt12 ~]#
[root@mgmt12 ~]# pulp-admin node sync run --node-id patch
This command may be exited via ctrl+c without affecting the request.
(1/2) Repository: pulp-unit
[==================================================] 100%
(2/2) Repository: zoo
[==================================================] 100%
Synchronization succeeded
+----------------------------------------------------------------------+
Child Node Synchronization
+----------------------------------------------------------------------+
Repository:
Action: Added
Content Sources:
Downloads:
Source Id: Parent Node
Total Failed: 0
Total Succeeded: 4
Total Sources: 0
Id: pulp-unit
Units:
Added: 61
Removed: 0
Updated: 0
Repository:
Action: Merged
Content Sources:
Downloads:
Total Sources: 0
Id: zoo
Units:
Added: 0
Removed: 0
Updated: 0
[root@mgmt12 ~]# pulp-admin consumer list
+----------------------------------------------------------------------+
Consumers
+----------------------------------------------------------------------+
Id: patch
Display Name: patch
Description: None
Bindings:
Confirmed: pulp-unit, zoo
Unconfirmed:
Notes:
<\pre>
</code></pre> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=61222015-09-14T12:52:08Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>6</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #666: Running a Node bind on a repo that is already bound to the consumer results in the repo showing up twice in the bindingshttps://pulp.plan.io/issues/666?journal_id=401802019-04-15T21:06:32Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>