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.
[RFE] Generating curl command for registering hosts to Capsule should not allow to select the Activation Key/Lifecycle Env if the same lifecycle env is not added to Capsule.
Description of problem:
Generating curl command for registering client host to Capsule using Global Registration Template method, should not allow to select the Activation Key if the Lifecycle Environment associated with Activation Key is not added to Capsule.
Version-Release number of selected component (if applicable): All Satellite versions
How reproducible: Always
Steps to Reproduce:
1. Deploy a Satellite 6.14 server (say 'satellite.example.com') and a Capsule-6.14 server (say 'capsule.example.com). Then synchronize any repositories (For example: 'Red Hat Satellite Client 6 for RHEL 8 x86_64 RPMs', 'Red Hat Satellite Client 6 for RHEL 9 x86_64 RPMs' and 'Red Hat Satellite Client 6 for RHEL 7 Server RPMs x86_64').
2. Create a new lifecycle environment (say 'prod'). Also create a new content view (say 'cv_1'). Add any repository (say 'Red Hat Satellite Client 6 for RHEL 8 x86_64 RPMs') to 'cv_1'. Publish a new version of 'cv_1' and promote the newly published version to 'prod' lifecycle environment.
3. Navigate to Satellite WebUI -> Infrastructure -> Capsule -> Capsule_Name -> Content -> Edit and add 'prod' lifecycle environment to Capsule server. Note here that only 'prod' lifecycle environment is added to Capsule and 'Library' lifecycle environment is not added to Capsule.
4. Create a Activation Key (say 'AK_1') and associate 'Library' lifecycle environment and 'Default Organization View' content view to the 'AK_1'.
5. Navigate to Satellite WebUI -> Hosts -> Register Host. Select Capsule as 'capsule.example.com'). Set 'AK_1' as 'Activation Keys'. Go to 'Advanced' tab and select Lifecycle Environment as 'Library'.
Actual results: The Library lifecycle environment is not added to Capsule. Still after selecting Capsule, the value for Activation Key can be set as 'AK_1' with which Library lifecycle environment is associated. Also lifecycle environment can be selected as 'Library'.
Expected results: The page should not allow to set 'Activation_Key' as 'AK_1' and 'Lifecycle environment' as 'Library'. Because only prod lifecycle environment is added to Capsule and 'Library' lifecycle environment is not added to Capsule.
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.