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.
DescriptionAnand Jambhulkar
2020-04-07 09:15:28 UTC
Description of problem:
----------------------
Cannot create eager zeroed disk before installation / during provisioning. In the Satelite on the "Virtual machine" tab there is a checkbox "Eager Zero". Independent on the state of the checkbox the disk is always created "lazy zeroed".
Version-Release number of selected component (if applicable):
------------------------------------------------------------
Satellite 6.6
How reproducible:
----------------
Always
Steps to Reproduce:
------------------
1. Try to create a host for provisioning on VMware platform.
2. On the "Virtual Machine" tab, click on the checkbox "Eager Zero".
3. Provision the machine.
4. Check the state of the disk by right clicking the settings on VMware.
Actual results:
--------------
Independent on the state of the checkbox the disk is always created "lazy zeroed".
Expected results:
----------------
The disk created for the VM should be "Eager Zero" disk.
Additional info:
---------------
The customer is trying to install SAP systems. These *require* the disks to be Thick provisioned / eager zeroed.
VERIFIED with Satellite 6.8 SNAP 7.0 and vSphere 6.7.0
I provisioned few virtual machines vith various combination of 'Thin Provision' and 'Eager zero'. All hard drives were created with expected configuration.
There was one exception: When using NFS data store without HW acceleration, the drives were always created as 'Thin Provision', which complies VMware vSphere documentation (https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-4C0F4D73-82F2-4B81-8AA7-1DD752A8A5AC.html)
It's also worth mention that selecting both checkboxes (thin provision and eager zero) is not possible as only thick provisioned disks can be eager zeroed.
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 (Important: Satellite 6.8 release), 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-2020:4366