yahoo-eng-team team mailing list archive

[Armando Migliaccio <1207139@xxxxxxxxxxxxxxxxxx>]

** Also affects: networking-cisco
   Importance: Undecided
       Status: New

** No longer affects: neutron

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

Title:
  Add configuration for ignorable exceptions from Cisco Nexus switch

Status in networking-cisco:
  New

Bug description:
  When the Cisco nexus plugin attempts certain configuration operations
  on the Nexus switch, the Nexus switch may return errors (depending on
  the version of Nexus HW and SW) which are benign.  When these
  configuration errors are generated, the ncclient (NetConf Client)
  module, which is used by the Cisco plugin to communicate with the
  Nexus switch, reports these errors as a generic configuration
  exception, but with a string representation which includes a
  description of the  specific error condition.

  For example, some versions of the Nexus 3K will not allow state changes for what those switches consider the extended VLAN range (1006-4094), including these state-change config commands:
      active
      no shutdown
  When a Nexus 3K reports errors for these state-change commands, the ncclient module will report a configuration failure exception which includes these strings in their string representations:
      "Can't modify state for extended"
      "Command is only allowed on VLAN"

  The Cisco Nexus plugin currently looks for and ignores any config
  exceptions with the above error strings whenever the 'active' and 'no
  shutdown' commands are sent to the Nexus switch. Admittedly, it's a
  bit ugly for the plugin to be matching strings for this purpose,
  instead of specific exception types. However, the current ncclient
  module only gives us the description strings on which to match. The
  ncclient module is external to OpenStack, and it may not be possible
  to convince the ncclient community to modify their exception
  generation for something that may be considered Cisco-specific.

  It's possible that these error strings could be modified in the
  future, or that there are other errors reported or other config
  operations which also need to be ignored. In order to handle this, we
  need to add configuration for the Cisco Nexus switch which will allow
  us to define which errors can be ignored and for which configuration
  operations.  The default list for this configuration should be the
  above error conditions (for VLAN state-change commands).  If an
  explicit list is provided in the plugin config, then that list should
  override the default list.

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