VM's Power State Does Not Update And Shows As "Unknown" After vCenter Server Reboots

VM's Power State Does Not Update And Shows As "Unknown" After vCenter Server Reboots

book

Article ID: CTX238157

calendar_today

Updated On:

Description

  • For maintenance purpose you reboot the  vCenter server. During the vCenter Server reboot, power managed VMs that resides on VMware Hypervisor show power state as "Unknown". This is an expected behaviour since the host connection is unavailable.
 
  • However, when the vCenter server goes alive after reboot, the hosting connection remains unavailable and those VMs' power state remains "Unknown" 
 
  • Restarting the Citrix Hosting Service or turning on and turning off and turning On the Maintenance mode of the hosting connection updates the power state of the machines.
Note:- This can impact the desktop\application launch

Resolution

The issue has been fixed under LD0355 in Citrix Virtual Apps and Desktops 7 1811.

When you manually restart the vCenter Server, the status of the power managed virtual machines that reside on the VMware hypervisor might become Unknown. The status becomes Unknown because the host connection is not available. After the vCenter Server restart completes, the virtual machine’s power state remains Unknown instead of restoring automatically. [LD0355]

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/whats-new/fixed-issues.html

Problem Cause

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

 When vCenter server goes alive after reboot i.e "https://<vCenter FQDN>/sdk" becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception "The session is not authenticated.".

CDF Traces from Delivery Controller

,BrokerHostingPlugin,,0,,1,Information,"Attempting connection",""
,BrokerHostingPlugin,,0,,1,Information,"***** Get Hypervisor Certificate for Connection to 'https://<vCenter FQDN>/sdk' *****",""
,BrokerHostingPlugin,,0,,1,Information,"Certificate is untrusted: False",""
,BrokerHostingPlugin,,0,,1,Information,"Time elapsed to get the hypervisor certificate: xxms",""
,BrokerHostingPlugin,,0,,1,Information,"***** Login Connection - 0 to 'https://<vCenter FQDN>/sdk' as '#login_name#' *****",""
,BrokerHostingPlugin,,0,,1,Information,"VMware plugin initialisation times: create service xms, content time xxxms, total xxxms",""
,BrokerHostingPlugin,,0,,1,Information,"Connected to 'VMware vCenter Server #vCenter version info#'",""
,BrokerHostingPlugin,,0,,1,Error,"System.Web.Services.Protocols.SoapException: The session is not authenticated.
,BrokerHostingPlugin,,0,,1,Information,"Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.
,BrokerHostingPlugin,,0,,1,Information,"Connection is still down",""
,BrokerHostingPlugin,,0,,1,Information,"Sleeping for 00:00:30 before trying to reconnect again",""

Issue/Introduction

VM's Power State Does Not Update And Shows As "Unknown" After vCenter Server Reboots.