yahoo-eng-team team mailing list archive

[Mithil Arun <arun.mithil@xxxxxxxxx>]

Public bug reported:

I'm running a metadata agent on provider network and I see that the
metadata service stops listening on port 80 randomly.

I see that the process itself is running, but port 80 is not open in the
DHCP namespace. There are no logs in neutron-server, neutron-metadata-
agent, neutron-dhcp-agent or journalctl.

The only way to recover is to kill ns-metadata-proxy and have neutron-
metadata-agent restart it at which point, the port is up.

In addition to monitoring the process itself, neutron-metadata-agent
must watch for port 80 in the namespace as well.

ENV: Ubuntu 16.04 running neutron rocky.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1843801

Title:
  metadata-proxy process stops listening on port 80

Status in neutron:
  New

Bug description:
  I'm running a metadata agent on provider network and I see that the
  metadata service stops listening on port 80 randomly.

  I see that the process itself is running, but port 80 is not open in
  the DHCP namespace. There are no logs in neutron-server, neutron-
  metadata-agent, neutron-dhcp-agent or journalctl.

  The only way to recover is to kill ns-metadata-proxy and have neutron-
  metadata-agent restart it at which point, the port is up.

  In addition to monitoring the process itself, neutron-metadata-agent
  must watch for port 80 in the namespace as well.

  ENV: Ubuntu 16.04 running neutron rocky.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1843801/+subscriptions