Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Scenario:
- Org1 Lifecycle Environment = Library > Test > Dev > Prod
- Org2 Lifecycle Environment (None Existing) = Library
- Add new Lifecycle Environment in Org2 (Test for example)
- Error in UI: <Test> of environment must be unique within one organization
- Error in /var/log/foreman/production.log:
2016-04-27 13:38:09 [I] Processing by Katello::Api::V2::EnvironmentsController#create as JSON
2016-04-27 13:38:09 [I] Parameters: {"name"=>"Test", "label"=>"Test", "prior_id"=>"2", "organization_id"=>"3", "api_version"=>"v2", "environment"=>{"name"=>"Test", "label"=>"Test", "prior_id"=>"2"}}
2016-04-27 13:38:09 [E] ActiveRecord::RecordInvalid
2016-04-27 13:38:09 [E] name: ["of environment must be unique within one organization"]
2016-04-27 13:38:09 [E] label: ["of environment must be unique within one organization"]
2016-04-27 13:38:09 [I] Completed 422 Unprocessable Entity in 245ms (Views: 0.3ms | ActiveRecord: 11.3ms)
BUG: environment IS unique to the organization, but it is not unique to Satellite. Does this error message need changed? Or should I be able to create Test > Dev > Prod as a Lifecycle in multiple Organizations?
BUG: Lifecycle is created even though the error seems to indicate that it can't be created
Version-Release number of selected component (if applicable): 6.1.6
How reproducible: Intermittent
Steps to Reproduce:
1. Create Lifecycle in Org1 as follows: Library > Test > Dev > Prod
2. Create Lifecycle in Org2 as follows: Library > Test (stop here)
3. UI displays an error that indicates the Lifecycle Environment can't be created (Error = <Test> of environment must be unique within one organization)
Actual results:
-Lifecycle is created, but the error displayed in the UI and the errors in /var/log/foreman/production.log seem to indicate that the creation was unsuccessful
Expected results:
-Lifecycle is created without an error. The following Lifecycle environments can co-exist:
- Org1: Library > Test > Dev > Prod
- Org2: Library > Test > Dev > Prod
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: Scenario: - Org1 Lifecycle Environment = Library > Test > Dev > Prod - Org2 Lifecycle Environment (None Existing) = Library - Add new Lifecycle Environment in Org2 (Test for example) - Error in UI: <Test> of environment must be unique within one organization - Error in /var/log/foreman/production.log: 2016-04-27 13:38:09 [I] Processing by Katello::Api::V2::EnvironmentsController#create as JSON 2016-04-27 13:38:09 [I] Parameters: {"name"=>"Test", "label"=>"Test", "prior_id"=>"2", "organization_id"=>"3", "api_version"=>"v2", "environment"=>{"name"=>"Test", "label"=>"Test", "prior_id"=>"2"}} 2016-04-27 13:38:09 [E] ActiveRecord::RecordInvalid 2016-04-27 13:38:09 [E] name: ["of environment must be unique within one organization"] 2016-04-27 13:38:09 [E] label: ["of environment must be unique within one organization"] 2016-04-27 13:38:09 [I] Completed 422 Unprocessable Entity in 245ms (Views: 0.3ms | ActiveRecord: 11.3ms) BUG: environment IS unique to the organization, but it is not unique to Satellite. Does this error message need changed? Or should I be able to create Test > Dev > Prod as a Lifecycle in multiple Organizations? BUG: Lifecycle is created even though the error seems to indicate that it can't be created Version-Release number of selected component (if applicable): 6.1.6 How reproducible: Intermittent Steps to Reproduce: 1. Create Lifecycle in Org1 as follows: Library > Test > Dev > Prod 2. Create Lifecycle in Org2 as follows: Library > Test (stop here) 3. UI displays an error that indicates the Lifecycle Environment can't be created (Error = <Test> of environment must be unique within one organization) Actual results: -Lifecycle is created, but the error displayed in the UI and the errors in /var/log/foreman/production.log seem to indicate that the creation was unsuccessful Expected results: -Lifecycle is created without an error. The following Lifecycle environments can co-exist: - Org1: Library > Test > Dev > Prod - Org2: Library > Test > Dev > Prod Additional info: