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

从设备中删除服务后，服务部署中使用的两个节点中的其中一个节点进入“已部署”状态。
从设备中删除服务后节点的预期状态：准备


Caused by thin-deployer health monitoring code code：
代码删除了定期库存更新（从旧代码逻辑中，我们将设备库存更新到相同的状态）- 这很好，但不是必需的，因为这会更新设备的陈旧数据条目。asm-core 将设备状态从 “Deployed” 更改为 “Ready” 并且运行状况检查再次将其更新为 “Deployed”

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.