Project

Profile

Help

Story #167

[RFE] new consumers do not auto subscribe to already bound consumer group repos

Added by scressi@wgen.net almost 7 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

++ This bug was initially created as a clone of Bugzilla Bug #801900 ++

Description of problem:

Description of problem:

If you bind a repository to a consumergroup, then add a consumer to the consumergroup that you just bound the repository to, the newly added consumer to that consumergroup will not autobind to that repository. you have to rebind all repos to that consumergroup for new clients

Version-Release number of selected component (if applicable):

1.0 (current)

How reproducible:

very

Steps to Reproduce:
1. pulp-admin consumergroup bind --id=test-consumergroup --repoid=test-repo
2. pulp-admin -u admin -p admin consumergroup add_consumer --id=test-consumergroup --consumerid=test-consumer
3. pulp-admin consumer info --id=test-consumer

Additional Info
Actual results:

+------------------------------------------+
          Consumer Information
+------------------------------------------+

Id upstreamconsumer
Description None
Capabilities
[x] bind
[x] heartbeat
Subscribed Repos []
Agent Status
Responding Yes
Last Heartbeat 2012-03-09 19:10:00.873903+00:00

Expected results:

+------------------------------------------+
          Consumer Information
+------------------------------------------+

Id upstreamconsumer
Description None
Capabilities
[x] bind
[x] heartbeat
Subscribed Repos [u'test-repo']
Agent Status
Responding Yes
Last Heartbeat 2012-03-09 19:10:00.873903+00:00

Additional info:

This is critical as we add several systems a day, and with an ever expanding environment this problem will become worse as time goes on

--- Additional comment from at 11/04/2014 19:45:25 ---

I'm not sure why I put high priority on this nearly a year ago, or why it's severity is urgent, so I am removing the Triaged flag so we can re-triage it.


Related issues

Has duplicate RPM Support - Story #1906: Consumers are added to group but not bound to group reposCLOSED - DUPLICATE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by jcline@redhat.com almost 6 years ago

  • Description updated (diff)
  • Private changed from Yes to No

#2 Updated by kfiresmith almost 6 years ago

+1 this issue.

This is a major usability problem for the concept of host fleet management via pulp-consumer instead of just distributing .repo files via {Puppet,Ansible,Chef}.

Consumer groups absolutely should be uniform resources that are applied to all hosts of a group regardless of when they joined the group.

#3 Updated by ipanova@redhat.com over 5 years ago

  • Has duplicate Story #1906: Consumers are added to group but not bound to group repos added

#4 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

#5 Updated by bmbouter over 2 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#6 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF