nova-api-metadata does not use keystone internal endpoint
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
Fix Released
|
High
|
James Page |
Bug Description
xenial + pike
I believe this is a duplicate of:
https:/
But let me open a new bug not to hijack the original one.
nova-api-metadata tries to access a public keystone endpoint and fails. Thus instance metadata won't work.
In my case, the host of neutron-gateway does not have any interface binding to OpenStack public endpoints network or a route to the network. use-internal-
172.18.246.39 - keystone public endpoint
172.18.248.39 - keystone internal endpoint
172.18.247.39 - keystone admin endpoint
[/var/log/
2018-03-15 05:39:33.708 505314 ERROR nova.api.
2018-03-15 05:39:33.708 505314 ERROR nova.api.
2018-03-15 05:39:33.710 505314 INFO nova.metadata.
Changed in charm-neutron-gateway: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → James Page (james-page) |
description: | updated |
description: | updated |
Changed in charm-neutron-gateway: | |
milestone: | none → 18.05 |
Changed in charm-neutron-gateway: | |
status: | Triaged → In Progress |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
"Canonical Field High" has been subscribed since this bug affects a delivery.