Avoid termination of ML2 Arista mechanism driver when EOS is not available
Bug #1624501 reported by
Nader Lahouti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-arista |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The current behavior of initialization method in Arista ML2 mechanism driver is to terminate the driver, if it fails to register with EOS. This behavior results in termination of neutron-server process. In an ML2 heterogeneous environment, it could cause problem as it does not allow other mechanism driver to initialize and run.
It is desirable not to terminate the driver if registration with EOS fails. The registration can be done when EOS is available.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-arista (master) | #1 |
| Changed in networking-arista: | |
| status: | New → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit d10821ce44ef6ee
Author: Nader Lahouti <email address hidden>
Date: Fri Sep 16 16:58:40 2016 -0700
Do not fail initialization when EOS not available
In the initialization of Arista ML2 mechanism driver, if registration with
EOS fails only log an error message and continue with the next step in the
initialization.
The registration will be performed in the sync method periodically.
A new flag is introduced which is an indication of availability of EOS to
Arista ML2 driver. In case of failure it is set to unavailable and when
registration succeeds it will be set to available.
Change-Id: I32218e2f2e3a97
Closes-Bug: #1624501