NCP-MCI-6.10 · Question #133
What would cause an LCM pre-check event with the test_esx_entering_mm_pinned_vms check during an AOS upgrade?
The correct answer is D. Affinity rules are configured to prevent VM migration. The test_esx_entering_mm_pinned_vms LCM pre-check fails when VM-to-host affinity rules prevent virtual machines from being evacuated off a host that must enter maintenance mode during an AOS upgrade.
Question
What would cause an LCM pre-check event with the test_esx_entering_mm_pinned_vms check during an AOS upgrade?
Options
- AHA priority settings are misconfigured.
- BHost has insufficient memory.
- CVMs on the host have high CPU usage.
- DAffinity rules are configured to prevent VM migration.
How the community answered
(24 responses)- B4% (1)
- C4% (1)
- D92% (22)
Why each option
The test_esx_entering_mm_pinned_vms LCM pre-check fails when VM-to-host affinity rules prevent virtual machines from being evacuated off a host that must enter maintenance mode during an AOS upgrade.
HA priority settings control VM restart behavior after a host failure but do not pin VMs to specific hosts, so they would not trigger this particular pre-check.
Insufficient host memory would trigger a resource-related pre-check, not the test_esx_entering_mm_pinned_vms check, which specifically targets VM migration restrictions.
High CPU usage on VMs does not restrict their ability to migrate between hosts and would not cause this affinity-focused pre-check to fail.
VM-to-host affinity rules 'pin' specific VMs to a host, preventing vSphere from live-migrating them to other hosts during maintenance mode entry; because the host cannot be safely evacuated, the LCM pre-check named test_esx_entering_mm_pinned_vms detects these pinned VMs and blocks the upgrade until the affinity rules are removed or modified.
Concept tested: LCM pre-check failure due to VM-to-host affinity rules blocking maintenance mode
Topics
Community Discussion
No community discussion yet for this question.