Bug 2007775

Summary:	Cockpit can not set up a VM on F35 WS
Product:	[Fedora] Fedora	Reporter:	Pat Kelly <pmkellly72>
Component:	cockpit-machines	Assignee:	Katerina Koukiou <k.koukiou>
Status:	CLOSED ERRATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	gmarr, k.koukiou, mmarusak, mpitt, pmkellly72, robatino
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	RejectedBlocker
Fixed In Version:	cockpit-machines-253-1.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-01 18:44:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pat Kelly 2021-09-24 20:08:33 UTC

Description of problem:
After loading cockpit on F35 Workstation, a VM can not set up on the F35 WS. This is working fine on F34.

Version-Release number of selected component (if applicable):

Cockpit 253-1.fc35
Cockpit-bridge 250-1.fc35
Cockpit-networkmanager 253-1.fc35
Cockpit-system 253-1.fc35
Cockpit-machines 252-1.fc35

How reproducible:
100%

Steps to Reproduce:

1.Load cockpit as follows:

sudo dnf install cockpit

sudo dnf install cockpit-machines

sudo dnf install virt-viewer

sudo systemctl enable --now cockpit.socket

sudo firewall-cmd --add-service=cockpit --permanent

sudo firewall-cmd --reload

reboot

2. Open with Firefox at localhost:9090
Login as root (works fine)

3. In Networks add a bridge that includes eno1 and uses STP (works fine)

4. Click Virtual Machines Responds with "libvirt is no active"


Actual results:
After clicking Click (Virtual Machines) button it Responds with "libvirt is not active"

The "Thouble Shoot and then Show more relationships" seems to indicate a chain of failures.

Expected results:

After clicking Virtual Machines the page where a VM can be added should appear.

Additional info:

Comment 1 Fedora Blocker Bugs Application 2021-09-24 20:28:30 UTC

Proposed as a Blocker for 35-final by Fedora user tablepc using the blocker tracking app because:

 Since Cockpit is sort of the premier management tool for Fedora Linux, one would expect full functionality. I this case the server will be on a VM running on F35 WS where Cockpit was installed.

Reference Requirements: 2.8.2

Comment 2 Martin Pitt 2021-09-27 06:49:00 UTC

This was fixed upstream a few days ago: https://github.com/cockpit-project/cockpit-machines/pull/387
It will be part of Wednesday's c-machines 253 release.

Comment 3 Geoffrey Marr 2021-09-27 18:04:37 UTC

Discussed during the 2021-09-27 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Final)" was made as this does not violate any criteria; the cockpit criteria do not cover virtualization, and the virtualization criterion covers the 'recommended virtualization technology', which does not include Cockpit as currently defined.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-27/f35-blocker-review.2021-09-27-16.00.txt

Comment 4 Fedora Update System 2021-09-30 05:04:35 UTC

FEDORA-2021-94dbdd6c6d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-94dbdd6c6d

Comment 5 Pat Kelly 2021-10-01 18:44:40 UTC

Cockpit machines is now able to run and setup a VM. Problem solved.

Comment 6 Fedora Update System 2021-10-29 22:52:36 UTC

FEDORA-2021-94dbdd6c6d has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.