[Bug 1885269] Re: ussuri: unable to stop and start an instance post upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package nova - 2:21.0.0-0ubuntu3

---------------
nova (2:21.0.0-0ubuntu3) groovy; urgency=medium

  * d/rules: Blacklist test_tcp_rst_no_compute_rpcapi.

 -- James Page <james.page at ubuntu.com>  Tue, 30 Jun 2020 09:06:12 +0100

** Changed in: nova (Ubuntu Groovy)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1885269

Title:
  ussuri: unable to stop and start an instance post upgrade

Status in Ubuntu Cloud Archive:
  In Progress
Status in Ubuntu Cloud Archive ussuri series:
  In Progress
Status in Ubuntu Cloud Archive victoria series:
  In Progress
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Focal:
  In Progress
Status in nova source package in Groovy:
  Fix Released

Bug description:
  == Impact ==

  instances cannot be stopped and then started

  == Test Case ==

  Deploy OpenStack (using Juju Charms)
  Create networking and boot an instance
  stop the instance
  start the instance
  (fails with permissions errors)

  == Regression Potential ==

  Low - the proposed change opens the permission under /var/lib/nova to
  allow for the odd ownership changes that happen during instance
  lifecycle.

  == Original Bug Report ==

  bionic or focal with OpenStack Ussuri.

  The latest version of the nova package sets permissions on package
  update for /var/lib/nova:

    find /var/lib/nova -exec chown nova:nova "{}" +
    find /var/lib/nova -type f -exec chmod 0640 "{}" + -o -type d -exec chmod 0750 "{}" +

  However, when managing vm's via libvirt, various ownership changes
  happen to the underlying disks that mean that nova can no longer
  access the disk files with 0640 permissions.

  The disks (and base image) for a vm are created as nova:nova; libvirt
  then shifts the ownership to libvirt-qemu:kvm as the vm starts.  When
  the vm is stopped the ownership reverts to root:root.

  0640 permissions are maintained - however nova is not part of the root
  or kvm groups so cannot access the file - which means the instance
  cannot be restarted.

  The following permissions are required for correct operation:

    find /var/lib/nova -type f -exec chmod 0644 "{}" + -o -type d -exec
  chmod 0755 "{}" +

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1885269/+subscriptions