Dell VxRail: Node-Erweiterung schlägt bei Validierung mit dem Fehler "PrimaryStorageReadyForExpansionValidator" fehl

Summary: Die Node-Erweiterung schlägt bei der Validierung mit dem Fehler "PrimaryStorageReadyForExpansionValidator" fehl.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Die Node-Erweiterung schlägt bei der Validierung mit dem folgenden Fehler fehl: 
General Error
An unknown validation error occurred in PrimaryStorageReadyForExpansionValidator
 
Screenshot der Fehlermeldung
Abbildung 1: Screenshot der Fehlermeldung 

Beim Anzeigen von Dayone.log oder shortterm.log schlägt die Konfiguration der Hosts mit get_customized_vibs fehl. Dies wird zum Vergleich des neuen Node und des konfigurierten Node verwendet. 
"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"

Das Skript für die Node-Integritätsprüfung bleibt bei der Abfrage, dem konfigurierten Node-Prozess hängen und das Node-Integritätsprüfungsprotokoll zeigt an, dass es 504 Gateway-Timeout zurückgibt. 
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

Dieses Problem tritt auf, wenn eine bestimmte Routineaufgabe (vScheduleCheckVsanConfigLro) gestartet wird, wenn die LRO-Jobwarteschlange des vCenter bereits voll mit Aufgaben in der Warteschlange ist. Dies führt dazu, dass vpxd-Services auf dem vCenter nicht mehr reagieren. Dies kann außerdem dazu führen, dass der Do-Host keine Informationen vom konfigurierten Node abruft.

Lesen Sie den VMware-Artikel vCenter Server vpxd service crashes due to "Too many outstanding operations" (89742) (Zu viele ausstehende Vorgänge) für weitere Informationen Dieser Hyperlink führt Sie zu einer Website außerhalb von Dell Technologies..

Resolution

Dieses Problem wurde in vCenter Server 7.0 Update 3i (Build-Nummer 20845200) behoben.

Problemumgehung:
Ändern Sie die parameter config.vmacore.threadPool.TaskMax in vCenter auf einen Wert über oder ähnlich 200.

Starten Sie alle Services in vCenter und die vpxa- und hostd-Services auf jedem Host neu. Versetzen Sie jeden Host in den Wartungsmodus, bevor Sie die Befehle darauf ausführen. 
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

Affected Products

VxRail
Article Properties
Article Number: 000218805
Article Type: Solution
Last Modified: 14 Nov 2023
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.