Bug 1287518 - Creating a new lifecycle environment path throws error message
Summary: Creating a new lifecycle environment path throws error message
Keywords:
Status: CLOSED DUPLICATE of bug 1349492
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
: 1331171 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 09:24 UTC by Dirk Herrmann
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 17:40:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dirk Herrmann 2015-12-02 09:24:39 UTC
Description of problem:

While adding a new lifecycle environment to an existing LC ENV path or while creating a new path it throws an error message: 

# hammer lifecycle-environment create \
>    --name "OSE3-PROD" \
>    --description "OpenShift Platform Production Environment" \
>    --prior "OSE3-DevQA" \
>    --organization "$ORG"
Could not create environment:
  Validation failed: Locations you cannot remove locations that are used by hosts or inherited., Environments you cannot remove environments that are used by hosts or inherited.

Using WebUI after clicking Save button the page does not reload and the same error message appears in foreman production log.

Nevertheless in both cases the new LC ENV has been successfully created.

Version-Release number of selected component (if applicable):


How reproducible:

Create a new LC ENV using hammer CLI or WebUI.

Steps to Reproduce:
1. 
2.
3.

Actual results:

Error message but LC ENV is created.

Expected results:

No error message and using WebUI page reload shows again the LC ENV main page.


Additional info:

Comment 3 Brad Buckingham 2016-04-20 17:47:30 UTC
The error message on this bug is very similar to bug 1326101.

Comment 4 Brad Buckingham 2016-05-02 20:47:24 UTC
*** Bug 1331171 has been marked as a duplicate of this bug. ***

Comment 6 Brad Buckingham 2016-06-23 17:40:12 UTC

*** This bug has been marked as a duplicate of bug 1349492 ***


Note You need to log in before you can comment on or make changes to this bug.