openstack
/
openstack-ansible
Code Issues Proposed changes

Docs: Manual nova_spice_console removal 

This patch explains how to manually remove nova-consoleauth service
entries left over from the upgrade to Kilo.

Closes-bug: 1487155

Change-Id: Ib9c525d5c017f418c5314fcedc4d133d50df92ae
This commit is contained in:
Major Hayden 2016-02-08 23:17:35 -06:00
parent c9a64de927
commit 79a250f253
2 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/upgrade-guide/index.rst
View File

@ -12,6 +12,7 @@ Contents:
scripts
upgrade-playbooks
process
manual-change
Indices and tables

31
doc/source/upgrade-guide/manual-changes.rst Normal file
View File

@ -0,0 +1,31 @@
Manual Changes
==============
Although the upgrade scripts and playbooks are fairly comprehensive, some
actions require manual intervention from the deployer. Some of these changes
require careful consideration of configuration variables or contents of a
database.
Removing nova spice console services
------------------------------------
Upgrading from Juno to Kilo using the upgrade scripts will automatically
remove the nova_spice_console containers, but the service entries will still
exist within the _services_ table in the _nova_ database. These entries will
require manual removal.
Start by searching for services running the ``nova-consoleauth`` binary:
.. code-block:: sql
SELECT Id, Binary, Host
FROM nova.services
WHERE Binary = 'nova-consoleauth';
If any of the service entries have ``nova_spice_console`` within the ``Host``
column, remove those entries carefully by their ``Id``:
.. code-block:: sql
DELETE FROM nova.services
WHERE Id = ###;