Red Hat Bugzilla – Bug 1471622
haproxy (from l3) does not able to reach the neutron_metadata_agent
Last modified: 2018-02-05 14:10:03 EST
Description of problem:
The vm tries to reach the metadata service on the 169.254.169.254, but it receives 500.
openstack-neutron-metadata-agent-docker has a service which provides services
on the /var/lib/neutron/metadata_proxy socket.
The service is consumed by the haproxy services launched in each router net namespaces.
These haproxy instances belongs to the neutron_l3_agent container.
$ docker exec neutron_metadata_agent stat /var/lib/neutron/metadata_proxy
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: fc02h/64514d Inode: 29800114 Links: 1
Access: (0644/srw-r--r--) Uid: (42435/ neutron) Gid: (42435/ neutron)
Access: 2017-07-15 22:01:47.556547000 +0000
Modify: 2017-07-15 22:01:47.556547000 +0000
Change: 2017-07-15 22:01:47.556547000 +0000
$ docker exec neutron_l3_agent stat /var/lib/neutron/metadata_proxy
stat: cannot stat '/var/lib/neutron/metadata_proxy': No such file or directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create network/subnet/router/floatingip/vm/sshkey
2. try to boot the vm
3. The vm receives 500 from the metadata haproxy (no ssh key)
Failed to ssh, the nova conslelog indicates the vm was able to connect to the
dhcp server , but it was not able to get the metadata.
The vm receives metadata over the metadata-service (ssh key) and I am able to ssh the vm.
neutron-ns-metadata-proxy was replaced by haproxy.
Forced config drive usage is a possible workaround.
neutron service should be running on BM for the OSP12 cycle , we should see if the problem still occurs with that configuration.
Moving to GA, will be tested during customized neutron Tech Preview RFE - https://bugzilla.redhat.com/show_bug.cgi?id=1433535
Agreed by UA
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.