Bug 1823710

Summary:	[RFE] Openshift entitled builds with Satellite without the need of copying them from a registered client
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.6.0	CC:	abadak, adam.kaplan, ahumbe, amarirom, batkisso, bbuckingham, bcourt, bkearney, ChetRHosey, chrobert, daniel.kucera, dsinglet, eric.nothen, hshukla, ipanova, kbeavers, kpelc, lee.brooks, mfuruta, milang, mmeeuw, momran, palshure, pcfe, rjerrido, satellite6-bugs, thadzhie, tmicheli, unixbasis, vpagar
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
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:	2024-06-05 21:37: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 Kenny Tordeurs 2020-04-14 10:27:22 UTC

1. Proposed title of this feature request
Get entitlements from Satellite without the need of copying them from a registered RHEL node.

2. What is the nature and description of the request?
It's required to copy the entitlements from a registered RHEL node for using in the OCP builds.
https://docs.openshift.com/container-platform/4.1/builds/running-entitled-builds.html#running-entitled-builds-with-satellite
Entitlement keypair for a docker build which is not tied to a host system and can be reused in multiple docker builds.

3. Why does the customer need this? (List the business requirements
here)
The used entitlement is copied from a subscribed RHEL node. There is a very high risk potential in the environment with the amount of people which are working independently that can cause those certs to be revoked.

4. How would the customer like to achieve this? (List the functional
requirements here)
Generate entitlements without the need of copying them from a registered RHEL node to avoid those entitlements from being revoked in case something happens to the RHEL node from which they originate.

5. Is there already an existing RFE upstream or in Red Hat bugzilla?
No

8. Does the customer have any specific timeline dependencies?
No

Comment 4 Adam Kaplan 2020-04-15 18:09:36 UTC

This relates to OpenShift's efforts to improve the experience of using subscription content in workloads [1].

[1] https://issues.redhat.com/browse/DEVEXP-473

Comment 9 Michel 2020-05-19 17:14:00 UTC

related Github issue:

https://github.com/code-ready/crc/issues/914#issuecomment-598100171

Comment 22 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 23 Brad Buckingham 2022-09-05 22:59:20 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 36 Akash Badak 2024-02-05 16:13:17 UTC

Hello Team,

One of our customers has requested an update as they have waited more than 3 years and from the updates, we can sense they are getting a little impatient.

Can we please have an update on this BZ?

Also, the customer has commented to "The Case is now open for over 3 years. Any ideas when you are going to resolve this?"


Regards,
Akash Badak
Red Hat

Comment 38 Eric Helms 2024-06-05 21:37:59 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.

Comment 39 Red Hat Bugzilla 2024-10-12 04:25:10 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days