Created attachment 1368142 [details]
Screenshot of error message
Description of problem:
When trying to configure the Red Hat Dropdbox for logs to be shipped to a support case, from any zone in a global region, we are getting an error stating "Error during 'Save': Validation failed: Name has already been taken".
A sub-region had in the past already been configured to use the Red Hat Dropbox for logs succesfully, and it appears there is a name collision between this existing "Red Hat Dropbox" name in the sub-region, and the attempted configuration in the Global region.
Version-Release number of selected component (if applicable):
Follow steps below
Steps to Reproduce:
1. Configure Global region with a sub-region
2. First configure the sub-region to have log collection done to a "Red Hat Dropbox" and save
3. Go to the Global region and attempt to also set it up to send its logs to a "Red Hat Dropbox" and attempt to save.
4. Notice the error as mentioned above
Can't configure the global region to ship logs to a Red Hat Depot in order to attach to a support case.
Have the ability to ship logs to red hat depot from a Global Region as well as any Sub-regions.
See attached screenshot for the error. Customer is also going to open a support case for this, and link this BZ to the case.
Fixed by https://github.com/ManageIQ/manageiq/pull/16731
New commit detected on ManageIQ/manageiq/fine:
Author: Jason Frey <email@example.com>
AuthorDate: Wed Jan 3 14:27:38 2018 -0500
Commit: Jason Frey <firstname.lastname@example.org>
CommitDate: Wed Jan 3 14:27:38 2018 -0500
Merge pull request #16731 from carbonin/validate_zone_name_within_region
Ensure that the zone name is unique only within the current region
(cherry picked from commit 1bf5290e0bdae708be0f2e8c8122b5768af449c2)
app/models/zone.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Verified on 126.96.36.199.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.