Therefore FDI cannot be booted from HDD and/or HDD cannot be initialized, partitioned and image-deployed manually.
[lzap@box libvirt]$ lsinitrd /home/libvirt/initramdisk/upstream-3.4.4.img | grep vmw_pvscsi
-rw-r--r-- 1 root root 11608 Jan 25 2018 usr/lib/modules/3.10.0-693.17.1.el7.x86_64/kernel/drivers/scsi/vmw_pvscsi.ko.xz
[lzap@box libvirt]$ lsinitrd /home/libvirt/initramdisk/upstream-3.5.0.img | grep vmw_pvscsi
-rw-r--r-- 1 root root 11908 Jul 16 19:24 usr/lib/modules/3.10.0-862.9.1.el7.x86_64/kernel/drivers/scsi/vmw_pvscsi.ko.xz
[lzap@box libvirt]$ lsinitrd /home/libvirt/initramdisk/downstream-3.4.4-1.img | grep vmw_pvscsi
[lzap@box libvirt]$ lsinitrd /home/libvirt/initramdisk/downstream-3.5.0-1.a1.img | grep vmw_pvscsi
This was actually fixed as well in FDI 3.5.
QA: To verify, boot FDI in VMWare VM, ssh to it and verify that disk is present as /dev/sda or /dev/vda.
@ Satellite 6.5 snap 7.0
1. Copy FDI image from satellite servers /usr/share/foreman-discovery-image/foreman-discovery-image-3.5.3-1.iso to VMWare datastore.(for PXELess Discovery)
2. Boot VM from above ISO.
3. Wait for DHCP to assign IP.
4. Provide satellite server URL.
5. Allow Discovery to happen
6. Take SSH of that machine.
7. Verify disk is present as /dev/sda or /dev/vda
1. The disk is present as /dev/sda
2. Discovery is successful.
# ll /dev/sda
brw-rw---- 1 root disk 8, 0 Dec 13 12:47 /dev/sda
# fdisk -l | grep sda
Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors
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.