VxRail: L'espansione del nodo non riesce nella convalida "PrimaryStorageReadyForExpansionValidator"

Summary: L'espansione dei nodi non riesce al momento della convalida con l'errore "PrimaryStorageReadyForExpansionValidator".

Αυτό το άρθρο ισχύει για Αυτό το άρθρο δεν ισχύει για Αυτό το άρθρο δεν συνδέεται με κάποιο συγκεκριμένο προϊόν. Δεν προσδιορίζονται όλες οι εκδόσεις προϊόντων σε αυτό το άρθρο.
Δείτε άλλους πόρους

Symptoms

L'espansione del nodo non riesce al momento della convalida con l'errore:

General Error
An unknown validation error occurred in PrimaryStorageReadyForExpansionValidator

 

Schermata del messaggio di errore  
Figura 1. Schermata del messaggio di errore 


Quando si visualizza il file Dayone.log oppure shortterm.log, gli host configurati con get_customized_vibs selezionato hanno esito negativo. Questa funzione viene utilizzata per confrontare il nuovo nodo e il nodo configurato.

"2023-10-18 09:30:03,412" microservice.do-host "2023-10-18T09:30:02.599693731Z stderr F 2023-10-18 09:30:02,599 [ERROR] <Dummy-52:140561398021704> esxcli_client2.py run() (154): Error occurred when running: esxcli.software.component.list"
"2023-10-18 09:31:01,413" microservice.do-host "2023-10-18T09:31:01.21374762Z stderr F 2023-10-18 09:31:01,213 [ERROR] <Dummy-60:140561395805768> esxcli_client2.py run() (154): Error occurred when running: esxcli.hardware.platform.get"

"2023-10-18 09:30:05,898" microservice.workflow-engine "2023-10-18T09:30:05.791005812Z stdout F INFO [wfengine.status] task host_customized_driver_validation_False____exp67b67ad3_d786_508bd1f536 failure"
"2023-10-18 09:30:05,898" microservice.workflow-engine "2023-10-18T09:30:05.809971889Z stdout F INFO [wfengine.status] notify {'level': 'step', 'id': 'host_customized_driver_validation', 'state': 'FAILED', 'progress': 97, 'status': {'id': 'host_customized_driver_validation', 'internal_id': 'host_customized_driver_validation_False____exp67b67ad3_d786_508bd1f536', 'internal_family': 'host_customized_driver_validation', 'status': 'FAILED', 'startTime': 1697621394266, 'stage': '', 'params':

{'has_customized_component': False}
, 'error':

{'result': 'FAILED'}
}}"
"2023-10-18 09:30:05,898" microservice.workflow-engine "2023-10-18T09:30:05.863154343Z stdout F INFO [luigi-interface] Informed scheduler that task host_customized_driver_validation_False____exp67b67ad3_d786_508bd1f536 has status FAILED"


Lo script di controllo integrità del nodo è bloccato nella query, il processo del nodo configurato e il registro del controllo integrità del nodo mostra che restituisce 504 Gateway Timeout.

23-10-19 02:59 - DEBUG - curl --unix-socket /var/lib/vxrail/nginx/socket/nginx.sock -H "Content-Type: application/json" http://127.0.0.1/rest/vxm/internal/do/v1/host/query -d '{"query": "{configuredHosts { moid, name, hardware{ sn, psnt, applianceId, model}, runtime{ agent {ready ,backend },  connectionState, powerState, inMaintenanceMode, overallStatus}, summary { config { product { version }}}, config { diskgroup{current{type}},network{vnic{device portgroup mtu interfaceTags}},biosUUID, isPrimary, product {name, version, build} }}}"}'
23-10-19 03:09 - DEBUG - <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>


shortterm.log

