Bug 1125397

Summary: Capsule happily syncs when invalid environment requested
Product: Red Hat Satellite 6 Reporter: Brad Buckingham <bbuckingham>
Component: APIAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: cwelton, jmontleo, xdmoon
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6871
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-11 12:26:05 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 Brad Buckingham 2014-07-31 18:12:44 UTC
Description of problem:

Assuming a capsule (id:1) has only the dev (id:2) lifecycle environment attached, attempting to perform a synchronize with the prod (id:4) lifecycle environment will attempt to perform the synchonize.

Scenario:

hammer capsule synchronize --id 1 --environment-id 4

Actual Result:

the server will attempt to sync environment 4, even if it is not associated with the capsule

Expected Result:

the server should return an error to the user indicating that it is an invalid environment

Comment 2 Brad Buckingham 2014-07-31 18:22:48 UTC
Created redmine issue http://projects.theforeman.org/issues/6871 from this bug

Comment 3 Brad Buckingham 2014-07-31 18:31:38 UTC
Fix proposed in Katello PR: 

https://github.com/Katello/katello/pull/4514

Comment 6 Bryan Kearney 2014-09-11 12:26:05 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.