Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-214

Unreliable ERROR message as Unable to resolve Externalgateway Mac address,while unstacking one of compute node on openstack

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • unspecified
    • openstack.net-virt
    • None
    • Operating System: All
      Platform: All

    • 4416

      Build#: Lithium-SR1 Build
      Openstack: stable/kilo

      local.conf snip
      =======
      enable_plugin networking-odl https://github.com/stackforge/networking-odl stable/kilo
      Q_PLUGIN=ml2
      ENABLE_TENANT_TUNNELS=True
      Q_ML2_TENANT_NETWORK_TYPE=vxlan
      PUBLIC_INTERFACE=em3
      ODL_LOCAL_IP=20.1.1.3
      disable_service q-l3
      Q_L3_ENABLED=True
      ODL_L3=True

      ODL custom.properites
      ================
      ovsdb.l3.fwd.enabled=yes

      Environment
      ============
      Openstack controller & 3 compute node(s) connected with ODL as external mode.

      Problem:
      ========
      Unresolved MAC Gateway error on karaf logs when unstack one of compute node instance in openstack side.However other compute nodes managed to reach external gateway and there is no functionalitywise impact.

      This karaf logs mislead to end-user.
      This error message goes-away until unstacked compute node to restacked!

      Step to Recreate:
      1.Disassociated floating IP,Deleted all VM's spawned on os-compute-1 node and unstacked
      2.Only error seen in the karaf logs.however L3 & l2 flows worked in between another two compute in new & old VM's.
      3.Untill restack and provision on VM with associate floating IP,this Unresolved MAC keeps on thrown on karaf logs.

      --Attached relevant logs.
      MAC_NOT_RESOLVED.txt -> during unstack of compute node
      MAC_NOT_RESOLVED.txt -> during restack of compute node

            Unassigned Unassigned
            vasanthan_balasubram@dell.com Vasanthan Balasubramaniyan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: