Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66108 - [cockpit] Cannot manage virtual machines anymore since cockpit 216

Attached to Project: Community Packages
Opened by rainer (raneon) - Saturday, 04 April 2020, 09:04 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Monday, 06 April 2020, 18:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since the upgrade of cockpit from 215 to 216 I cannot manage my virtual machines (libvirt) anymore.

The cockpit blog https://cockpit-project.org/blog/cockpit-216.html mentions that virsh has been dropped in favor of libvirt-dbus. Is there some action required for the user or packaging?

Steps to reproduce:
1. upgrade to 216
This task depends upon

Closed by  Massimiliano Torromeo (mtorromeo)
Monday, 06 April 2020, 18:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  libvirt-dbus-1.3.0-2
Comment by rainer (raneon) - Monday, 06 April 2020, 15:09 GMT
  • Field changed: Percent Complete (100% → 0%)
Thanks for providing a new package. But besides this I still have the same issue. In cockpit 215 I could manage all my existing VM's. In 216 they are not there anymore, but I can see them with Virt-Manager.
Comment by Massimiliano Torromeo (mtorromeo) - Monday, 06 April 2020, 16:21 GMT
I was missing the creation of the libvirtdbus system user. It should be working now (with libvirt-dbus-1.3.0-2)

Loading...