Red Hat Bugzilla – 1778669 – [machines] If no storage pool is created and set a larger number for the 'Storage' in the VM creation dialog, there is an Ooops when creating VM
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
If no storage pool is created and set a large number for the 'Storage' in the VM creation dialog, an Ooops will be raised.
Version-Release number of selected component (if applicable):
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Make sure no storage pool created. Then open VM creation dialog and fill the fields.
2. Set a number, which is over than the available storage of the default location(/var/lib/libvirt/images/), in the 'Storage' of the VM creation dialog.(such as 10000GB). Then Click 'Create' button
Actual results:
There will be an Ooops raised .
Expected results:
No Ooops is raised.
Additional info:
1. The error message from chrome console is:
machines.js:129 Uncaught TypeError: Cannot read property 'path' of undefined
at machines.js:129
at Array.find (<anonymous>)
at eC (machines.js:129)
at tC (machines.js:129)
at sC (machines.js:129)
at pa (machines.js:108)
at $a (machines.js:108)
at Ps (machines.js:108)
at Nl (machines.js:108)
at Tl (machines.js:108)
2. Though the steps are not similar, the error message is similar with another bug. please close if it is duplication, many thanks
Description of problem: If no storage pool is created and set a large number for the 'Storage' in the VM creation dialog, an Ooops will be raised. Version-Release number of selected component (if applicable): cockpit-machines-208-1.el8.noarch libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64 How reproducible: 100% Steps to Reproduce: 1. Make sure no storage pool created. Then open VM creation dialog and fill the fields. 2. Set a number, which is over than the available storage of the default location(/var/lib/libvirt/images/), in the 'Storage' of the VM creation dialog.(such as 10000GB). Then Click 'Create' button Actual results: There will be an Ooops raised . Expected results: No Ooops is raised. Additional info: 1. The error message from chrome console is: machines.js:129 Uncaught TypeError: Cannot read property 'path' of undefined at machines.js:129 at Array.find (<anonymous>) at eC (machines.js:129) at tC (machines.js:129) at sC (machines.js:129) at pa (machines.js:108) at $a (machines.js:108) at Ps (machines.js:108) at Nl (machines.js:108) at Tl (machines.js:108) 2. Though the steps are not similar, the error message is similar with another bug. please close if it is duplication, many thanks