SDDC Manager vCenter upgrade — Pre-check failed with error 'Bundle validation for bundle of type VCENTER with upgrade version 8.0.3.00600 failed due to error Bundle level precheck for VCENTER failed with exception'.

Products

VMware SDDC Manager VMware vCenter Server 8.0

Issue/Introduction

The following error is observed in the SDDC Manager UI :- 'Bundle validation for bundle of type VCENTER with upgrade version 8.0.3.00600 failed due to error Bundle level precheck for VCENTER failed with exception'.

/var/log/vmware/vcf/lcm/lcm-debug.log

YYY-MM-DDTHH:MM:SS.030+0000 DEBUG [vcf_lcm,0000000000000000,0000,precheckId=acb08c8d-####-####-####-6586####ae65,resourceType=BUNDLE,resourceId=bb0ff1fa-####-####-####-896e####508c] [c.v.e.s.l.p.i.v.VCenterPatchUpgradeImpl,Precheck-1] Error message during bundle precheck Bundle level precheck for VCENTER failed with exception : Error: Error (com.vmware.vapi.std.errors.error) => {
messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
id = com.vmware.appliance.update.precheck_operation_description,
defaultMessage = Run update prechecks,
args = [],
params = <null>,
localized = <null>
}],
data = <null>,
errorType = ERROR
}
2025-11-02T20:22:18.030+0000 INFO [vcf_lcm,0000000000000000,0000,precheckId=acb08c8d-####-####-####-6586####ae65,resourceType=BUNDLE,resourceId=bb0ff1fa-####-####-####-896e####508c]] [c.v.e.s.l.s.i.UpgradePrecheckServiceImpl,Precheck-1] Precheck completed for resource type: BUNDLE, ID: bb0ff1fa-####-####-####-896e####508c, status: RED

/var/log/vmware/applmgmt/applmgmt.log:

YYY-MM-DDTHH:MM:SS PM -03 [10163]ERROR:vmware.appliance.monitoring.stats:Got exception while reading storage stats : 'StatId storage.util.filesystem.core does not exist.'
Traceback (most recent call last):
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/stats.py", line 452, in gatherStats
fsStats = [getFilesystemStats(
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/stats.py", line 452, in <listcomp>
fsStats = [getFilesystemStats(
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/stats.py", line 74, in getFilesystemStats
return getTotalAndUtilStats(
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/stats.py", line 171, in getTotalAndUtilStats
percRaw = reader.getStatValuesRaw(totalKey, start, end)
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/statsMonitor.py", line 369, in getStatValuesRaw
self._validate(statId, startTime, endTime)
File "/usr/lib/applmgmt/monitoring/py/vmware/appliance/monitoring/statsMonitor.py", line 434, in _validate
raise NotFoundException('StatId %s does not exist.' % statId)
vmware.appliance.monitoring.statsMonitor.NotFoundException: 'StatId storage.util.filesystem.core does not exist.'

The /storage/core partition is not displayed when running 'df -h' command:
root@vCenterVM [ ~ ]# df -h
- Filesystem Size Used Avail Use% Mounted on
  devtmpfs 4.0M 0 4.0M 0% /dev
  tmpfs 15G 1.2M 15G 1% /dev/shm
  tmpfs 5.9G 1.3M 5.9G 1% /run
  tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
  /dev/mapper/vg_root_0-lv_root_0 47G 23G 23G 50% /
  /dev/sda3 488M 37M 415M 9% /boot
  /dev/mapper/vg_lvm_snapshot-lv_lvm_snapshot 196G 28K 186G 1% /storage/lvm_snapshot
  tmpfs 15G 4.9M 15G 1% /tmp
  /dev/sda2 10M 2.0M 8.1M 20% /boot/efi
  /dev/mapper/netdump_vg-netdump 9.8G 24K 9.3G 1% /storage/netdump
  /dev/mapper/vtsdb_vg-vtsdb 49G 36M 47G 1% /storage/vtsdb
  /dev/mapper/imagebuilder_vg-imagebuilder 25G 36K 24G 1% /storage/imagebuilder
  /dev/mapper/archive_vg-archive 98G 73G 21G 79% /storage/archive
  /dev/mapper/lifecycle_vg-lifecycle 98G 4.0G 89G 5% /storage/lifecycle
  /dev/mapper/dblog_vg-dblog 25G 545M 23G 3% /storage/dblog
  /dev/mapper/autodeploy_vg-autodeploy 25G 40K 24G 1% /storage/autodeploy
  /dev/mapper/db_vg-db 25G 899M 23G 4% /storage/db
  /dev/mapper/log_vg-log 25G 5.0G 19G 22% /storage/log
  /dev/mapper/vtsdblog_vg-vtsdblog 25G 33M 24G 1% /storage/vtsdblog
  /dev/mapper/updatemgr_vg-updatemgr 98G 5.7G 88G 7% /storage/updatemgr
  /dev/mapper/seat_vg-seat 49G 528M 46G 2% /storage/seat

Cause

vCenter VM storage/core partition is missing.

Resolution

Steps to recreate the /storage/core partition on the vCenter VM

1. Take a snapshot of the vCenter VM.
2. SSH into the vCenter VM.
3. Validate that Hard Disk 2 is using SCSI (0:1).
4. Add a new 25 GB hard disk on SCSI (2:1) to the vCenter VM.
5. Run lsblk and confirm the new 25 GB disk is visible (for example, /dev/sdb).
  - root@vCenterVM [ ~ ]#lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
    sda 8:0 0 10.6G 0 disk
    ├─sda1 8:1 0 4M 0 part
    ├─sda2 8:2 0 10M 0 part /boot/efi
    ├─sda3 8:3 0 512M 0 part /boot
    └─sda4 8:4 0 10G 0 part
    └─vg_root_0-lv_root_0 254:3 0 10G 0 lvm /
    sdb 8:16 0 25G 0 disk <-------------------- new entry
6. Initialize the new disk:
  - pvcreate /dev/sdb
7. Create a volume group:
  - vgcreate core_vg /dev/sdb
8. Create a logical volume:
  - lvcreate -l 100%FREE -n core core_vg
9. Format the logical volume:
  - mkfs.ext4 /dev/core_vg/core
10. Create the mount point and mount the filesystem:
  - mkdir -p /storage/core
  - mount /dev/core_vg/core /storage/core
11. Note down the UUID of the newly created LV from the output of the below command
  - blkid /dev/core_vg/core
12. Update the new UUID in /etc/fstab against the commented entry from Step 7, by uncommenting it
  
  UUID=<PLEASE_REPLACE_WITH_UUID_FROM_STEP11> /storage/core
13. Power off the vCenter VM and delete any existing snapshots.
14. Remove the corrupted Hard Disk 2, re-point the new disk it to the SCSI controller at (0:1) (entry from Step3).
15. Power on the VM. It may boot into emergency mode initially — restart the VM and it should boot normally.
16. Verify the new storage (/storage/core) is visible in vCenter.