Restart Nova services after adding certs relation
Warn users that they should restart nova-compute and nova-scheduler after a certificates issue due to a known bug. Change-Id: I0727b85cec4aea85a00eda2b6a91416be5370f31
This commit is contained in:
parent
12dcc7d161
commit
313b31af64
|
@ -350,6 +350,22 @@ When deploying the glance-simplestreams-sync charm on Bionic use
|
|||
`source=ppa:simplestreams-dev/trunk`. See bug `1790904
|
||||
<https://bugs.launchpad.net/simplestreams/+bug/1790904>`.
|
||||
|
||||
Restart Nova services after adding certificates relation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
A race condition exists with the use of the 'certificates' relation.
|
||||
When SSL certificates are issued Nova services may attempt to talk
|
||||
to the placement API over HTTP while the API has already changed to
|
||||
HTTPS. See bug `1826382 <https://bugs.launchpad.net/nova/+bug/1826382>`__.
|
||||
|
||||
To mitigate against this, restart nova-compute and nova-scheduler
|
||||
services once certificates have been issued:
|
||||
|
||||
.. code:: bash
|
||||
|
||||
juju run --application nova-compute "systemctl restart nova-compute"
|
||||
juju run --application nova-cloud-controller "systemctl restart nova-scheduler"
|
||||
|
||||
Bugs Fixed
|
||||
==========
|
||||
|
||||
|
|
Loading…
Reference in New Issue