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

[Łukasz Zemczak]

Hello James, or anyone else affected,

Accepted nova into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nova/2:21.0.0-0ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nova (Ubuntu Focal)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
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:
  Fix Committed
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