PowerFlex 4.x - 新增現有 RG 失敗，並顯示 VXFM0004 或 VXFM00611

Summary: 新增現有服務失敗，並顯示 VXFM0004 或 HTTP 500 內部伺服器錯誤。 先前從 PFxM 裝置移除服務後，有一個 （或多個） 節點處於「已部署」狀態。 服務從裝置移除後節點的預期狀態：䙼

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

在之前刪除資源組，現在重新添加該資源組后，UI 顯示： 

An error occurred.  Expand the list to view the details of the error. (500)
The operation cannot be performed because of an internal issue. (VXFM0004)
image.pngasmManager.log顯示類似以下內容：

2023-07-18 04:05:14,981 [https-jsse-nio-9080-exec-5] (ServiceTemplateComponentService.java:75) [DEBUG] filter: (serviceTemplate.templateId ne "ad43fce5-9a80-466e-9ebe-8bb5
002faae8") and (type eq "SCALEIO") and (asmGUID eq "scaleio-block-legacy-gateway") and (parameters.value eq "PD-1") and (serviceTemplate.deployment notnull)
2023-07-18 04:05:14,981 [https-jsse-nio-9080-exec-5] (ServiceTemplateComponentService.java:76) [DEBUG] sort: name
2023-07-18 04:05:14,981 [https-jsse-nio-9080-exec-5] (ServiceTemplateComponentService.java:77) [DEBUG] offset: 0 limit: 1
2023-07-18 04:05:15,089 [https-jsse-nio-9080-exec-5] (DeploymentService.java:1636) [ERROR] Device Reservation for deployment 82ecd3ee-0234-47fe-b33c-f61d15190834 failed. R
olling back attached devices and their states
2023-07-18 04:05:15,144 [https-jsse-nio-9080-exec-5] (BrownfieldService.java:3162) [ERROR] Exception occurred while validating existing service
com.dell.asm.rest.common.exception.LocalizedWebApplicationException: HTTP 500 Internal Server Error
        at com.dell.asm.asmcore.asmmanager.app.rest.DeploymentService.updateFromComponentValues(DeploymentService.java:1582) ~[classes!/:?]
        at com.dell.asm.asmcore.asmmanager.app.rest.DeploymentService$$FastClassBySpringCGLIB$$fadfdd18.invoke(<generated>) ~[classes!/:?]
        at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.27.jar!/:5.3.27]
        at org.springframework.aop.framework.CglibAopProxy.invokeMethod(CglibAopProxy.java:386) ~[spring-aop-5.3.27.jar!/:5.3.27]
        at org.springframework.aop.framework.CglibAopProxy.access$000(CglibAopProxy.java:85) ~[spring-aop-5.3.27.jar!/:5.3.27]
        at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:704) ~[spring-aop-5.3.27.jar!/:5.3.27]
        at com.dell.asm.asmcore.asmmanager.app.rest.DeploymentService$$EnhancerBySpringCGLIB$$53f63bf9.updateFromComponentValues(<generated>) ~[classes!/:?]
        at com.dell.asm.asmcore.asmmanager.app.rest.BrownfieldService.validateExistingService(BrownfieldService.java:2781) [classes!/:?]
        at com.dell.asm.asmcore.asmmanager.app.controller.BrownfieldController.validateExistingService(BrownfieldController.java:130) [classes!/:?]
        at com.dell.asm.asmcore.asmmanager.app.controller.BrownfieldController$$FastClassBySpringCGLIB$$b2683910.invoke(<generated>) [classes!/:?]
        at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) [spring-core-5.3.27.jar!/:5.3.27] 
 

Cause

從設備中刪除服務後，服務部署中使用的兩個節點中的一個節點進入“已部署”狀態。
服務從裝置移除後節點的預期狀態：䙼


由精簡部署程式健全狀況監控代碼所造成：
代碼刪除了定期清單更新（從舊代碼邏輯中，我們將設備清單更新為相同狀態） - 這很好，但不是必需的，因為這會更新設備的過時數據條目。當裝置狀態由 asm-core 從「已部署」變更為「就緒」，且執行狀況檢查再次將其更新為「已部署」時

Resolution

  1. 從資源清查移除個別節點
  2. 重新發掘
  3. 繼續「新增現有資源群組」 

 

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