yahoo-eng-team team mailing list archive

[Brian Haley <2112492@xxxxxxxxxxxxxxxxxx>]

Strange, we are calling the looping code with a function argument:

            self.heartbeat = loopingcall.FixedIntervalLoopingCall(
                self._report_state)

Will have to do some more debugging.

Shows we don't have much (any) functional coverage for this code.

** Changed in: neutron
       Status: Fix Released => Confirmed

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

Title:
  neutron-metadata-agent shows XXX (dead) status despite being
  functional in Neutron 26.0.0

Status in neutron:
  Confirmed

Bug description:
  Environment:
  - OpenStack Release: 2025.1 (Epoxy) / Neutron 26.0.0
  - OS: Ubuntu 24.04 LTS
  - Backend: RabbitMQ for RPC

  Issue:
  neutron-metadata-agent appears as XXX (dead) in `openstack network agent list` despite:
  - Service being active and running (systemctl status shows active)
  - Metadata functionality working correctly for instances
  - [agent] section configured with report_interval = 30
  - log_agent_heartbeats = true shows no actual heartbeat attempts in logs

  Expected: Agent should show :-) (alive) status
  Actual: Agent shows XXX (dead) status

  Configuration tested:
  - Verified RabbitMQ connectivity
  - Confirmed Nova metadata service reachability
  - Checked hostname resolution
  - Verified other agents (L3, DHCP, OVS) report correctly

  This appears to be a state reporting implementation issue specific to
  the metadata agent, as it doesn't seem to be sending RPC heartbeat
  messages despite configuration.

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