Project

General

Profile

Actions

Bug #23185

closed

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

Added by Samir Jha about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Content Views
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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:

Actions

Also available in: Atom PDF