Description of problem:
At a partner site, we created a new cloud provider. We subsequently deleted that cloud provider, and then added a new one with the same name. It turns out that the delete operation did not remove the associated cloud tenant or group (i.e., the entries in the "tenants" and "miq_groups" tables in the database).
This ultimately resulted in synchronization problems as reported in https://bugzilla.redhat.com/show_bug.cgi?id=1547734.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a cloud provider
2. delete that cloud provider
3. look at the "access control" section of the "configuration" screen and see that the "cloud tenant" is still visible
Stale cloud tenants resulted in synchronization errors.
Related tenant and group would get deleted.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
There doesn't seem to be any mention of the Provider type, but it sounds like this is for Openstack, is that correct?
That's correct, this was an OpenStack provider.
Hi, just for clarificaton, was the Tenant Mapping feature enabled for the Cloud Provider? Thanks.
Yes, tenant mapping was enabled for the cloud provider.
New commit detected on ManageIQ/manageiq/hammer:
Author: Adam Grare <firstname.lastname@example.org>
AuthorDate: Wed Oct 17 14:26:15 2018 -0400
Commit: Adam Grare <email@example.com>
CommitDate: Wed Oct 17 14:26:15 2018 -0400
Merge pull request #17866 from mansam/cleanup-mapped-tenants-after-ems-destroy
Clean up mapped tenants after a CloudManager is destroyed
(cherry picked from commit 89a1ebf0dadecf532b557f74adbb68dce82c1dae)
app/models/manageiq/providers/cloud_manager.rb | 10 +
spec/models/manageiq/providers/cloud_manager_spec.rb | 11 +
2 files changed, 21 insertions(+)
*** Bug 1547734 has been marked as a duplicate of this bug. ***
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.