Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
- Pulp unable to publish a Content View which has Solve Dependencies enabled.
Version-Release number of selected component (if applicable):
- satellite-6.6.0-5.beta.el7sat.noarch
How reproducible: 100%
Steps to Reproduce:
1. Create a Content View and add RHEL 7/ RHEL 8 repos to it.
2. Enable "Solve Dependencies" for the Content View.
3. Try publishing a version of the Content View.
Actual results:
- The Content View publish task does not complete and is stuck at "Actions::Pulp::Repository::CopyAllUnits (waiting for Pulp to finish the task)"
Expected results:
- Content View should be published.
Additional info:
Hey @Subhash Mane,
I followed your steps of creating a cv and adding a rhel7 server repo and published. It was able to published successfully after waiting for around 20 minutes. The same applied when I added 2 filters and republished. I was able to publish with depSolving just fine. Remember that depSolving takes 3x as long to publish so that's why it's taking a long time for me. Please retest/recheck again and let us know if you're still experiencing issues.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3172