Hi Robie, about: "Since we're changing behaviour I'm also concerned that this is high risk of regression for some use case we haven't considered where the previous behaviour is being depended upon. Thoughts on how to mitigate this would be appreciated. I appreciate that Christian has already come up with and tested a variety of use cases here - how comprehensive do you think these are when compared to "weird" things users might be doing?"
Answer: the current workaround would server there as well, one can tweak in file /etc/libvirt/qemu.conf # Whether libvirt should dynamically change file ownership # to match the configured user/group above. Defaults to 1. # Set to 0 to disable file ownership changes. #dynamic_ownership = 1 Currently this is enabled, changing the file to the runtime perms needed and then back (the bug) to root. If you just chown the files to root and disable this feature it will match the former behavior (which now restores the proper former owner). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691590 Title: libvirt restore exactly the old ownership of images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/691590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
