openstack
/
nova
Code Issues Proposed changes

[stable-only] Improve the reno for consoleauth upgrade check 

This adds more information to the release note to make it clear that
the nova-consoleauth service is deprecated and should not be deployed,
except in cases of a live/rolling upgrade.

Change-Id: I28fc8fa00a8402d0cbc738729fb43758524aeb80
(cherry picked from commit ea71592d7a)
This commit is contained in:
melanie witt 2019-05-23 20:59:46 +00:00
parent 8e130e2be7
commit 9fea5a2f34
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
releasenotes/notes/nova-status-check-consoleauths-618acb3a67f97418.yaml
View File

@ -1,7 +1,13 @@
---
upgrade:
- |
A new check is added to the ``nova-status upgrade check`` CLI to check for
use of the ``nova-consoleauth`` service to warn and provide additional
The ``nova-consoleauth`` service is deprecated and should no longer be
deployed, however, if there is a requirement to maintain support for
existing console sessions through a live/rolling upgrade, operators should
set ``[workarounds]enable_consoleauth = True`` in their configuration and
continue running ``nova-consoleauth`` for the duration of the live/rolling
upgrade.
A new check has been added to the ``nova-status upgrade check`` CLI to
help with this and it will emit a warning and provide additional
instructions to set ``[workarounds]enable_consoleauth = True`` while
performing a live/rolling upgrade.