Hi, Aaron-- In 2.5.3, we collect new information about the disks in the trees to help manage the disk chain. When we can't get the information for disks on a machine on a given host, we prevent deployments onto that host until we can; that is what you are seeing. The issue should go away once all the hosts are enabled after upgrade.