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:
While creating a VM from a cockpit, there is no option to select destination storage for VM and it is being created in the default location.
One should be able to select a storage when creating a VM from the cockpit GUI.
If the default storage is not enough to keep the VM disk, there will be an error on vm creation:
"Creation of vm <vm_name> failed ERROR The requested volume capacity will exceed the available pool space when the volume is fully allocated. (81920 M requested capacity > 70403 M available) (Use --check disk_size=off or --check all=off to override)"
Version-Release number of selected component (if applicable):
RHEL 8 Beta
cockpit-dashboard-183-1.el8.noarch
cockpit-machines-183-1.el8.noarch
How reproducible:
Always
Steps to Reproduce:
1. From the cockpit --> Virtual Machines --> create VM
2. With the other details, there is not an option to select a storage pool.
3. There are 4 pools exists in the system though.
Actual results:
No storage pool selection.
Expected results:
Storage pool selection should be available.
Additional info:
Test version:
cockpit-machines-195-1.el7.x86_64
libvirt-dbus-1.3.0-1.el7.x86_64
As the same version cockpit-machines has the same features in rhel 7.7 and 8.1, i tried to verify it in 'cockpit-machines-195-1.el7.x86_64', but there is still a problem, it is that the disk still need to be created by command, or there is still no disk can be chosen though the storage pool can be chosen during the creation.
For the above reasons, and confirm with Katerina, move the bug status to ASSIGNED
Just to clarify: The bug original asked (and still asks in the title) for *selecting* the destination storage pool. Then the scope was extended to also *create* new pools. But I thought current versions can now do that as well?
Comment 11Katerina Koukiou
2020-01-17 11:45:57 UTC
Cockpit does allow users to create Storage Pools from the UI and then you can select from the Vm creation dialog the destination pool for the disk. So I believe this is fully implemented.
Verified with package:
cockpit-machines-211.2-1.el8.noarch
Steps:
1. Enter storage pools page, click "Create Storage Pool",prepare a storage pool, like NFS storage pool
2. Click the new created NFS storage pool,enter "Storage Volumes" tab,click "Create Volume"
3. Enter Virtual Machines page, click "Create VM", choose the storage and volume created in step1&2, click create.
The function is available, so verified.
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