openstack
/
charm-guide
Code Issues Proposed changes

Address known issue with ambiguous interfaces 

nova-cloud-controller now includes new amqp-cell and shared-db-cell
interfaces which may cause ambiguous relation errors while deploying
legacy bundles. Addressed in 18.11 release notes doc.

Change-Id: I4cf4b2b8870fbc6eaa2c21fd20c9428e38cc28de
Related-Bug: #1804301
This commit is contained in:
Drew Freiberger 2018-11-20 14:15:45 -06:00
parent 4cc9b4dd9b
commit 95e0317264
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/1811.rst
View File

@ -206,6 +206,17 @@ https://bugs.launchpad.net/nova-lxd/+bug/1790943
The issue is that very recently tempest has started failing some tests where the instance is not found when going to delete various items after a test (e.g. network vif). nova-lxd complains that the profile doesn't exist, which means the instance has already been deleted. When setting the concurrency to 1 for tempest, the failures disappear. Either tempest is now showing race conditions in nova-lxd - pylxd - lxd, or tempest has its own internal issues; it's not clear yet which is the case.
New ambiguous relation interfaces on nova-cloud-controller
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1804301
With the release of Nova Cell support, new relation interfaces have been added to the nova-cloud-controller charm which creates potential deployment issues with bundles using implied relations between nova-cloud-controller and rabbitmq-server (amqp) or mysql (shared-db). The following relation definitions may be used to set these explicitly:
.. code:: bash
- [ "nova-cloud-controller:shared-db", "mysql:shared-db" ]
- [ "nova-cloud-controller:amqp", "rabbitmq-server:amqp" ]
Bugs Fixed
==========