Bug 1329542

Summary: Multi org with single capsules fail, when adding Lifecycle environments for the individual org trough UI
Product: Red Hat Satellite Reporter: Kim Borup <kborup>
Component: CapsuleAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NEXTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1.8CC: bkearney, cwelton, igreen, kbidarka, kborup, mmccune
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-12 16:44:23 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:

Description Kim Borup 2016-04-22 08:10:20 UTC 
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"
Comment 1 Kim Borup 2016-04-25 09:49:47 UTC 
Sorry it says LS where it should say LC for lifecycle my bad.
Comment 3 Kedar Bidarkar 2016-05-12 16:14:31 UTC 
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.
Comment 4 Kim Borup 2016-05-13 06:46:07 UTC 
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.
Comment 8 Mike McCune 2016-07-12 16:34:29 UTC 
This does not reproduce on 6.2 and will be resolved with the GA of this release.
Comment 10 Mike McCune 2016-07-12 16:44:23 UTC 
This bug does not happen with 6.2 and if it re-occurs feel free to re-open.