Actions
Bug #6871
closedCapsule happily syncs when invalid environment requested
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1125397
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
Actions