yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #95971
[Bug 2112492] [NEW] neutron-metadata-agent shows XXX (dead) status despite being functional in Neutron 26.0.0
Public bug reported:
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.
** 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/2112492
Title:
neutron-metadata-agent shows XXX (dead) status despite being
functional in Neutron 26.0.0
Status in neutron:
New
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