4250 Truststore slots tagged 'vasa' could not be migrated to the metadata vdisk.

Explanation

Migration of truststore slots tagged with 'vasa' to the metadata VDisk was attempted but unsuccessful. The first migration attempt happens at upgrade commit time. If it is successful, then no event is raised. If it fails, then the event is raised to allow the user to trigger another attempt.

While the event is unfixed, no maintenance of vasa truststore is possible. This includes adding new certificate bundles, or adding the vasa tag to existing bundles. A vCenter that was registered pre-upgrade, continues to be authenticated by the Embedded VASA Provider while the event is unfixed but new registrations are not supported.

User response

The metadata VDisk was not available when migration was attempted. The user should check the status of the metadata VDisk with lsmetadatavdisk command, and recover the metadata VDisk if necessary. If the user no longer requires the use of vSphere Virtual Volumes (vVols), truststore slots that are tagged with 'vasa' should be deleted. Once the metadata VDisk is online or there are no truststore slots that are tagged with 'vasa', the user must manually fix the event to trigger another migration attempt.