Bug #23185
closedAttempting to promote a content view to a lifecycle environment in another org is not immediately rejected
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1518426
Description of problem:
When trying to promote a content view to a lifecycle environment in another org, the server initially accepts this and returns a task. The task fails terribly and it is difficult to recover from
(yes i did this by mistake).
Version-Release number of selected component (if applicable):
6.3 (likely possible in 6.2 as well)
How reproducible:
always
Steps to Reproduce:
1. Create org 'a'
2. Create a lifecycle env 'test' in org a
3. Create org 'b'
4. Create some content view in org b, and add one repo to it
5. Publish this content view and grab the version id
6. run:
hammer content-view version promote --organization="Org-A" --to-lifecycle-environment=test --from-lifecycle-environment=Library --id=3591 --force
Actual results:
Error: Runtime Error could not execute statement at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse:2,102
Error when candlepin catches this terrible terrible mistake
Expected results:
Immediate error with something like "This content view is not part of organization "Org-A"
Additional info:
Updated by The Foreman Bot almost 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/7297 added
Updated by Justin Sherrill almost 7 years ago
- Translation missing: en.field_release set to 338
Updated by Anonymous almost 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|bc4a03523a071252fe4ed7c13caa533d78df61c7.