Bug 1287518
Summary: | Creating a new lifecycle environment path throws error message | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Dirk Herrmann <dherrman> |
Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.4 | CC: | bbuckingham, cwelton, mmccune |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-23 17:40:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
The error message on this bug is very similar to bug 1326101. *** Bug 1331171 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 1349492 *** |
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: