NCP-EUC · Question #87
The administrator has checked the logs to see the below output: The API call sent to the VM via XD Plugin at [CDF logs]: Following that while the VM is being powered OFF, query for the current VM…
The correct answer is D. Create a Scheduled reboot cycle. The logs reveal a race condition or state-conflict issue: after a power-off API call is sent via the XD Plugin, subsequent state queries intermittently return 'ON' and then a conflicting state that is simultaneously reported as both ON and OFF. This typically occurs when…
Question
The administrator has checked the logs to see the below output:
The API call sent to the VM via XD Plugin at [CDF logs]:
Following that while the VM is being powered OFF, query for the current VM state results in ON (the administrator sees a number of these until the VM is marked as power OFF) logs]:
Upon further review the administrator notices in COF logs, after a number of queries for the machine state, one results in a conflicting state, reporting the Power state as ON anc OFF [CDF logs) HCM should the administrator resolve the issue?
Exhibits
Options
- AIncrease the distribution time in Machine Update Rollout
- BDecrease the distribution time in Machine Update Rollout
- CDelete Scheduled reboot settings
- DCreate a Scheduled reboot cycle.
How the community answered
(26 responses)- A12% (3)
- B4% (1)
- C4% (1)
- D81% (21)
Explanation
The logs reveal a race condition or state-conflict issue: after a power-off API call is sent via the XD Plugin, subsequent state queries intermittently return 'ON' and then a conflicting state that is simultaneously reported as both ON and OFF. This typically occurs when machines are being powered off without a structured, orderly reboot/power cycle process, causing the hypervisor and Citrix broker to disagree on the machine state. Creating a Scheduled Reboot Cycle enforces controlled, predictable power state transitions for VDI machines, ensuring they cycle cleanly through defined power states and eliminating the race condition that produces conflicting state reports. Simply adjusting distribution time (Options A/B) addresses rollout timing, not power state conflicts, and deleting scheduled reboots (Option C) would remove management rather than fix the issue.
Topics
Community Discussion
No community discussion yet for this question.

