nova cloud controller uses public name to reach cinder despite use-internal-endpoints

[José Pekkarinen]

Hi,

I have a new environment with xenial/queens where I set use-internal
endpoints both in cinder and nova-cloud-controller. When I run testing
on this cloud I see a couple of test fails because of an API error,
from nova api logs I can see backtraces like the file attached. From
juju I can see:

$ juju config nova-cloud-controller use-internal-endpoints
true
$ juju config cinder use-internal-endpoints
true
$ juju config cinder os-internal-hostname
cinder.internal.mydomain.com
$ juju config nova-cloud-controller os-internal-hostname
nova.internal.mydomain.com

Thanks!

José.

[José Pekkarinen (koalinux)]

subscribed field-critical.

José.

[José Pekkarinen (koalinux)]

Moved to field medium as we could workaround using local dns.

José.

[Andrew McLeod (admcleod)]

Please provide a bundle for replication

[Launchpad Janitor (janitor)]

[Expired for OpenStack nova-cloud-controller charm because there has been no activity for 60 days.]

[Arif Ali (arif-ali)]

This may have been because the relation between nova-cloud-controller and cinder was not set?