I have received some feedback on the proposed story grooming process. I have
made some changes based on that feedback and moved the content to a public
etherpad[0].
The main difference from the first version is the lack of the "groomed" state
for a story. Once the author thinks a story has all
Pulp, along with the Puppet (pulp_puppet) and RPM (pulp_rpm) plugins,
has been updated to 2.8.3, Beta 2.
This release also includes betas for OSTree plugin (pulp_ostree) version
1.1.1, the Docker plugin (pulp_docker) version 2.0.1, and the Python plugin
(pulp_python) version 1.1.1.
The release
Kodiak is right that the second task stuck at "Waiting to Begin" is
likely waiting behind another operation on that same repo. Canceling the
one prior will likely allow the later one to start.
How many workers are running and how many do you expect? You can see
what Pulp thinks with: `pulp-admin
I've been noticing that although my Pulp sync's are successful, it appears
I'm missing packages. I'm syncing with Red Hat repositories for RHEL6 w/
Pulp, then syncing with Spacewalk. When I sync with Spacewalk, I see the
below error:
131 errata skipped because of empty package list.
Sync
Yes Kodiak, there is no such task for this repo. I forgot to mention that
tasks i cancelled several times aw well. That did not worked for me. even
if i cancel task, reboot the server and try to execute, it enters into
waiting stage again.
On Tue, May 3, 2016 at 9:23 PM, Kodiak Firesmith
I believe you may need to cancel the pending repo sync task before you can
delete the repo. Maybe try:
pulp-admin tasks cancel --task-id=2d776d63-fd8a-4e0a-8f32-d2276c85187c
pulp-admin tasks cancel --task-id=03842c9d-e053-4a6f-a4c4-2d7302be9c8c
Then:
pulp-admin rpm repo delete
Could anyone please tell me what went wrong with the repository. One of my
EL7 server registered and was able to fetch contents from CDN. Recently I
found one of the repo stuck after downloading RPMs. It’s never ending. I
rebooted my server, cancelled tasks, deleted the repo and recreated, but no
