openstack
/
charm-deployment-guide
Code Issues Proposed changes

Add OpenStack upgrade issue - Placement endpoints 

Partial-Bug: #1928992
Change-Id: I52e81a3f5b1320a2348b11bea94811af42a6f387
This commit is contained in:
Peter Matulis 2021-05-21 13:54:52 -04:00
parent 7dca14f60c
commit 64536f938a
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
deploy-guide/source/placement-charm-upgrade-to-train.rst
View File

@ -28,7 +28,7 @@ Here are example commands for the process just described:
juju add-relation placement nova-cloud-controller
List endpoints and ensure placement endpoints are now listening on the new
placment IP address. Follow this up by resuming nova-cloud-controller:
placement IP address. Follow this up by resuming nova-cloud-controller:
.. code-block:: none

10
deploy-guide/source/upgrade-issues.rst
View File

@ -203,6 +203,15 @@ Queens). Problems will occur if storage is scaled out without first disabling
BlueStore (set ceph-osd charm option ``bluestore`` to 'False'). See bug `LP
#1885516`_ for details.
Placement: endpoints not updated in Keystone service catalog
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When the placement charm is deployed during the upgrade to OpenStack Train (as
described in :doc:`placement charm: OpenStack upgrade to Train
<placement-charm-upgrade-to-train>`) the Keystone service catalog is not
updated accordingly. This issue is tracked in bug `LP #1928992`_, which also
includes an explicit workaround (comment #4).
Series upgrades
---------------
@ -246,3 +255,4 @@ error can be resolved with:
.. _LP #1886083: https://bugs.launchpad.net/vault-charm/+bug/1886083
.. _LP #1890106: https://bugs.launchpad.net/vault-charm/+bug/1890106
.. _LP #1912638: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1912638
.. _LP #1928992: https://bugs.launchpad.net/charm-deployment-guide/+bug/1928992