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:
When provisioning multiple VMs with ISOs from Satellite, deployment fails because of storage pool name conflicts
Version-Release number of selected component (if applicable):
libvirt-4.5.0-36.el7_9.5.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Provision multiple VMs from Satellite using ISOs for boot media
Actual results:
VMs fail to be created because libvirt creates a storage pool for the provided ISO using a name based on the ISO specified, so other VMs fail because that storage pool name is already in use.
Expected results:
Multiple VMs provisioned as expected from Satellite.
Additional info:
This can be worked around by implemented a time delay between VMs, but this is severely hindering in a production environment.
(In reply to Allie DeVolder from comment #0)
> Description of problem:
>
> When provisioning multiple VMs with ISOs from Satellite, deployment fails
> because of storage pool name conflicts
snip
> VMs fail to be created because libvirt creates a storage pool for the
> provided ISO using a name based on the ISO specified, so other VMs fail
> because that storage pool name is already in use.
Libvirt just uses the storage pool name that it is told to use by the client application.
IOW, the problem of picking non-unique pool names originates in whatever code Satellite is running to provision the VM, rather than in libvirt.
CLOSEing as WONTFIX. There is very little likelihood of any fix being implemented for RHEL7 mainly due to resources. The work around suggested in the dependent bug 2177837 using a retry timeout loop should work fine in RHEL7 too.