PowerFlex: After deployment of CO and HCI services the migrate vCLS VMs button is missing
Summary: After deploying Compute Only (CO) and Hyperconverged infrastructure (HCI) services using PFxM 3.8.4, the Migrate vCLS VMs button is missing due to a code issue.
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.
Symptoms
- CO services do not go into Lifecycle mode as expected and the Migrate vCLS VMs button is missing under Service Actions on the Service details pane.
- HCI services have the service volumes/datastores created, but the vCLS VMs have not been migrated to them.
- If you attempt to create or map volumes to your service, you get the following error in the logs:
INFO [2023-06-06T06:39:59.835865] 78914: service_deployment.rb:1429:in `block in create_component_thread': Status: Failed_component_vcls/vcenter-vcsa-prod INFO [2023-06-06T06:39:59.848367] 78844: service_deployment.rb:1255:in `block in process_components': An error occurred during the processing of cluster vcls components. ERROR [2023-06-06T06:39:59.851651] 78844: service_deployment.rb:622:in `process': There is no service volume / datastore available! ERROR [2023-06-06T06:39:59.852143] 78844: service_deployment.rb:623:in `process': ["/opt/asm-deployer/lib/asm/provider/cluster/vmware.rb:1803:in `migrate_vcls_vms'", "/opt/asm-deployer/lib/asm/lazy_connection.rb:101:in `block in with_connection'", "/opt/asm-deployer/lib/asm/lazy_connection.rb:86:in `with_connection'", "/opt/asm-deployer/lib/asm/lazy_connection.rb:100:in `block in with_connection'", "/opt/asm-deployer/lib/asm/type/base.rb:413:in `delegate'", "/opt/asm-deployer/lib/asm/type/cluster.rb:200:in `migrate_vcls_vms'", "/opt/asm-deployer/lib/asm/service_deployment.rb:2231:in `process_vcls'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1409:in `block in create_component_thread'"] INFO [2023-06-06T06:39:59.853018] 78844: service_deployment.rb:625:in `process': Status: Error
- Other service actions fail due to the vCLS VMs not being on shared storage as expected.
Cause
The check that PowerFlex Manager performs to identify vCLS VMs does not work because the OS guestId is reporting a value other than expected in some versions of vCenter.
Resolution
To resolve this issue, you must apply the hotfix. Follow these steps to download and install:
-
Download the .zip file attached to this article (The attached file is available only in the English version of the article).
-
Using WinSCP or similar tool, copy the file to /var/tmp on the PowerFlex Manager VM.
-
SSH to PowerFlex Manager and extract the file:
unzip hotfix-3.8.4-vxfm-34640.zip
-
Change to the hotfix directory:
cd vxfm-34640-3.8.4
-
Run the following commands to install the hotfix:
sudo rpm -Fvh Dell-VxFM-*-3.8.4-*.noarch.rpm
-
Reboot your PowerFlex Manager VM:
sudo shutdown -r now
-
Verify that the hotfix was installed:
sudo rpm -qa | grep -i puppet-module-vmware-vcenter sudo rpm -qa | grep -i asm-deployer
Note: Output should show the following versions:
- Dell-VxFM-puppet-module-vmware-vcenter-3.8.4-40.noarch.rpm
- Dell-VxFM-asm-deployer-3.8.4-89.noarch.rpm
Additional Information
- This hotfix is version specific and only applies to PowerFlex Manager 3.8.4.
- This issue is resolved in PowerFlex Manager 3.8.5.
Affected Products
PowerFlex rack, PowerFlex ApplianceAttachments
Article Properties
Article Number: 000215124
Article Type: Solution
Last Modified: 10 Dec 2025
Version: 7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.