Bug 2228784 - [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.
Summary: [RFE] Generating curl command for registering hosts to Capsule should not all...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-03 09:07 UTC by Jayant Bhatia
Modified: 2023-08-08 11:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19432 0 None None None 2023-08-08 11:13:11 UTC

Description Jayant Bhatia 2023-08-03 09:07:12 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.