RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1778049 - [machines] There is an Ooops during creating VM
Summary: [machines] There is an Ooops during creating VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.2
Assignee: Katerina Koukiou
QA Contact: YunmingYang
URL:
Whiteboard:
: 1778056 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-29 06:56 UTC by YunmingYang
Modified: 2020-04-28 15:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:43:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1639 0 None None None 2020-04-28 15:43:19 UTC

Description YunmingYang 2019-11-29 06:56:47 UTC 
Description of problem:
If there is no 'default' storage pool, then creating/importing a VM will raise an Ooops.

Version-Release number of selected component (if applicable):
cockpit-machines-206-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a storage pool with '/var/lib/libvirt/images/', don't set 'default' for its name
2. Create/Import a VM

Actual results:
There will be raise an Ooops.

Expected results:
No Ooops is raised.

Additional info:
If importing VM, the error message from console is:
machines.js:87 Uncaught TypeError: Cannot read property 'connectionName' of undefined
    at Function.<anonymous> (machines.js:87)
    at Function.<anonymous> (machines.js:1)
    at s (cockpit.js:961)
    at cockpit.js:973
    at n (cockpit.js:879)

If creating VM, the error message from console is:
Uncaught TypeError: Cannot read property 'connectionName' of undefined
    at machines.js:87
    at machines.js:1
Comment 1 Martin Pitt 2019-11-29 14:07:42 UTC 
https://github.com/cockpit-project/cockpit/pull/13219
Comment 2 Martin Pitt 2019-11-29 14:08:14 UTC 
*** Bug 1778056 has been marked as a duplicate of this bug. ***
Comment 5 Xianghua Chen 2019-12-23 11:46:54 UTC 
Failed to verify with packages:
cockpit-machines-209-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

Steps:
1. Create a storage pool with '/var/lib/libvirt/images/', don't set 'default' as its name
2. Create/Import a VM

The Ooops is still there, so set status back to ASSIGNED.
Comment 6 Katerina Koukiou 2019-12-23 16:05:45 UTC 
Xianghua, you are right, 209 addressed only the case where no storage pool was not defined and the path `/var/lib/libvirt/images` didn't exist either.

So the fix will be in release 210. For the record this was fixed with:

commit 84778e3c128dbd622712406e062f71b5fcbf3a17
Author: Simon Kobyda <skobyda>
Date:   Wed Dec 18 12:50:05 2019 +0100

    machines: Fix typo for default storage pool search

$ git describe 84778e3c128dbd622712406e062f71b5fcbf3a17
209-37-g84778e3c1
Comment 8 Xianghua Chen 2020-01-10 14:13:58 UTC 
Verified with packages:
cockpit-machines-210-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

Steps:
1. Create a storage pool with '/var/lib/libvirt/images/', don't set 'default' as its name
2. Create/Import a VM

There is no Ooops and the VM can be created successfully.
So verified.
Comment 10 errata-xmlrpc 2020-04-28 15:43:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1639
Note You need to log in before you can comment on or make changes to this bug.