VxRail: vCLS cannot deploy on vCenter after cluster rebooted
Сводка: vSphere Cluster Services (vCLS) cannot deploy on vCenter after the cluster has been rebooted.
Данная статья применяется к
Данная статья не применяется к
Эта статья не привязана к какому-либо конкретному продукту.
В этой статье указаны не все версии продуктов.
Симптомы
vSphere Cluster Services (vCLS) cannot deploy on vCenter after the cluster has been rebooted.
- Tried to set vCLS with retreat mode and disable it, but vCLS still cannot deploy on any ESXi host.
- In the vCenter task list, can see vCenter continue to deploy vCLS and then destroy it.
2024-03-28T03:08:14.942Z | ERROR | cluster-agent-0 | AuditedJob.java | 106 | JOB FAILED: [#1733615521] DeployVmJob(ClusterAgent(ID: 'Agent:cef3bd5a-3886-40a0-99eb-31b2b6bc677f:null')) com.vmware.eam.job.DeployVmJob$DeployVmJobFailure: Can't provision VM for ClusterAgent(ID: 'Agent:cef3bd5a-3886-40a0-99eb-31b2b6bc677f:null') due to lack of suitable datastore./var/log/vmware/vpxd/vpxd.log:
2024-03-28T13:31:37.037+08:00 warning vpxd[12577] [Originator@6876 sub=VmProv opID=10847a9b] Unable to lookup ds for disk
- We followed the Broadcom KB | https://knowledge.broadcom.com/external/article/318191/vsphere-drs-functionality-was-impacted-d.html
to reset the STS certificate but still same error.
- Ran VCF Diagnostic Tool for vSphere (VDT) and it shows a DNS warning.
Причина
DNS is unreachable and causes this issue.
Разрешение
Check your DNS settings.
Ensure to use nslookup to resolve vCenter and all ESXi hosts FQDNs.
Ensure to use nslookup to resolve vCenter and all ESXi hosts FQDNs.
Свойства статьи
Номер статьи: 000226449
Тип статьи: Solution
Последнее изменение: 02 Jul 2024
Версия: 1
Получите ответы на свои вопросы от других пользователей Dell
Услуги технической поддержки
Проверьте, распространяются ли на ваше устройство услуги технической поддержки.