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.
Description of problem:
When having a single satellite with example 2 orgs, and you add a capsule in one org but assign it to both orgs after installation so both orgs can use it, when adding LS for Org 1 they will add, when going to Org 2 adding its LS, Org 1's LS will be remove from the capsule, and when doing it for Org 1 again, Org 2 will be removed.
Using hammer to do it will function as a work arround, making it posible to add LS for both ORGS on one capsule.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install Capsule
2. Attach 2 Orgs.
3. Attach LS for Org 1 trough UI
4. Attach LS for Org 2 trough UI
5. Org1 LS is now gone.
Actual results:
LS for each org is removed if other org is adding his trough UI only.
Expected results:
LS for both Orgs attached at the same time.
Additional info:
Using hammer to add the LS to the capsule you can avoid this "bug"
Can you please confirm whether you can see both the lifecycle-env's once the Org context is set to "Any Context".?
I think here the Org context is masking the other life-cycle environment.
If Org is set to Any and Loc any, you can indeed, see all Lifecycles, and add them. however if you are not a global admin and you then press the capsule under org 1 and add one new lifecycle org2 will have all their lifecycles removed.
A fix could be that org 1/2 can only delete its own Lifecycles instead of deleting all lifecycles that it cant see when adding a new one.