automatic blacklisting of openvswitch packages for auto-update

Bug #1725177 reported by James Page on 2017-10-20
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack neutron-gateway charm
Medium
Unassigned
OpenStack neutron-openvswitch charm
Medium
Unassigned

Bug Description

Restarting openvswitch as part of a package upgrade will cause a minor disruption to networking flows until the neutron-openvswitch agent re-programs the ovs daemons; In order to avoid automatic updates causing this type of problem in charm based deployments we should create a blacklist file for the openvswitch packages to prevent them from being upgraded by auto-updates:

   https://help.ubuntu.com/lts/serverguide/automatic-updates.html

Suggest /etc/apt/apt.conf.d/99{charm_name}-openvswitch file is created with content:

  Unattended-Upgrade::Package-Blacklist {
        "openvswitch-common";
        "openvswitch-switch";
  };

James Page (james-page) wrote :

We might also want to take a similar approach for the ceph charms; package updates should always be managed.

Changed in charm-neutron-gateway:
status: New → Triaged
Changed in charm-neutron-openvswitch:
status: New → Triaged
Changed in charm-neutron-gateway:
importance: Undecided → Medium
Changed in charm-neutron-openvswitch:
importance: Undecided → Medium
Changed in charm-neutron-gateway:
milestone: none → 17.11
Changed in charm-neutron-openvswitch:
milestone: none → 17.11
tags: added: bite-sized canonical-bootstack
James Page (james-page) on 2017-12-01
Changed in charm-neutron-openvswitch:
milestone: 17.11 → 18.02
Changed in charm-neutron-gateway:
milestone: 17.11 → 18.02
Ryan Beisner (1chb1n) on 2018-03-09
Changed in charm-neutron-openvswitch:
milestone: 18.02 → 18.05
Changed in charm-neutron-gateway:
milestone: 18.02 → 18.05
David Ames (thedac) on 2018-06-11
Changed in charm-neutron-openvswitch:
milestone: 18.05 → 18.08
Changed in charm-neutron-gateway:
milestone: 18.05 → 18.08
Paul Collins (pjdc) wrote :

I believe this is addressed by bug 1383674, at least for liberty and above.

However, as the operators of a large icehouse-based cloud, we're still interested in avoiding restarts as much as possible - when you have 64 compute hosts and complex software stacks deployed on them, even a minor disruption adds up quite quickly to a major one.

Paul Collins (pjdc) wrote :

Oh, of course it's not fixed by bug 1383674, which was for neutron-openvswitch-agent restarts.

James Page (james-page) on 2018-09-12
Changed in charm-neutron-openvswitch:
milestone: 18.08 → 18.11
Changed in charm-neutron-gateway:
milestone: 18.08 → 18.11
David Ames (thedac) on 2018-11-20
Changed in charm-neutron-openvswitch:
milestone: 18.11 → 19.04
Changed in charm-neutron-gateway:
milestone: 18.11 → 19.04
David Ames (thedac) on 2019-04-17
Changed in charm-neutron-openvswitch:
milestone: 19.04 → 19.07
Changed in charm-neutron-gateway:
milestone: 19.04 → 19.07
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers