Bug 1906737

Summary:	docker-type repository is not synced to the external capsule if a puppet CV already exists there
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Capsule - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	Keywords:	Regression, Triaged
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-28 18:02:59 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:
Embargoed:

Description Vladimír Sedmík 2020-12-11 10:20:51 UTC

Description of problem:
Attempts to sync a docker-type repository to the external capsule fail in case there is already present a puppet CV.


Version-Release number of selected component (if applicable):
6.8.1 and later (earlier probably too, not tested)


How reproducible:
always


Steps to Reproduce:
1. Have a Satellite with registered Capsule in the Library LCE.
2. On SAT create a puppet product and repo, upload a puppet module to it.
3. Create a content view, add the puppet module, publish the CV.
4. Sync the capsule.
5. Create a docker-type product and repository:
   Content > Products > Repo Discovery > select Container Images, registry.redhat.io > Discover > select some from dicovered repos > Create Selected
6. Sync the docker-type repository.
7. Sync the capsule again.


Actual results:
Capsule sync task will stop in "Actions::Pulp::Consumer::UnassociateUnits" with error "RestClient::NotFound: 404 Not Found"


Expected results:
Successful sync


Additional info:
If we sync the docker-type repo to an *empty* capsule, it succeeds.

Comment 2 Brad Buckingham 2020-12-14 15:07:07 UTC

Is this a regression from Satellite 6.7?

Comment 3 Vladimír Sedmík 2020-12-14 21:42:48 UTC

(In reply to Brad Buckingham from comment #2)
> Is this a regression from Satellite 6.7?

No, I have reproduced the issue on 6.7.5 snap 2 too. It seems to be a regression from 6.6 - I don't see the issue on 6.6.3 snap 1.

Comment 4 Brad Buckingham 2022-09-02 20:25:18 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2022-09-02 20:31:26 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Brad Buckingham 2022-10-28 18:02:59 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.