Falha na adição de RG existente do PowerFlex 4.x com o erro "O componente de cluster do VCENTER não tem um servidor bem-sucedido com o qual construir"

Summary: A adição de um grupo de recursos (RG) existente no PowerFlex Manager falha e informa que o RG está em um estado crítico.

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

  • Falha ao adicionar RG existente 
  • O RG mostra estado crítico
  • O status Associated Resource mostra "Deployment Failed" na guia Resources
  • O recurso PowerFlex Gateway (GW) pode estar no estado "Unreachable"
  • O erro relatado nos estados do log de implementação "O componente de cluster do VCENTER_FQDN não tem um servidor bem-sucedido com o qual criar"
  • Os logs de implementação relatam um IP de destino em branco quando util.rb tenta executar o comando esxcli
    • Exemplo: Executando esxcli 600 env VI_PASSWORD=****** esxcli -s -u root

 

 

deployment.log 
DEBUG [2025-05-19T20:00:08.463271] 222264: type/base.rb:167:in `db_status': deployment status for certname: rackserver-####### component: 0df74c6b-9923-4142-8833-98ac9eabd4f4 deployment: 2caa81fa9668b3f20196b2fbccd555f9 is '{:deployment_status=>"pending"}'
INFO  [2025-05-19T20:00:08.463688] 222264: type/server.rb:3600:in `block in esxi_ready?': rackserver-#######: Checking if ESXi is ready
 
****
DEBUG [2025-05-19T20:00:08.464034] 222264: util.rb:190:in `esxcli': rackserver-#######: Executing esxcli 600 env VI_PASSWORD=****** esxcli -s  -u root
****
 
INFO  [2025-05-19T20:00:08.464531] 222264: service_deployment.rb:1531:in `block in create_component_thread': Status: Failed_component_server/rackserver-#######
DEBUG [2025-05-19T20:00:08.489312] 221708: service_deployment.rb:320:in `is_volume_scale_up?': No storage components in current deployment.
INFO  [2025-05-19T20:00:08.504164] 221708: service_deployment.rb:1338:in `block in process_components': Finished post-processing for components of type SERVER
INFO  [2025-05-19T20:00:08.529030] 221708: service_deployment.rb:1267:in `block in process_components': Processing components of type CLUSTER_POST_OPS
DEBUG [2025-05-19T20:00:08.554874] 221708: service_deployment.rb:320:in `is_volume_scale_up?': No storage components in current deployment.
INFO  [2025-05-19T20:00:08.555466] 222872: service_deployment.rb:1457:in `block in create_component_thread': Processing component VCENTER_FQDN
INFO  [2025-05-19T20:00:08.565962] 222872: service_deployment.rb:3840:in `process_cluster_post_ops': Processing cluster component: VCENTER_FQDN
INFO  [2025-05-19T20:00:08.566381] 222872: service_deployment.rb:1531:in `block in create_component_thread': Status: Failed_component_cluster_post_ops/VCENTER_FQDN
DEBUG [2025-05-19T20:00:08.595147] 221708: service_deployment.rb:320:in `is_volume_scale_up?': No storage components in current deployment.
INFO  [2025-05-19T20:00:08.595637] 221708: service_deployment.rb:1351:in `block in process_components': VXFM011::An error occurred during the processing of cluster_post_ops components.
ERROR [2025-05-19T20:00:08.622036] 221708: service_deployment.rb:653:in `process': Cluster component for vcenter-VCENTER_FQDN does not have a successful server to build with
 
Rackserver-#######_exception.log: 
#<TypeError: no implicit conversion of nil into String>

 

Impacto

O grupo de recursos não foi adicionado.

Cause

Existe uma diferença de tempo maior que 30 s entre os MDMs do Manager e as VMs de gerenciamento (MVMs) do PowerFlex Manager.

Resolution

Investigue e resolva o problema de distorção de horário nos servidores afetados. Analise o status do serviço chronyd e verifique a integridade/conectividade com os servidores NTP designados.

Depois de garantir que o horário seja sincronizado entre os MDMs/MVMs, pode ser necessário reiniciar o pod do gateway.

 

Exemplo de solução de problemas:

  • "chronyc tracking" - Este comando verifica o status geral de sincronização do sistema. Um status de salto "Normal" significa que o relógio do sistema está sincronizado e não há problemas com a cronometragem.
chronyc tracking
Reference ID    : 0E0E0E12 ( 30.30.30.2)
Stratum         : 11
Ref time (UTC)  : Mon Aug 12 20:41:25 2024
System time     : 0.000000200 seconds slow of NTP time
Last offset     : -0.000001402 seconds
RMS offset      : 0.000014281 seconds
Frequency       : 86.862 ppm slow
Residual freq   : -0.000 ppm
Skew            : 0.026 ppm
Root delay      : 0.000198145 seconds
Root dispersion : 0.000033342 seconds
Update interval : 64.4 seconds
Leap status     : Normal

 

  • "chronyc sources -v" - Este comando fornece detalhes sobre os servidores NTP que estão sendo usados e seu status. Ter o ^ confirma que o sistema está usando um servidor NTP externo para sincronização de horário
chronyc sources -v
  
  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^*  30.30.30.2                  10   6   377    33  -2137ns[-3539ns] +/-  103us

 

Versões afetadas

PowerFlex Manager 4.x

 

Article Properties
Article Number: 000325442
Article Type: Solution
Last Modified: 29 May 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.