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:
Created redmine issue http://projects.theforeman.org/issues/23185 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23185 has been resolved.
Verified in Satellite 6.4: # hammer content-view version promote --organization="a" --to-lifecycle-environment=test --from-lifecycle-environment=Library --id=5 --force Could not promote the content view: Validation failed: CV could not be promoted to test because the content view and the environment are not in the same organization!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927