Bug 2159974

Summary:	Unable to disable SCA for an organization without manifest using API
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Subscription Management	Assignee:	Jeremy Lenz <jlenz>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	dsynk, jlenz, pcreech
Target Milestone:	6.13.0	Keywords:	TestBlocker, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-4.7.0.3-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:24:04 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 Roman Plevka 2023-01-11 09:33:51 UTC

Description of problem:
For some reason, API endpoints
/katello/api/organizations/:organization_id/simple_content_access/*
complain about organizations not having manifest imported.

However, I am to disable SCA for such organization using UI with no issues.

My scenario:
I'm using custom products/repos within an organization with no manifest (it is not required) and I'd like to attach subs for these products to a host.


Version-Release number of selected component (if applicable):
6.13.0-6.0

Steps to Reproduce:
1. curl -sku user:pass -H "content-type: application/json" -X PUT https://$(hostname)/katello/api/organizations/22/simple_content_access/disable


Actual results:
{"displayMessage":"Current organization does not have a manifest imported.","errors":["Current organization does not have a manifest imported."]}

Expected results:
since this works using UI even on orgs with no manifest imported, I see no reason for this not to work via API/CLI

Comment 1 Jeremy Lenz 2023-01-17 18:13:34 UTC

Created redmine issue https://projects.theforeman.org/issues/35961 from this bug

Comment 6 errata-xmlrpc 2023-05-03 13:24:04 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 (Important: Satellite 6.13 Release), 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-2023:2097