This is caused because the libvirt-qemu user is added to the nova group
as part of the nova-compute-libvirt package post-install script.
Following up on comment #17 above, the user/group of the delta file
changes from nova:nova to libvirt-qemu:kvm, whereas in comment #21
above, the user/group of
As background, adding libvirt-qemu user to the nova group was an attempt
to make /var/lib/nova/* directories more restricted, but that proved to
be difficult with ownership changes between changes nova and
libvirt/qemu.
** Summary changed:
- Creation of image (or live snapshot) from the existing
It turns out the tempfile.mkdtemp() call in nova/utils.py creates the
directory with the restrictive permissions, in our case 0o700.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896617
Title:
I moved this back to New for upstream nova.
@Lee or anyone else from upstream nova, do you have an opinion on
changing the chmod in nova/virt/libvirt/driver.py from:
os.chmod(tmpdir, 0o701)
to:
st = os.stat(tmpdir)
os.chmod(tmpdir, st.st_mode | stat.S_IXOTH)
--
You received this bug
I'm still really confused by this but some thoughts on the nova
os.chmod() call mentioned in an earlier commit that would fix this.
If I chmod the tmp dir that gets created by nova (e.g.
/var/lib/nova/instances/snapshots/tmpkajuir8o) to 755 just before the
snapshot (after the nova chmod), the
@Vlad, I had reported this bug previously on
https://bugs.launchpad.net/nova/+bug/1885418.
My research with different scenarios showed that the problem is probably
related to the latest versions of libvirtd libraries and modules. I did
test the previous versions of libvirtd and they worked
@Vlad, confirmed on my own deployment that it is not fixed in ussuri-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896617
Title:
Creation of image (or live snapshot) from the existing VM
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896617
Title:
Creation of image (or live snapshot) from the existing VM fails if
@Corey, you're mentioning that it works on instance with id 049f but
it was in SHUTOFF state (thus it was working), but if you'd start the
instance:
$ os server list
| 049f76c6-3f6d-4299-b332-bf4c264b8741 | ubuntu-tests2 | SHUTOFF |
internal=10.0.0.30 |
I'm fairly certain that 1885269 fixes this. @vlad it's working for
node-06 and instance 049f76c6-3f6d-4299-b332-bf4c264b8741 on your
deployment. I upgraded all of your nova-compute-kvm's to ussuri-proposed
and it didn't work at first. Either it was something else I changed or a
restart of libvirtd
Some directory comparisons (after enabling ussuri-proposed with the fix
for 1885269). I'm seeing no differences, except that the snapshot is
successful for bionic-train and still fails for focal-ussuri:
bionic-train:
ubuntu@juju-d9-zaza-4dbb8b0e6cc9-21:~$ ls -al
I'm fairly certain this is a package bug so I'm going to triage against
the package for now.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nova (Ubuntu)
Status: New => Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided => Critical
12 matches
Mail list logo
