Bug 1748426

Summary:	Pulp unable to publish a Content View which has Solve Dependencies enabled.
Product:	Red Hat Satellite	Reporter:	Subhash Mane <smane>
Component:	Pulp	Assignee:	Kersom <koliveir>
Status:	CLOSED ERRATA	QA Contact:	Kersom <koliveir>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	cwelton, dalley, jyejare, ltran, mmccune, rchan, zhunting
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libsolv, python-solv	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:50:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Subhash Mane 2019-09-03 14:45:34 UTC

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:

Comment 4 Lai 2019-09-03 19:13:21 UTC

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.

Comment 17 Bryan Kearney 2019-10-22 19:50:54 UTC

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