Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 1613679

Summary: VMWare SCSI PV driver not present in FDI initramdisk
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: Discovery ImageAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: low Docs Contact:
Priority: low    
Version: 6.4CC: ktordeur, lzap, mpusater, rabajaj
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:37:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1598020, 1635749    

Description Lukas Zapletal 2018-08-08 07:03:24 UTC 
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
Comment 4 Lukas Zapletal 2018-10-03 15:24:12 UTC 
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.
Comment 6 Jitendra Yejare 2018-12-13 13:45:51 UTC 
Verified!

@ Satellite 6.5 snap 7.0

Steps:

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


Observation:

1. The disk is present as /dev/sda
2. Discovery is successful.


Logs:

# 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
Comment 8 errata-xmlrpc 2019-05-14 12:37:41 UTC 
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/RHSA-2019:1222