2055168 – Enabling repo synced in upstream SAT under non-default org fails

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.

Bug 2055168 - Enabling repo synced in upstream SAT under non-default org fails

Summary: Enabling repo synced in upstream SAT under non-default org fails

Keywords:
Status:	CLOSED DUPLICATE of bug 2055570
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Inter Satellite Sync
Sub Component:
Version:	6.11.0
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	high
Target Milestone:	6.11.0
Assignee:	satellite6-bugs
QA Contact:	Radek Mynar
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-02-16 12:10 UTC by Vladimír Sedmík
Modified:	2022-03-18 14:12 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2022-03-01 17:25:06 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Vladimír Sedmík 2022-02-16 12:10:09 UTC

Description of problem:
In the downstream SAT, enabling a repository which is synced in the upstream SAT under non-default organization fails.


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


How reproducible:
always


Steps to Reproduce:
1. In upstream SAT, create new organization, upload manifest, enable and sync some repositories (I used rhel-7-server-ansible-2.9-rpms and rhel-7-server-satellite-tools-6.10-rpms).
2. In downstream SAT, create new organization, upload manifest and create SSL CA CC for the upstream SAT.
3. In downstream SAT, go to Manage manifest > CDN Configuration > Upstream Foreman server, fill all fields and click Update:
   URL: <UPSTREAM_SAT_URL>
   Username: admin
   Organization label: OWCA (the org from step 1.)
   LCE label: Library
   CV label: Default_Organization_View
4. Go to Content > Red Hat Repositories and try to enable some repo from step 1.


Actual results:
Error
Upstream organization OWCA does not have a content view with the label


Expected results:
Repository enabled


Additional info:
In the upstream SAT the repository does exist:
# hammer repository-set list --enabled true --organization OWCA
------|------|----------------------------------------------------------------------
ID    | TYPE | NAME                                                                 
------|------|----------------------------------------------------------------------
9318  | yum  | Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server
12054 | yum  | Red Hat Satellite Tools 6.10 (for RHEL 7 Server) (RPMs)              
------|------|----------------------------------------------------------------------

Comment 2 Samir Jha 2022-03-01 17:25:06 UTC

Hi Vladimír,

Thanks for raising this. We noticed this while investigating another BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2055570 and the root cause for both was discovered and fixed in that. The call you noticed the call to endpoint /katello/api/v2/organizations/3/content_views?name= is incorrect and we have updated that to search for label since that is the user entered value. That should resolve this issue as well. I'm going to mark this duplicate and will link it to other issue so these can be tested together when the fix lands in a snap.

Thanks,
Samir

*** This bug has been marked as a duplicate of bug 2055570 ***

Note You need to log in before you can comment on or make changes to this bug.