group.of.nepali.translators team mailing list archive

[James Page <james.page@xxxxxxxxxx>]

** Also affects: openvswitch (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: openvswitch (Ubuntu Artful)
   Importance: High
     Assignee: Frode Nordahl (fnordahl)
       Status: Confirmed

** Also affects: openvswitch (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: openvswitch (Ubuntu Zesty)
       Status: New => Triaged

** Changed in: openvswitch (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: openvswitch (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: openvswitch (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: openvswitch (Ubuntu Artful)
       Status: Confirmed => Triaged

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

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1723480

Title:
  openvswitch-switch package postinst modifies existing configuration

Status in OpenStack neutron-openvswitch charm:
  Invalid
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in Ubuntu Cloud Archive pike series:
  Triaged
Status in openvswitch:
  Invalid
Status in openvswitch package in Ubuntu:
  Triaged
Status in openvswitch source package in Xenial:
  Triaged
Status in openvswitch source package in Zesty:
  Triaged
Status in openvswitch source package in Artful:
  Triaged

Bug description:
  Similar to, but slightly different from bug 1712444, we have found the
  upgrade of the openvswitch-switch package by unattended-upgrade (or
  otherwise) will trigger the service restart of openvswitch-switch
  within the neutron-openvswitch charm if the config-changed hook is
  called.

  While this is a reasonable behavior based on an assumption that if the
  /etc/default/openvswitch-switch file changes due to upgrade and the
  charm resets it to the charm-configured version of the file, we should
  want to restart the service to be on the latest code.  However, the
  restart of the service causes between 6-12 seconds of network outage
  for the tenant VMs utilizing OVS.

  Would it be possible to have a config-flag to disable the charm's
  ability to restart the openvswitch-switch service outside of the
  install hook to avoid automated network outages due to package
  upgrades?

  Elsewise, is there a way to serialize the resulting restarts in such a
  way that only one member of the neutron-openvswitch
  application/service is restarting at a time along with a buffer to
  allow for high availability applications to failover and fail back and
  not be afflicted by multiple nodes' switches being restarted
  simultaneously.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1723480/+subscriptions