Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34623

[vSphere CAPI install] installconfig.platform.vsphere.diskType does not work

XMLWordPrintable

    • No
    • OpenShift SPLAT - Sprint 254, OpenShift SPLAT - Sprint 255
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-33561. The following is the description of the original issue:

      Description of problem:

          The valid values for installconfig.platform.vsphere.diskType are thin, thick, and eagerZeroedThick.But no matter the diskType is set to thick or eagerZeroedThick, the actual check result is thin.
      
      govc vm.info --json  /DEVQEdatacenter/vm/wwei-511d-gtbqd/wwei-511d-gtbqd-master-1 | jq -r .VirtualMachines[].Layout.Disk[].DiskFile[][vsanDatastore] e7323f66-86ef-9947-a2b9-507c6f3b795c/wwei-511d-gtbqd-master-1.vmdk[fedora@preserve-wwei ~]$ govc datastore.disk.info -ds  /DEVQEdatacenter/datastore/vsanDatastore e7323f66-86ef-9947-a2b9-507c6f3b795c/wwei-511d-gtbqd-master-1.vmdk |grep Type  Type:    thin

      Version-Release number of selected component (if applicable):

          4.16.0-0.nightly-2024-05-07-025557

      How reproducible:

          Setting installconfig.platform.vsphere.diskType to thick or eagerZeroedThick and continue installation.

      Steps to Reproduce:

          1.Setting installconfig.platform.vsphere.diskType to thick or eagerZeroedThick     
          2.continue installation          

      Actual results:

          diskType is thin when install-config setting diskType: thick/eagerZeroedThick

      Expected results:

          The check result for disk info should match the setting in install-config

      Additional info:

          

            jcallen@redhat.com Joseph Callen
            openshift-crt-jira-prow OpenShift Prow Bot
            Wenxin Wei Wenxin Wei
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: