yahoo-eng-team team mailing list archive

[George Shuklin <1659290@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Right now when ML2 load mechanism driver, if some of them is unavailable
(due to typo or bug in the driver, preventing it to be loaded by
stevedore), it registered only in 'info' output of neutron-server
('Configured mechanism driver names' and 'Loaded mechanism driver
names').

I believe inability to initialize any on given mechanism drivers is
grave and fatal for neutron server. Server without proper mechanism
driver will silently made all relevant port bindings 'binding_failed',
causing harm and chaos in production environment.

Proposition:

terminate neutron-server with CRITICAL failure if some of
cfg.CONF.ml2.mechanism_drivers is unavailable.

This is a big issue for operators, because, currently, such
misconfigurations are REALLY hard to debug, especially in conjuncture
with (crappy) vendor mechanism drivers.

Affected version: 8.3 (newton)

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Failure to load mechanism drivers in ML2 should be critical

Status in neutron:
  New

Bug description:
  Right now when ML2 load mechanism driver, if some of them is
  unavailable (due to typo or bug in the driver, preventing it to be
  loaded by stevedore), it registered only in 'info' output of neutron-
  server ('Configured mechanism driver names' and 'Loaded mechanism
  driver names').

  I believe inability to initialize any on given mechanism drivers is
  grave and fatal for neutron server. Server without proper mechanism
  driver will silently made all relevant port bindings 'binding_failed',
  causing harm and chaos in production environment.

  Proposition:

  terminate neutron-server with CRITICAL failure if some of
  cfg.CONF.ml2.mechanism_drivers is unavailable.

  This is a big issue for operators, because, currently, such
  misconfigurations are REALLY hard to debug, especially in conjuncture
  with (crappy) vendor mechanism drivers.

  Affected version: 8.3 (newton)

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