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.
So I changed the check and scoped it by environment. Is this okay? I can imagine a system named the same in preproduction and production.
cc907bc 746339 - System Validates on the uniqueness of name
# REOPEN
The issue still exists for the katello: katello-0.1.116-1.el6.x86_64
Scenario performed:
----
server1 performs: subscription-manager register --name=test --environment=Test ...
server2 performs: subscription-manager register --name=test --environment=Dev ...
(for both the same org is used - ACME_Corporation)
Scenario fails with ActiveRecord exception like:
---
ActiveRecord::RecordInvalid
name: has already been taken
Rendered text template (0.0ms)
Completed 400 Bad Request in 90ms (Views: 0.4ms | ActiveRecord: 2.1ms)
So maybe the DB side has some constraint(s) still there?
# REOPEN
Following is the case that again breaks the logic :)
1. subscription-manager register --username admin --password admin --org=ACME_Corporation --environment=dev
2. subscription-manager register --username admin --password admin --org=EMEA_Corporation --environment=dev
(so same env name, different orgs - which is quite possible case)
packages:
katello-0.1.148-1.git.0.0b9ff7d.el6.noarch
subscription-manager-0.98.3-1.el6.x86_64
(and the case with different env names in one org - is fixed now)