This bug was fixed in the package libvirt-dbus - 1.4.1-1ubuntu1
---
libvirt-dbus (1.4.1-1ubuntu1) jammy; urgency=medium
* d/postinst: Fix check for Ubuntu. dpkg-vendor lives in dpkg-dev, it cannot
be used in postinst scripts. Check os-release for "ubuntu" instead, which
wil
Timeout -- I uploaded the patch of the salsa PR to Jammy now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications about this
I sent a fix to Debian: https://salsa.debian.org/libvirt-team/libvirt-
dbus/-/merge_requests/14
I'll give it a few days, if I can get that landed soon, we can just
sync. Otherwise I'll upload it to Jammy directly.
** Changed in: libvirt-dbus (Ubuntu Jammy)
Status: Triaged => Fix Committed
Thanks a lot Martin!
For the sake of helping your look into this, the old fix in Ubuntu was [1] part
of [2].
The two things one might assume to fail are
a) the conditional checks we didn't have before
b) the switch from usermod to adduser
Let me know what you find and if you need help.
[1]:
ht
The image build log shows why:
Setting up libvirt-dbus (1.4.1-1) ...
/var/lib/dpkg/info/libvirt-dbus.postinst: 54: dpkg-vendor: not found
dpkg-vendor is in the "dpkg-dev" package, so it should not be used in
postinst scripts. libvirt-dbus could depend on dpkg-dev, but that's
highly undesirable. T
This regressed in jammy:
# id libvirtdbus
uid=120(libvirtdbus) gid=125(libvirtdbus) groups=125(libvirtdbus)
This was supposed to be fixed in
https://salsa.debian.org/libvirt-team/libvirt-dbus/-/commit/cd5b637db51de64368723996cc770f323b6c1f53
(and hence the package was synced), but this does no
This bug was fixed in the package libvirt-dbus - 1.4.0-2ubuntu0.1
---
libvirt-dbus (1.4.0-2ubuntu0.1) hirsute; urgency=medium
* d/postinst: add libvirtdbus to group libvirt to be able to access the
sockets of libvirtd (LP: #1802005)
-- Christian Ehrhardt Fri, 23 Apr
2021 12:
Old version fails:
root@h:~# apt install libvirt-dbus
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
libvirt-dbus
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 61.6 kB of
Hello Martin, or anyone else affected,
Accepted libvirt-dbus into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libvirt-
dbus/1.4.0-2ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Ok, Impish is complete and thereby all ready.
I uploaded the very same fix to hirsute for the SRU team to consider.
The SRU template is still present from "last time :-/"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
This bug was fixed in the package libvirt-dbus - 1.4.0-2ubuntu1
---
libvirt-dbus (1.4.0-2ubuntu1) impish; urgency=medium
* d/postinst: add libvirtdbus to group libvirt to be able to access the
sockets of libvirtd (LP: #1802005)
-- Christian Ehrhardt Fri, 23 Apr
2021 12:25:41
Impish is open, uploaded if there.
Not sure if that is still in some early-cycle-complexity - we will see and SRU
it then once complete there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Ti
** Changed in: libvirt (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications
FYI I'm mostly waiting for impish to open to be able to go on with this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Thanks Christian! Lesson learned -- for 21.10 I'll update our images a
few weeks *before* the release. (I found a handful of regressions so
far..)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
If we are on impish by the time we can upload then it would be
** Patch added: "libvirt-dbus-refix-1802005.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt-dbus/+bug/1802005/+attachment/5491338/+files/libvirt-dbus-refix-1802005.debdiff
--
You received this bug notification because
This would be re-applying the fix and should still work.
Same change as in the past (minus a typo).
Test PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4533
For review please have a look at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885
Hmmm,
indeed I remember doing a merge for 1.4 in
https://launchpad.net/ubuntu/+source/libvirt-dbus/1.4.0-1ubuntu1
I fail to remember to ahve synced it but the logs point at me :-/
Maybe when the FTFBS was fixed we thought that was all that was left ...
I beg your pardon, agree and will fix it aga
This regressed in 21.04 (hirsute) again. 1.4.0-2 was synced from Debian
(https://launchpad.net/ubuntu/+source/libvirt-dbus/+changelog) instead
of merged.
** Tags added: hirsute regression-release
** Changed in: libvirt-dbus (Ubuntu)
Status: Fix Released => Triaged
** Also affects: libvirt
This bug was fixed in the package libvirt-dbus - 1.3.0-1ubuntu1
---
libvirt-dbus (1.3.0-1ubuntu1) focal-security; urgency=medium
* d/postinst: add libvirtdbus to group libvirt to be able to access the
sockets of libvirtd (LP: #1802005)
-- Christian Ehrhardt Tue, 29 Sep
2020
Tested on Focal PPA
root@f:~# apt install libvirt-dbus
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
geoip-database libgd3 libgeoip1 libxpm4
Use 'apt autoremove' to r
Confirmed, https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4296 has valid Focal test builds now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for
In Focal it is an FTFBS as well, but a different one
=== FAILURES ===
___ TestConnect.test_connect_node_device_create_xml
Fixture "node_device_create" called directly. Fixtures are not meant to be
called
This bug was fixed in the package libvirt-dbus - 1.4.0-1ubuntu1
---
libvirt-dbus (1.4.0-1ubuntu1) groovy; urgency=medium
* d/postinst: add libvirtdbus to group libvirt to be able to access the
sockets of libvirtd (LP: #1802005)
* Fix FTFBS due to libvirt 6.6
- d/p/tests-sk
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt-dbus (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Uploaded to groovy.
I also linked another bug as duplicate which is about the same issue.
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Won't Fix
** Changed in: libvirt-dbus (Ubuntu Focal)
Status: Confirmed => Triaged
** Changed in: libvirt-dbus (Ubuntu)
Status: Co
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt-dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
** Description changed:
+ [Impact]
+
+ * Due to the difference in auth mechanisms between Debian (polkit)
+and Ubuntu (group based) libvirt-dbus does not work as-is in
+Ubuntu.
+
+ * Users would need to manually add a user to a group, but we
+should make the default install experie
Tested on two systems, one with one without the PPA - the fix seems to work
just as planned.
This also will be used as SRU Template test steps.
# should install fine
$ sudo apt-get install libvirt-dbus
# should be avail due to dependencies and look normal (as shown here)
$ ls -l /var/run/libvirt/
The PPA build [1] is now complete if someone would want to give it a try.
That should add the libvirtdbus user to the group on install and therefore
avoid the issues.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4284
--
You received this bug notification because you are a m
FYI - this has issues to rebuild (independent to my changes) which
stalls providing a test PPA a bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-
Sorry, meant that last reply for Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications about this bug go to:
https:
Mark,
Looks like you're correct, removing libvirt-qemu from the libvirt group
seems to allow things to work. I also removed the policy from
/etc/dbus-1/system.d/ and things kept working after a reboot. Still
testing if anything about the system is not working, but seems just
adding libvirtdbus to
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt-dbus/+git/libvirt-dbus/+merge/391526
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is i
libvirt can be configured in two ways, to use policykit for
authentication, or to use traditional unix permissions. Ubuntu uses the
traditional permissions configuration, not the policykit one.
libvirt-dbus ships with a /var/lib/polkit-1/localauthority/10-vendor.d
/libvirt-dbus.pkla file that cont
Hi Chris,
thanks for your report, your workarounds are interesting.
> sudo usermod -a -G libvirt libvirt-qemu
Users that shall be able to connect to libvirt should be in the group "libvirt"
which also is what the socket is on as group.
srw-rw 1 root libvirt 0 Sep 18 12:25 /var/run/libvirt
This bug affects me in Focal (20.04) and is not resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications about this bug
I was able to manually workaround this on Ubuntu 20.04 with the file
from here:
https://wiki.libvirt.org/page/Networking#Using_NetworkManager_directly
And the solution from here:
https://github.com/cockpit-
project/cockpit/issues/13343#issuecomment-570611574
```
# ==
# install cockpit on ub
@Christian: Wontfix WFM, I'm glad that the default works in focal (the
next LTS). For the non-LTS ones it can be worked around (write a systemd
unit drop-in or so), but apparently it's not such a big issue. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The permissions of the sockets are usually controlled by libvirtd.conf
$ grep '^unix_sock_' /etc/libvirt/libvirtd.conf
unix_sock_group = "libvirt"
unix_sock_ro_perms = "0777"
unix_sock_rw_perms = "0770"
The new version still has the config entry but ... "fortunately" ignores
the config and sets 6
Nice, thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications about this bug go to:
https://bugs.launchpad.net
Eoan:
srwxrwx--- 1 root libvirt 0 Feb 24 15:32 /var/run/libvirt/libvirt-sock=
root@e:~# busctl call org.libvirt /org/libvirt/QEMU org.libvirt.Connect
ListDomains u 0
Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
** Also affects: libvirt (Ubuntu Eoan)
Importan
Hi Martin o/
I have
srw-rw-rw- 1 root root 0 Feb 24 07:42 /var/run/libvirt/libvirt-sock=
And the command you posted just works:
# busctl call org.libvirt /org/libvirt/QEMU org.libvirt.Connect ListDomains u 0
ao 0
^^ that was in Focal.
Let me check releases back one by one ...
--
You received
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
s
45 matches
Mail list logo
