Anyone get a lot of powerstate unknowns daily with DAAS ??? . The affected VDA's are running on Citrix Hypervisor 8.2 CU1 hosts on prem and i dont see any Hypervisor connection alerts and get-brokerhypervisorconnection | select name,state shows them all "On" event logs on the Cloud connectors dont suggest any connection issues to citrix cloud and its not all VDA's on the same host that are affected. If i run a test hosting connection/resources within cloud studio the tests all come back good. I restart the Remote HCL service / Remote broker service on the cloud connector the power states go back to normal. I have ran the below script in past when i get power states unknown but that is on prem CVAD not DAAS https://github.com/citrix/Powershell-Scripts/tree/master/XAXD/VMsInUnknownPowerState

IME, the DaaS console is slow to update that status. I see the same power state for both our on-prem (VMware) and cloud (Azure) for a while in DaaS before it eventually updates, whereas those respective consoles show the state in a much more timely manner.

I thought it was a GUI bug at first but when i run get-brokermachine | where {$_.powerstate -eq "unknown} via remote powershell sdk it shows them as unknown

I had this a few years back, it was on nutanix though, resolved by AHV updates. not worked with Citrix XenServer in years, is 8.2 CU1 as high as you can go?

Had this last year. There was a bug introduced with a Citrix hypervisor patch that triggered another bug in the cvad service cloud connectors. Basically the CC’s would poll hypervisor and not retry if hypervisor reported it was busy.. Manifested itself as regular bootstorm showing large number of machines with a status of registered but powered OFF in DaaS, trying (and failing) to match users to one of those machines. On Hypervisor all the machines were running. We had to run a PS command to force DaaS to retry communication about 3 times a day until cloud team added additional polling to the CCs.