Revert "Add osd blacklist cap when openstack client cap is built"
Explicit allowance for command blacklist shouldn't be necessary in
master nor ussuri/train as per [1] and, more in general, shouldn't
ever be needed with "profile rbd"
It seems a problem seen when upgrading from jewel to luminous, for
tripleo that means upgrading from newton to queens; the changes are
for the jewel keyring so I think the patch should be posted for
the newton branch only
1. https://bugzilla.redhat.com/show_bug.cgi?id=1838145#c25
This reverts commit 4421bf8056
.
Change-Id: I151a1b8d0f2775463580f46082aa22469878dc15
This commit is contained in:
parent
19172a2169
commit
bdf648ff20
|
@ -29,7 +29,7 @@
|
||||||
|
|
||||||
- name: set openstack client caps
|
- name: set openstack client caps
|
||||||
set_fact:
|
set_fact:
|
||||||
osp_client_caps: {'mgr': 'allow *', 'mon': 'profile rbd, allow command "osd blacklist"', 'osd': "{{ profiles | regex_replace('\\, $', '') }}"}
|
osp_client_caps: {'mgr': 'allow *', 'mon': 'profile rbd', 'osd': "{{ profiles | regex_replace('\\, $', '') }}"}
|
||||||
|
|
||||||
- name: set openstack client key
|
- name: set openstack client key
|
||||||
set_fact:
|
set_fact:
|
||||||
|
|
Loading…
Reference in New Issue