Customers may observe the following warning messages in vCenter events or tasks associated with SSP worker node virtual machines:
The object or item referred to could not be found
Invalid configuration for device '0': Cannot remove virtual disk from the virtual machine because it or one of its parent disks is part of a snapshot
These messages typically appear during container volume detach operations performed by the platform and may be seen across multiple SSP worker nodes. The warnings may appear intermittently in the vCenter task history while storage reconciliation activities are occurring.
SSP 5.X
SSP runs a Kubernetes-based platform on vSphere, where persistent volumes used by pods are managed through the vSphere CSI driver.
During normal Kubernetes storage lifecycle operations, the CSI controller performs volume detach operations when pods terminate or volumes are remounted.
The warning messages occur due to the following conditions:
Object Not Found Warning
The object or item referred to could not be found
This occurs when the Kubernetes platform has already removed or updated the volume reference while a corresponding detach task is still being processed in vCenter. When the vCenter task attempts to detach the disk, the referenced object may already be removed, resulting in this warning. This behavior is part of the reconciliation process and does not affect platform functionality.
Snapshot Dependency Warning
Invalid configuration for device '0': Cannot remove virtual disk from the virtual machine because it or one of its parent disks is part of a snapshot
This occurs when a worker node virtual machine has an active snapshot at the time a container volume detach operation is attempted.Because the virtual disk is part of a snapshot chain, vSphere temporarily prevents the disk from being removed. The detach operation is retried by the CSI controller once the snapshot dependency is cleared or reconciliation occurs.
No action is required if the SSP platform and Kubernetes workloads are functioning normally.
These warning messages are expected artifacts of Kubernetes CSI storage reconciliation and may appear temporarily during container volume detach operations.