Bug 2274388

Summary:	API endpoint for activation_keys/:id/product_content should be TRUE by default
Product:	Red Hat Satellite	Reporter:	Cole Higgins <chiggins>
Component:	Activation Keys	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.16.0	CC:	chrobert, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	https://projects.theforeman.org/issues/37350
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:28:23 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 Cole Higgins 2024-04-10 19:19:23 UTC

Description of problem:

Now that Satellite is in SCA mode by default. We should also update the endpoint "GET /katello/api/activation_keys/:id/product_content" so users do not have to pass in the content_access_mode_all param as TRUE. If users do not use this param, an empty list is returned

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


How reproducible:100%


Steps to Reproduce:
1. Create Organization
2. Sync RedHat Repository
3. Enable RedHat Repository on Activation key
4. Hit GET /katello/api/activation_keys/:id/product_content endpoint or run 

hammer activation-key product-content --id --organization-id 

with and without the --content-access-mode-all param 

Actual results:

Without adding the --content-access-mode-all param, an empty list is returned 

With adding the --content-access-mode-all param, the added repository is shown

Expected results:

We should see the enabled repositories on the activation key without needed to pass this param in since sca is now the default

Additional info:

Comment 1 Eric Helms 2024-05-16 16:18:44 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37350 has been resolved.

Comment 2 Eric Helms 2024-06-06 17:28:23 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.