openstack
/
charm-deployment-guide
Code Issues Proposed changes

Add known issues section to deploy-guide for upgrades 

This change adds a new section to the upgrade appendix to list known
issues at the time that might not be resolvable via charm changes; i.e.
that need operator manual intervention.

Change-Id: I0250ac7dbb289e7e63703818a475f1854bf0f8a4
This commit is contained in:
Alex Kavanagh 2019-01-11 15:28:42 +00:00
parent bc33b8b04d
commit ba63ff107e
1 changed files with 41 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
deploy-guide/source/app-upgrade-openstack.rst
View File

@ -280,3 +280,44 @@ is only one unit in the application then this is the only option.
---------------------
Check **juju status** and any monitoring solution for errors.
Known Issues to be aware of during Upgrades
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Before doing an *OpenStack* upgrade (rather than a charm upgrade), the release
notes for the original and target versions of OpenStack should be read. In
particular pay attention to services or configuration parameters that have
retired, deprecated or changed. Wherever possible, the latest version of a
charm has code to handle almost all changes such that the resultant system
should be configured in the same way. However, removed, added or replaced
services **will** require manual intervention.
When charms *can't* perform a change, either due to a bug in the charm (i.e. a
system configuration that the charms haven't been programmed to handle) or
because *at the individual charm level* the charm can't change the service
(i.e. when a service is replaced with another service, a *different* charm
would be needed).
However, the following list is known issues that an operator may encounter that
the charm does not automatically take care of, along with mitigation strategies
to resolve the situation.
neutron-gateway charm: upgrading from Mikata to Newton
------------------------------------------------------
Reference Bug `#1809190: switching from external-network-id and external-port
to data-port and bridge-mappings does not remove incorrect nics from bridges
<https://bugs.launchpad.net/charm-neutron-gateway/+bug/1809190>`_
Between the mitaka and newton OpenStack releases, the ``neutron-gateway`` charm
add two options, ``bridge-mappings`` and ``data-port``, which replaced the
(now) deprecated ``ext-port`` option. This was to provide more control over
how ``neutron-gateway`` can configure external networking.
The charm was designed so that it would work with either ``data-port`` (no
longer recommended) *or* ``bridge-mappings`` and ``data-port``. Unfortunately,
when upgrading from OpenStack Mitaka to Newton the referenced bug above was
been encountered, and therefore may require manual intervention to resolve the
issue.