PowerFlex 4.x PowerFlex GatewayとMDMの再構成中にMDMクラスターとの接続が失われる

• MDMの再構成操作が失敗し、PowerFlexゲートウェイに接続できないと表示されます。
• PowerFlex Gatewayのインベントリー操作は、MDMの再構成操作後に失敗し始めます。
• Resourceペインで、PowerFlex Gatewayに「PowerFlex unreachable」または「unhealthy」と表示されます
• scaleio.log/scaleio_trace.logでは、次のようなエラーが報告されます。これは、SwitchMdmOwnership リクエストの後に開始されます。

2022-07-13 17:28:37,810 [https-openssl-nio-443-exec-5] DEBUG c.e.s.s.s.ConnectionServiceImpl - Send request SwitchMdmOwnership to MDM
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Cipher suites supported by server: [TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256, TLS_CHACHA20_POLY1305_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Default or requested cipher suites: [TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256]
2022-07-13 17:28:37,811 [https-openssl-nio-443-exec-5] DEBUG c.e.e.n.c.LayeredProtocolConnection - Intersection of the supported and requested cipher suites: [TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256]
2022-07-13 17:28:37,813 [https-openssl-nio-443-exec-5] DEBUG c.e.e.u.s.X509TrustManagerExtended - Trusting all the certificates
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-1-ReceiveLoop-1293774449] ERROR c.e.e.n.c.LayeredProtocolConnection - LPC-1293774449 #9dc0fdda29f79ec8 [192.168.150.26:8611]: IOException in receive loop: java.net.SocketException: Connection reset
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-1-ReceiveLoop-1293774449] INFO  c.e.e.n.c.LayeredProtocolConnection - LPC-1293774449 #9dc0fdda29f79ec8 [192.168.150.26:8611]: Attempting to re-connect
2022-07-13 17:28:37,975 [https-openssl-nio-443-exec-5] DEBUG c.e.s.s.s.ConnectionServiceImpl - Got rc SUCCESS for command SwitchMdmOwnership
2022-07-13 17:28:37,975 [command-service-0-ReceiveLoop-1271882087] ERROR c.e.e.n.c.LayeredProtocolConnection - LPC-1271882087 #858e689a28e91ed7 [192.168.150.26:8611]: IOException in receive loop: java.net.SocketException: Connection reset

この問題を解決するには、ユーザーがPowerFlex ゲートウェイ ポッドを再起動する必要があります。

次のコマンドを使用して、PowerFlexゲートウェイを再起動できます。

kubectl delete pod -n powerflex $(kubectl get pods -A | grep block-legacy-gateway | grep -v mds | grep -i running | awk ' {print $2}')