Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1975105

Summary: [global registration] - Global Registration is not working w.r.t. Life Cycle Environment
Product: Red Hat Satellite Reporter: Omkar Khatavkar <okhatavk>
Component: RegistrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Omkar Khatavkar <okhatavk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: lstejska, pcreech
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:12:00 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 Omkar Khatavkar 2021-06-23 06:51:12 UTC 
Description of problem:
[global registration] - Global Registration is not working w.r.t. Life Cycle Environment 

Version-Release number of selected component (if applicable):
Satellite 6.10 Snap 5

How reproducible:
always 

Steps to Reproduce:
1.Create activation key with 1 repo in content view and LCE with 2 repos 
2.Now select the activation key in global registration form and then select the LCE to override the behaviour  
3.

Actual results:
content hosts are registed based on activation key and there is no way we can register based on the LCE, or the LCE does not take precedence 

Expected results:
When ever we override the LCE on top activation key, content host should get registered based on the LCE 

Additional info:
Comment 3 Leos Stejskal 2021-07-13 13:08:04 UTC 
Hi Brad,
it would be better to keep this issue, https://bugzilla.redhat.com/show_bug.cgi?id=1962928#c5 is just overall tracker with 6.10 Registration changes.
Comment 4 Leos Stejskal 2021-07-13 13:09:58 UTC 
Created redmine issue https://projects.theforeman.org/issues/33005 from this bug
Comment 5 Patrick Creech 2021-07-21 18:14:31 UTC 
moving back to assigned, as the upstream PR is not merged yet.
Comment 6 Bryan Kearney 2021-07-28 16:04:08 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33005 has been resolved.
Comment 7 Omkar Khatavkar 2021-08-10 10:50:26 UTC 
Verified this on Satellite 6.10 with Snap 12,

In GR form after selection of activation key, if the content view from the activation key is matching the LCE then the repos are getting enabled based on environment.
Comment 8 Omkar Khatavkar 2021-08-10 10:51:17 UTC 
Verified this on Satellite 6.10 with Snap 12,

In GR form after selection of activation key, if the content view from the activation key is matching the LCE then the repos are getting enabled based on environment.
Comment 11 errata-xmlrpc 2021-11-16 14:12:00 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 (Moderate: Satellite 6.10 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-2021:4702