Pulp

Description of problem:
When the pulp-consumer runs an rpm repo bind command to bind to a specific repository, there is no way of knowing whether or not the task has completed from the server prospective, you can identify whether or not the task was sent successfully but not when it is complete. As it's asynchronous and the message returns form the server onto the queue for goferd to pickup and then deal with the repo creation, you can't really tell when the repos are actually created to proceed to some installations of rpms.

It would be good if either it was syncrhonous and returns a success on the completion of the repo file i.e. maybe it should be pulp_<repo_name>.repo for each repo creation as oppose one static pulp.repo file for each task it completes, (which would be the preferred for me) or maybe just returns an ID you can then track wiht a query pulp-consumer rpm task --id <id> to see whether it's success or waiting but that itself is quite tiresome as it would mean then wrapping around a loop until success before proceeding for each creation.

The reason for this is because i have a provider / type for pulp and it can create the repos by grabbing hiera data merging it into an array list and then iterates , if they dont already exist on the box already it will then use pulp-consumer to bind to that repo. The issue is that it's possible i proceed with other tasks in puppet that expect those repos to be there and in some instances they are not created quick enough and so i have had to put a sleep in there which is arbitary and i have no visibility of when the repos are created to proceed.

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

How reproducible:
very, it's explained above.

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:
all info above

Additional info:
all info above

+ This bug was cloned from Bugzilla Bug #1171188 +