Bug #23185

Attempting to promote a content view to a lifecycle environment in another org is not immediately rejected

Added by Samir Jha over 3 years ago. Updated about 3 years ago.

Content Views
Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:


Cloned from

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:

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:

Associated revisions

Revision bc4a0352 (diff)
Added by sjha4 over 3 years ago

Fixes #23185 - Reject promoting CV to another org>>env


#1 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request added

#2 Updated by Samir Jha over 3 years ago

  • Assignee set to Samir Jha

#3 Updated by Justin Sherrill over 3 years ago

  • Legacy Backlogs Release (now unused) set to 338

#4 Updated by Anonymous over 3 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF