charm-nova-cloud-controller:stable/21.01

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

5db0669... by Aurelien Lourot on 2021-02-17

Fix for not passing CA cert to nova-compute

The charm looked for `keystone_juju_ca_cert` on disk
instead of
`/usr/local/share/ca-certificates/keystone_juju_ca_cert.crt`

Change-Id: Ib7cfdadc3a75fca951792ef2c2e2b454b1ad021d
Closes-Bug: #1915504
(functionally equivalent to commit bd3e24f359e75f6fc1a47346274630fffbceb2b0)

50d1708... by Aurelien Lourot on 2021-02-10

Updates for stable branch creation 21.01

Set default branch for git review/gerrit.
Switch tests to stable.
Switch to using stable charm-helpers branch.
Switch to using stable charm.openstack branch.
Switch to using stable zaza branch.
Switch to using stable zaza-openstack-tests branch.

Change-Id: Ia34c41be06a8c0c0cb204f9c1af491a08e51498e

0e02c9a... by Alex Kavanagh on 2021-01-20

Hotfix charmhelpers sync for local_address() fix

The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().

Note: func-test-pr is to test a change in zaza around model deletion.

Change-Id: I758571613a945631e16412c9515b931029538c00
func-test-pr: https://github.com/openstack-charmers/zaza/pull/410

92eb1e0... by Aurelien Lourot on 2020-11-05

Add Groovy to the test gate

Change-Id: Ia7b8ea4cf40f1aeb77b11fb3c5201ffcdfae59cb

51b3383... by Alex Kavanagh on 2021-01-15

Updates for testing period for 20.01 release

Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9

* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
  - ensure master branch for charms.openstack
  - ensure master branch for charm-helpers
* Remove unit_get mock from unit tests as not in charmhelpers context

Change-Id: Ic828c8d6dd45148a1684c74d3f2b2157cfe6bbc4

93efd6e... by Frode Nordahl on 2021-01-15

Fix CA certificate on cloud-compute relation

Note that part of this fix belongs in c-h, but let's add it here
as a tactical measure given we are practically frozen.

Enable TLS in the functional test for focal-ussuri and onwards.

Also switch to focal-ussuri as target for smoke.

Drop Trusty/Mitaka as it currently does not pass with symptoms
like https://bugs.launchpad.net/charm-nova-compute/+bug/1861094

Closes-Bug: #1911902
Change-Id: I7b12479ce3afb94a0fb21c26b1ac78736b81aba2

a29e54b... by Zuul <email address hidden> on 2021-01-14

Merge "Updates for testing period for 20.01 release"

f4e3c8f... by Alex Kavanagh on 2021-01-12

Updates for testing period for 20.01 release

* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
  - ensure master branch for charms.openstack
  - ensure master branch for charm-helpers

Change-Id: I65d378de1b124c3c668e05bb37c79fe45596747b

93aa769... by Aurelien Lourot on 2021-01-12

Remove Disco and Eoan bits

Change-Id: I5c82d4399e41203a1a63810605ae8e687059bb20

6c5a5cd... by Alex Kavanagh on 2021-01-07

Ensure user is aware upgrade has not happened w/ train

There is a 'hole' in the user experience where if you try to
openstack-upgrade from stein to train but have no already related
placement to the nova-cc unit, then the openstack upgrade is aborted and
a workload message indicates that the relation is needed.

However, if you then subsequently add the placement relation, the
warning goes away, but the payload is not upgraded to match the
openstack-origin value.

This patch adds a warning if the openstack-origin is for train, the
payload is stein, the action-managed-upgrade is false and the placement
relation is made; i.e. that the operator fell into the above hole.

Change-Id: I360f2d72cad374c31ee766065af682e2fa6218d1
Closes-Bug: #1910276