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
Updated by The Foreman Bot over 10 years ago
- Status changed from New to Ready For Testing
- Target version set to 54
- Pull request https://github.com/Katello/katello/pull/4514 added
- Pull request deleted (
)
Updated by Eric Helms over 10 years ago
- Assignee set to Brad Buckingham
- Triaged changed from No to Yes
Updated by Brad Buckingham over 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|5ee5f52d0dcf0f4fc90866ff720840cfc56ad078.
Updated by Eric Helms over 10 years ago
- Translation missing: en.field_release set to 13
Actions