metadata server unreachable with provider networking only
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
Fix Released
|
High
|
David Ames | ||
OpenStack Neutron Gateway Charm |
Fix Released
|
High
|
David Ames | ||
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
High
|
David Ames |
Bug Description
In the scenario where their is no Nuetron Gateway, we're only using provider networking. Specifically VLAN provider networking.
The one network and subnet created look as follows:
openstack network show mgmt-1
+------
| Field | Value |
+------
| admin_state_up | UP |
| availability_
| availability_zones | zone1, zone2 |
| created_at | 2019-06-
| description | |
| dns_domain | |
| id | 724aef7a-
| ipv4_address_scope | None |
| ipv6_address_scope | None |
| is_default | None |
| is_vlan_transparent | None |
| mtu | 9000 |
| name | mgmt-1 |
| port_security_
| project_id | 143294d60ce5445
| provider:
| provider:
| provider:
| qos_policy_id | None |
| revision_number | 3 |
| router:external | Internal |
| segments | None |
| shared | False |
| status | ACTIVE |
| subnets | 5d0cf549-
| tags | |
| updated_at | 2019-06-
+------
$ openstack subnet show mgmt-1
+------
| Field | Value |
+------
| allocation_pools | 10.243.
| cidr | 10.243.160.0/24 |
| created_at | 2019-06-
| description | |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.243.160.254 |
| host_routes | |
| id | 5d0cf549-
| ip_version | 4 |
| ipv6_address_mode | None |
| ipv6_ra_mode | None |
| name | mgmt-1 |
| network_id | 724aef7a-
| project_id | 143294d60ce5445
| revision_number | 0 |
| segment_id | None |
| service_types | |
| subnetpool_id | None |
| tags | |
| updated_at | 2019-06-
+------
neutron-openvswitch has enable-
$ openstack network agent list | egrep -i 'dhcp|meta'
| 08586252-
| 09f469c9-
| 0a9bc81d-
| 0c0ecf6a-
| 170fb80a-
| 1e0f1511-
| 22a110e4-
| 236387f3-
| 2d643308-
| 2f35c4bd-
| 3db2dcbf-
| 44a09595-
| 44e02602-
| 468e7408-
| 51ba61b8-
| 56f99f61-
| 61df9ce0-
| 6897a6d1-
| 6ab71669-
| 6ba578ee-
| 7feaf689-
| 80e7c6d1-
| a8a70e20-
| b6a751e7-
| bd95e896-
| d5ec415a-
| dba5e158-
| f4640a2e-
| fdde9c2b-
| ff340680-
The instance, when booting is giving the message:
[WARNING]: No active metadata service found
If i create an instance using config-drive (ignoring metadata server), it starts up fine, and has a routing table with 169.254.169.254 via one of the qdhcp namespaces.
Inside of this instance i can ping both the IP of the namespace and the 169.254.169.254 address, but I cannot curl it.
Inside of the namespace if I curl http://
---
# curl http://
<html>
<head>
<title>404 Not Found</title>
</head>
<body>
<h1>404 Not Found</h1>
The resource could not be found.<br /><br />
</body>
---
Doing some googling, I found a suggestion of verify that the following rule existed in the iptables of the namespace:
-A neutron-
I have no such rule, but this is likely because there is no NGW in their environment.
It is also worth noting, that in the console output of the instance, it never attempts to call http://
Bundle can be found at:
Console log of last boot found at:
information type: | Private → Public |
information type: | Public → Private |
description: | updated |
information type: | Private → Public |
Changed in charm-neutron-openvswitch: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → David Ames (thedac) |
milestone: | none → 19.07 |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-openvswitch: | |
status: | Fix Released → Triaged |
milestone: | 19.07 → 20.02 |
Changed in charm-helpers: | |
status: | New → Triaged |
Changed in charm-neutron-gateway: | |
status: | New → Triaged |
Changed in charm-helpers: | |
importance: | Undecided → High |
Changed in charm-neutron-gateway: | |
importance: | Undecided → High |
Changed in charm-neutron-openvswitch: | |
importance: | Critical → High |
Changed in charm-helpers: | |
assignee: | nobody → David Ames (thedac) |
Changed in charm-neutron-gateway: | |
assignee: | nobody → David Ames (thedac) |
milestone: | none → 20.02 |
Changed in charm-neutron-openvswitch: | |
status: | Triaged → In Progress |
Changed in charm-neutron-openvswitch: | |
milestone: | 20.02 → 20.05 |
Changed in charm-neutron-gateway: | |
milestone: | 20.02 → 20.05 |
Doing some further testing, port 8775 is not open int he namespace. But it is open on the compute host.
a curl to http://<compute- with-namespace> :8775 provides:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
latest
So there's a rule missing or a service not running to allow reaching the metadata running on the compute host that holds the namespace