Hide Forgot
this is fine, but the uniqueness should be scoped by owner. I could see removing this edit as the is no real business reason for this.
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
I would say - to be scoped by org (as entitlements are associating for organization seems). @Bryan - could you please confirm that?
# 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?
Fix completed in commit 1089b183194d30199132932680ca7ea0a899727e
# 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)
heh. donno why , but it works now ... was unable to reproduce my "issue" - so fixed. :)
# VERIFIED and verified.
getting rid of 6.0.0 version since that doesn't exist