From cbe3cd9dc3ddc0b05fca500fd02018559cebf67d Mon Sep 17 00:00:00 2001
From: Dan Smith <dansmith@redhat.com>
Date: Fri, 29 Jan 2021 15:30:03 -0800
Subject: [PATCH] Restart glance after updating policy in job

When we write out the glance policy for the multistore job, we do
so after glance has already started. After the json->yaml change,
we will decide too early in g-api lifetime that the legacy file
isn't present and thus never honor it later. So, create it and then
restart glance services.

Change-Id: Ic1c01366dbfdcfb85750b85f960b76aea934db59
---
 playbooks/ceph/glance-copy-policy.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/playbooks/ceph/glance-copy-policy.yaml b/playbooks/ceph/glance-copy-policy.yaml
index 2b9d25fc502f..fc0244c71e96 100644
--- a/playbooks/ceph/glance-copy-policy.yaml
+++ b/playbooks/ceph/glance-copy-policy.yaml
@@ -12,3 +12,4 @@
           # or public) to copy. This way we will be able to test copy
           # image via non-admin as well as on private images.
           echo $'{"copy_image": ""}' > /etc/glance/policy.json
+          sudo systemctl restart 'devstack@g-*'