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.

Description of problem:
[global registration] - Activation Key and LCE mismatch should be raised at global registration form level 

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

How reproducible:
always 

Steps to Reproduce:
1.Create the activation key activation_key_1 with content view 1 
2.Now create the LCE doest no have the content view 1
3.select the acivation_key1 in the global registration form  

Actual results:
Currently, the registration curl link is generated. But after running it shows the mismatch error    

Expected results:
The error should be raised if the activation_key does not match with the LCE 

Additional info:

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

After discussion with QA (Omkar Khatavkar), we agreed that the issue can be postponed to Sat-7.0.

Fix wont be small and it could break a lot of stuff in the form, in current behavior users will still get the error explaining what is happening, but not in the form but during the registration process.

Can you attach or paste the error that the user will see in this scenario?

Hi,
this haven't been fixed yet, should be reproducible on 6.10

I'm closing this bug I cant reproduce it with same steps, we can reopen in case we similar issue.