Bug 2124343

Summary:	When simple content access is enabled, we should not be able to attach subscription to RHEL 7 Client.
Product:	Red Hat Satellite	Reporter:	Rohit Rajput <rrajput>
Component:	Candlepin	Assignee:	Barnaby Court <bcourt>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.0	CC:	bbuckingham, chrobert, nmoumoul, pwaghmar, saydas
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:30:42 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:
Bug Depends On:	2017774, 2332067
Bug Blocks:

Description Rohit Rajput 2022-09-05 18:18:25 UTC

Description of problem:

When Simple Content Access is enabled on Satellite, we should not be able to attach a subscription to the RHEL 7.9 client.


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

Red Hat Satellite 6.12.
Red Hat Satellite 6.11.
Red Hat Satellite 6.10.

How reproducible: Always


Steps to Reproduce:

1. Enable SCA on Satellite manifest.

2. Register an RHEL 7.9 client with Satellite.

3. Try to attach a subscription to the client.

# subscription-manager attach --pool=xxxxxxxxxxxxxxxxxxxxxxxxxx
Successfully attached a subscription for: Red Hat Satellite Infrastructure Subscription


Actual results:

- Successfully attach a subscription to the client.

Expected results:

- Since the SCA is enabled, attaching a subscription to the client should be ignored.

Additional info:

Comment 3 Brad Buckingham 2023-10-04 21:43:14 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 9 Brad Buckingham 2023-11-02 17:08:04 UTC

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Comment 10 Eric Helms 2024-06-06 12:30:42 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.