The issue is that the agent is reporting at 5 minute intervals, not 30 seconds.
2021-08-26 12:30:41.101 495681 INFO networking_baremetal.agent.ironic_neutron_agent [-] Starting agent networking-baremetal. 2021-08-26 12:30:41.137 495681 INFO networking_baremetal.agent.ironic_neutron_agent [-] Adding member id c68f1490-4252-4c74-be59-3a02f5b6bce3 on host undercloud.mydomain.tld to hashring. 2021-08-26 12:35:41.130 495681 DEBUG networking_baremetal.agent.ironic_neutron_agent [-] Listing Ironic ports. _report_state /usr/lib/python3.6/site-packages/networking_baremetal/agent/ironic_neutron_agent.py:209 2021-08-26 12:35:41.179 495681 DEBUG networking_baremetal.agent.ironic_neutron_agent [-] Found Ironic ports: [] _report_state /usr/lib/python3.6/site-packages/networking_baremetal/agent/ironic_neutron_agent.py:211 2021-08-26 12:40:41.131 495681 DEBUG networking_baremetal.agent.ironic_neutron_agent [-] Listing Ironic ports. _report_state /usr/lib/python3.6/site-packages/networking_baremetal/agent/ironic_neutron_agent.py:209 2021-08-26 12:40:41.187 495681 DEBUG networking_baremetal.agent.ironic_neutron_agent [-] Found Ironic ports: [] _report_state /usr/lib/python3.6/site-packages/networking_baremetal/agent/ironic_neutron_agent.py:211
This change[1] in TripleO changed it to 300s, instead of the neutron default which is 30s.
<hjensas> ksambor: ^^ Any reason to up the report interval from 30s (the default) to 300s? https://opendev.org/openstack/neutron/src/branch/master/neutron/conf/agent/common.py#L112 <hjensas> Tengu: ^ that explains the bug. <ksambor> hjensas, yah it was to small for bigger/more dense deployments with ovn
It seems the longer interval makes sense for OVN so we should try to find a way to reduce the interval specifically for ironic-neutron-agent instead of reverting it.
https://opendev.org/openstack/tripleo-heat-templates/commit/5ab70af5a681c2281d0a8883b6aaf41f94f0855f
The issue is that the agent is reporting at 5 minute intervals, not 30 seconds.
2021-08-26 12:30:41.101 495681 INFO networking_ baremetal. agent.ironic_ neutron_ agent [-] Starting agent networking- baremetal. baremetal. agent.ironic_ neutron_ agent [-] Adding member id c68f1490- 4252-4c74- be59-3a02f5b6bc e3 on host undercloud. mydomain. tld to hashring. baremetal. agent.ironic_ neutron_ agent [-] Listing Ironic ports. _report_state /usr/lib/ python3. 6/site- packages/ networking_ baremetal/ agent/ironic_ neutron_ agent.py: 209 baremetal. agent.ironic_ neutron_ agent [-] Found Ironic ports: [] _report_state /usr/lib/ python3. 6/site- packages/ networking_ baremetal/ agent/ironic_ neutron_ agent.py: 211 baremetal. agent.ironic_ neutron_ agent [-] Listing Ironic ports. _report_state /usr/lib/ python3. 6/site- packages/ networking_ baremetal/ agent/ironic_ neutron_ agent.py: 209 baremetal. agent.ironic_ neutron_ agent [-] Found Ironic ports: [] _report_state /usr/lib/ python3. 6/site- packages/ networking_ baremetal/ agent/ironic_ neutron_ agent.py: 211
2021-08-26 12:30:41.137 495681 INFO networking_
2021-08-26 12:35:41.130 495681 DEBUG networking_
2021-08-26 12:35:41.179 495681 DEBUG networking_
2021-08-26 12:40:41.131 495681 DEBUG networking_
2021-08-26 12:40:41.187 495681 DEBUG networking_
This change[1] in TripleO changed it to 300s, instead of the neutron default which is 30s.
<hjensas> ksambor: ^^ Any reason to up the report interval from 30s (the default) to 300s? https:/ /opendev. org/openstack/ neutron/ src/branch/ master/ neutron/ conf/agent/ common. py#L112
<hjensas> Tengu: ^ that explains the bug.
<ksambor> hjensas, yah it was to small for bigger/more dense deployments with ovn
It seems the longer interval makes sense for OVN so we should try to find a way to reduce the interval specifically for ironic- neutron- agent instead of reverting it.
https:/ /opendev. org/openstack/ tripleo- heat-templates/ commit/ 5ab70af5a681c22 81d0a8883b6aaf4 1f94f0855f