From 51757afe1625f6ed74b3bae56f9864c0ea0f6ec8 Mon Sep 17 00:00:00 2001 From: Matt Thompson Date: Wed, 19 Aug 2015 11:41:42 +0100 Subject: [PATCH] Trigger restart after adding user to cephkeys Currently, on an AIO, when you deploy w/ ceph support nova-compute comes up non-functional and needs a restart. Doing an strace on the nova-compute process, you can see nova-compute is unable to read the /etc/ceph/ceph.client.cinder.keyring file. This reason for this is due to the fact that cinder-volume and nova-compute both live on the same host, and a bulk of the tasks in ceph_auth.yml (which do have valid restarts) are being taken care of when the cinder installation playbook is run. When the nova installation playbook is run, ceph_auth.yml is included after nova is installed but when nova is added to cephkeys there is nothing else happening in that task file to trigger a restart of nova. Change-Id: I61e2709ce48ff80fd6eded9c1e6bd649bcd73088 Closes-Bug: #1486504 --- playbooks/roles/ceph_client/tasks/ceph_auth.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/playbooks/roles/ceph_client/tasks/ceph_auth.yml b/playbooks/roles/ceph_client/tasks/ceph_auth.yml index 0d50306b4c..81f3c8b505 100644 --- a/playbooks/roles/ceph_client/tasks/ceph_auth.yml +++ b/playbooks/roles/ceph_client/tasks/ceph_auth.yml @@ -44,6 +44,8 @@ name: "{{ openstack_service_system_user }}" groups: "{{ cephkeys_access_group }}" append: yes + notify: + - Restart os services - name: Provision ceph client keyrings # TODO: do we really need a template for this? what's the added value compare to