Skip to main content

provisioningType property is no longer respected in 8.18.0 and above with improvements to deterministic placement and storage profiles / policies

https://knowledge.broadcom.com/external/article?articleNumber=389672


Products

VMware Aria Suite

Issue/Introduction

  • You are using VMware Aria Automation 8.x and recently upgraded to 8.18.x
  • You previously used provisioningType explicitly in your blueprints to define the disk to be set as Thick/Thin/EagerZero.
    • When disks are provisioned, they do not respect the provisioningType set in the blueprint.
  • You are not currently using Storage Profiles, and no Storage Profiles have been created.

Environment

VMware Aria Automation 8.x

Cause

Beginning with versions 8.18.x and above, feature improvements were released for deterministic datastore and storage profile selection.

Resolution

Prerequisites

  • Version your blueprints before making any changes.

Procedure

  1. Create new storage profiles for each disk provisioningType
  2. Add a capability tag to these profiles, then assign them to be used in the blueprint.
  3. Override the provisioningType set in the storage profile with the provisioningType you prefer.

Example:

Cloud_vSphere_Disk_1:
  type: Cloud.vSphere.Disk.1
  properties:
    capacityGB: 1
    provisioningType: thick
  constraints:
    - tag: 'profile:ThickStorage'

 

Cloud_vSphere.Machine_1:
  type: Cloud.vSphere.Machine
  properties:
    name: '${input.name}'
            - name: 'vSphereBootDiskStorageProfile'
      sizeGB: '${input.bootDiskSize}'
      provisioningType: thick
      constraints:
        - tag: 'profile:ThickStorage'

 

 

 

 

 

Additional Information

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...
Post a Comment
Read more