Browse Source

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
changes/69/735569/3
Giulio Fidente 2 weeks ago
parent
commit
bdf648ff20
1 changed files with 1 additions and 1 deletions
  1. +1
    -1
      tripleo_ansible/roles/tripleo_ceph_work_dir/tasks/build_keys.yml

+ 1
- 1
tripleo_ansible/roles/tripleo_ceph_work_dir/tasks/build_keys.yml View File

@@ -29,7 +29,7 @@

- name: set openstack client caps
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
set_fact:


Loading…
Cancel
Save