yahoo-eng-team team mailing list archive

[Sam Morrison <1729767@xxxxxxxxxxxxxxxxxx>]

OK I've figured it out, very sorry, not a bug. In newton we had
mech_driver set to midonet_ext and in ocata this is now just midonet
again so this is why everything was failing.

** Changed in: networking-midonet
       Status: New => Invalid

** Changed in: neutron
       Status: New => Invalid

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

Title:
  Ocata upgrade, midonet port binding fails in mixed ml2 environment

Status in networking-midonet:
  Invalid
Status in neutron:
  Invalid

Bug description:
  We have a mixed ml2 environment with some networks are linuxbridge and some are midonet.
  We can bind the 2 different ports to instances on the same compute nodes (can do to the same instance too)

  Testing out Ocata this is now not working due to some extra checks that have been introduced.
  In the logs I get:

  
  2017-11-03 15:50:47.967 25598 DEBUG neutron.plugins.ml2.drivers.mech_agent [req-0779656d-919a-4517-9a5c-12b63d77fd02 ac2c53521bd74ab89acb7b705f2b49ff 2f3e9e705b0b460b9de90d9844e88fd2 - - -] Checking agent: {'binary': u'neutron-linuxbridge-agent', 'description': None, 'admin_state_up': True, 'heartbeat_timestamp': datetime.datetime(2017, 11, 3, 4, 50, 31), 'availability_zone': None, 'alive': True, 'topic': u'N/A', 'host': u'cn2-qh2', 'agent_type': u'Linux bridge agent', 'resource_versions': {u'SubPort': u'1.0', u'QosPolicy': u'1.3', u'Trunk': u'1.0'}, 'created_at': datetime.datetime(2017, 8, 9, 3, 43, 15), 'started_at': datetime.datetime(2017, 11, 3, 3, 38, 31), 'id': u'afba1ad9-b880-4943-aea9-7faae20f787a', 'configurations': {u'bridge_mappings': {}, u'interface_mappings': {u'other': u'bond0.3082'}, u'extensions': [], u'devices': 9}} bind_port /opt/neutron/neutron/plugins/ml2/drivers/mech_agent.py:105
  2017-11-03 15:50:47.967 25598 DEBUG neutron.plugins.ml2.drivers.mech_agent [req-0779656d-919a-4517-9a5c-12b63d77fd02 ac2c53521bd74ab89acb7b705f2b49ff 2f3e9e705b0b460b9de90d9844e88fd2 - - -] Checking segment: {'segmentation_id': None, 'physical_network': None, 'id': u'4d716b78-d0b6-4503-b22d-1e42f7d5667a', 'network_type': u'midonet'} for mappings: {u'other': u'bond0.3082'} with network types: ['local', 'flat', 'vlan'] check_segment_for_agent /opt/neutron/neutron/plugins/ml2/drivers/mech_agent.py:231
  2017-11-03 15:50:47.968 25598 DEBUG neutron.plugins.ml2.drivers.mech_agent [req-0779656d-919a-4517-9a5c-12b63d77fd02 ac2c53521bd74ab89acb7b705f2b49ff 2f3e9e705b0b460b9de90d9844e88fd2 - - -] Network 4d716b78-d0b6-4503-b22d-1e42f7d5667a is of type midonet but agent cn2-qh2 or mechanism driver only support ['local', 'flat', 'vlan']. check_segment_for_agent /opt/neutron/neutron/plugins/ml2/drivers/mech_agent.py:242
  2017-11-03 15:50:47.969 25598 ERROR neutron.plugins.ml2.managers [req-0779656d-919a-4517-9a5c-12b63d77fd02 ac2c53521bd74ab89acb7b705f2b49ff 2f3e9e705b0b460b9de90d9844e88fd2 - - -] Failed to bind port 1c68f72b-1405-43cd-b0d1-ba128f211f51 on host cn2-qh2 for vnic_type normal using segments [{'segmentation_id': None, 'physical_network': None, 'id': u'4d716b78-d0b6-4503-b22d-1e42f7d5667a', 'network_type': u'midonet'}]

  
  It seems that because there is a linuxbridge agent on the compute node that it thinks that is the only type of network that can be bound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1729767/+subscriptions