I can reproduce this bug with build:
virt-manager-2.0.0-5.el8.noarch
Steps:
1. Remove default storage pool if it exists.
2. Define new storage pool that will point to the same directory as the default one with a different name then 'default:
# cat pool-images.xml
<pool type='dir'>
<name>images</name>
<target>
<path>/var/lib/libvirt/images</path>
</target>
</pool>
# virsh pool-define pool-images.xml
Pool images defined from pool-images.xml
# virsh pool-start images
Pool images started
3. Run virt-install command that will try to create new disk in default storage pool:
# virt-install --name def-disk --memory 512 --import --disk size=1
ERROR Error: --disk size=1: Storage pool not found: no storage pool with matching name 'default'
Then try to verify this bug with new build:
virt-manager-2.0.0-5.1.el8_0.noarch
virt-install-2.0.0-5.1.el8_0.noarch
virt-manager-common-2.0.0-5.1.el8_0.noarch
libvirt-4.5.0-23.module+el8+2800+2d311f65.x86_64
qemu-kvm-2.12.0-63.module+el8+2833+c7d6d092.x86_64
Steps:
4. Rerun virt-install command that will try to create new disk in default storage pool:
# virt-install --name def-disk --memory 512 --import --disk size=1
WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results.
Starting install...
Allocating 'def-disk.qcow2'
...
Result: No error reports, so I move this bug from ON_QA to 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-2019:1533