"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602210134Z stdout F 2023-10-18 09:29:53,602 ERROR [StorageDeviceService.py:352] get_configured_hosts_model_dg_map: Failed to get current hosts info by do-host graphql."
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602593053Z stdout F 2023-10-18 09:29:53,602 ERROR [validator.py:68] execute: Validator MultiDGConfigurationValidator raise a Exception {'message': ""(vmodl.fault.SystemError) {\n   dynamicType = <unset>,\n   dynamicProperty = (vmodl.DynamicProperty) [],\n   msg = 'A general system error occurred: Too many outstanding operations',\n   faultCause = <unset>,\n   faultMessage = (vmodl.LocalizableMessage) [],\n   reason = 'Too many outstanding operations'\n}"", 'locations': [\{'line': 11, 'column': 9}], 'path': ['configuredHosts', 2, 'config', 'diskgroup', 'options']}"

"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602603034Z stdout F Traceback (most recent call last):"
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602606355Z stdout F   File ""/home/app/common/validator.py"", line 66, in execute"
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602608952Z stdout F     self.perform(*args, **kwargs)"
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602611897Z stdout F   File ""/home/app/multidiskgroupconfigurationvalidator/multi_disk_group_configuration_validator.py"", line 70, in perform"
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.602616418Z stdout F     model_dg_map = StorageDeviceService().get_configured_hosts_model_dg_map()"
...........
...........
Unknown macro: {n   dynamicType = <unset>,n   dynamicProperty = (vmodl.DynamicProperty) [],n   msg = 'A general system error occurred}
"", 'locations': [\{'line': 11, 'column': 9}], 'path': ['configuredHosts', 2, 'config', 'diskgroup', 'options']}"
"2023-10-18 09:29:53,891" microservice.storage-service "2023-10-18T09:29:53.603258112Z stdout F 2023-10-18 09:29:53,603 INFO [utils.py:131] wrapper: log_call 72 return: [{'result': {'result': 'FAILED', 'name': 'MultiDGConfigurationValidator', 'context':

Unknown macro: {'invalid_fields'}
, 'errors': [{'type': 'THOROUGH-VALIDATOR', 'field': 'General Error ', 'code': 'config.validation.common.unknown.error', 'placeholders': ['MultiDGConfigurationValidator'], 'message': 'An unknown validation error occurred in MultiDGConfigurationValidator.'}], 'warnings': []}}]"

Cause

Questo problema si verifica quando un'attività di routine specifica (vScheduleCheckVsanConfigLro) viene avviato quando la coda dei processi LRO di vCenter è già piena di attività in coda. Ciò fa sì che i servizi vpxd su vCenter smettano di rispondere. Ciò può ulteriormente comportare l'impossibilità per do-host di ottenere informazioni dal nodo configurato.

Per ulteriori informazioniQuesto link ipertestuale indirizza a un sito web esterno a Dell Technologies., consultare l'articolo VMware Il servizio vpxd vCenter Server si arresta in modo anomalo a causa di "Too many outstanding operations" (89742) (Link esterno).

Resolution

Questo problema è stato risolto in vCenter Server 7.0 Update 3i (numero di build 20845200).

Soluzione:
Modificare i parametri particolari config.vmacore.threadPool.TaskMax in vCenter a un valore superiore o simile a 200.

Riavviare tutti i servizi su vCenter e vpxa e hostd servizi su ciascun host. Mettere ogni host in modalità di manutenzione prima di eseguire i comandi su di esso.

On ESXi hosts:
#Rolling restart the ESXi host daemon and vCenter Agent services using these commands:
/etc/init.d/hostd restart
/etc/init.d/vpxa restart

On vCenter
#take a snapshot of vcenter server
#service-control --stop --all
#service-control --start --all

Επηρεαζόμενα προϊόντα

VxRail
Ιδιότητες άρθρου
Article Number: 000218805
Article Type: Solution
Τελευταία τροποποίηση: 19 Φεβ 2026
Version:  3
Βρείτε απαντήσεις στις ερωτήσεις σας από άλλους χρήστες της Dell
Υπηρεσίες υποστήριξης
Ελέγξτε αν η συσκευή σας καλύπτεται από τις Υπηρεσίες υποστήριξης.