yahoo-eng-team team mailing list archive

[OpenStack Infra <2112492@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/952399
Committed: https://opendev.org/openstack/neutron/commit/3ff9cfd026d29392b049d4e9a51664a86d5bead1
Submitter: "Zuul (22348)"
Branch:    master

commit 3ff9cfd026d29392b049d4e9a51664a86d5bead1
Author: Brian Haley <haleyb.dev@xxxxxxxxx>
Date:   Wed Jun 11 15:43:19 2025 -0400

    Add state reporting back to metadata agents
    
    The call to initialize state reporting was removed
    in [0], which resulted in the metadata-agent for
    ML2/OVS being reported as Not Alive (XXX) when
    'openstack network agent list' is run, even though
    it is running properly.
    
    The second part of this fix is that we need force the
    metadata agents to run using the oslo.service threading
    backend, not the eventlet one. Otherwise the background
    thread sending RPC updates to neutron-server will never
    start.
    
    This also needs to be backported to stable/2025.1 as the
    original change was merged there, but since oslo.service
    4.2.0 does not support the threading backend, we will
    need to implement private versions of LoopingCallBase
    and FixedIntervalLoopingCall there.
    
    [0] https://review.opendev.org/c/openstack/neutron/+/942916
    
    Closes-bug: #2112492
    Change-Id: I4399b6aca1984003e0b564552cc1907425241b9d


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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