← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1980488] Re: [OVN] OVN fails to report to placement if other mech driver is configured

 

** Changed in: neutron
       Status: New => 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/1980488

Title:
  [OVN] OVN fails to report to placement if other mech driver is
  configured

Status in neutron:
  Fix Released

Bug description:
  Bugzilla reference:
  https://bugzilla.redhat.com/show_bug.cgi?id=2103019

  NOTE: we don't catch this error in our CI because we don't test OVN
  with other mech drivers, for example SR-IOV. This is happening in
  versions prior to Zed (the bugzilla refers to Wallaby).

  Description of problem:
  OSP17 (Wallaby) environment with OVN+SRIOV configured

  sriov_agent.ini includes the following minimum BW configuration that should be reported to placement:
  [sriov_nic]                                                                                                                                                                                                                                   
  physical_device_mappings=datacentre:enp7s0f3,datacentre:enp5s0f0
  resource_provider_bandwidths=enp7s0f3:10000000:10000000,enp5s0f0:10000000:10000000
  resource_provider_hypervisors=enp7s0f3:computesriov-0.localdomain,enp5s0f0:computesriov-0.localdomain                                                                                                                                         

  placement section is correctly configured on neutron.conf:
  [placement]
  auth_url=http://10.20.1.65:5000
  username=nova
  password=D6BO88QBbKbEYI76XkNzX5W68
  project_domain_name=Default
  project_name=service
  user_domain_name=Default
  region_name=regionOne
  auth_type=password

  
  When the sriov-agent running in a compute node is restarted, it successfully generates the information that should be reported to placement:
  2022-07-01 08:03:13.803 526516 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Physical Devices mappings: {'datacentre': ['enp7s0f3', 'enp5s0f0']}
  2022-07-01 08:03:13.804 526516 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Exclude Devices: {}
  2022-07-01 08:03:13.804 526516 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider bandwidths: {'enp7s0f3': {'egress': 10000000, 'ingress': 10000000}, 'enp5s0f0': {'egress': 10000000, 'ingress': 1000000
  0}}
  2022-07-01 08:03:13.804 526516 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider inventory defaults: {'allocation_ratio': 1.0, 'min_unit': 1, 'step_size': 1, 'reserved': 0}
  2022-07-01 08:03:13.804 526516 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider hypervisors: {'enp7s0f3': 'computesriov-0.localdomain', 'enp5s0f0': 'computesriov-0.localdomain'}
  2022-07-01 08:03:13.805 526516 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp7s0f3: 5 get_numvfs /usr/lib/python3.9/site-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/
  eswitch_manager.py:133
  2022-07-01 08:03:13.805 526516 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp5s0f0: 5 get_numvfs /usr/lib/python3.9/site-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/
  eswitch_manager.py:133

  
  However, the neutron server is unable to send those data to placement:
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager [req-f40ac07f-9e01-480d-b4a3-11cd63ade5f1 - - - - -] Error during notification for neutron.services.placement_report.plugin.PlacementReportPlugin.handle_placement_config-1384518 agent, after_update: AttributeError: 'OVNMechanismDriver' object has no attribute 'agent_type'
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager Traceback (most recent call last):
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager   File "/usr/lib/python3.9/site-packages/neutron_lib/callbacks/manager.py", line 197, in _notify_loop
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager     callback(resource, event, trigger, **kwargs)
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager   File "/usr/lib/python3.9/site-packages/neutron/services/placement_report/plugin.py", line 204, in handle_placement_config
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager     if agent['agent_type'] not in self._agents.supported_agent_types:
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager   File "/usr/lib/python3.9/site-packages/neutron/services/placement_report/plugin.py", line 264, in supported_agent_types
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager     self._supported_agent_types = [
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager   File "/usr/lib/python3.9/site-packages/neutron/services/placement_report/plugin.py", line 265, in <listcomp>
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager     driver.obj.agent_type
  2022-07-01 08:03:13.967 20 ERROR neutron_lib.callbacks.manager AttributeError: 'OVNMechanismDriver' object has no attribute 'agent_type'

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



References