PowerFlex 4.X: Storage Only Deployment Fails to Finish zypper update
Summary: PowerFlex Manager is failing to complete a SO Deployment RG when performing the 'zypper update' task.
Symptoms
A Storage Only Deployment RG can fail when the deployment automation attempts to upgrade the SO Hosts OS with the IC repo performing an 'zypper update --allow-vendor-change --allow-downgrade --recommends -y' task.
exception.log:
#<RuntimeError: VxFlexOS component, scaleio-block-legacy-gateway, does not have a successful server to build with> /opt/asm-deployer/lib/asm/service_deployment.rb:4149:in `process_scaleio' /opt/asm-deployer/lib/asm/service_deployment.rb:1539:in `block in create_component_thread'
scaleio-block-legacy-gateway_exception.log:
#<RuntimeError: VxFlexOS component, scaleio-block-legacy-gateway, does not have a successful server to build with> /opt/asm-deployer/lib/asm/service_deployment.rb:4149:in `process_scaleio' /opt/asm-deployer/lib/asm/service_deployment.rb:1539:in `block in create_component_thread'
rackserver-XXXXXXX_exception.log:
Below details where the failure was encountered: "rackserverhost1___8.out"
# /opt/asm-deployer/lib/asm/service_deployment.rb:1934:in `process_ansible_errors' /opt/asm-deployer/lib/asm/service_deployment.rb:1877:in `block in process_ansible_playbook' /opt/asm-deployer/lib/asm/private_util.rb:1333:in `block in wait_until_available' /opt/asm-deployer/lib/asm.rb:792:in `wait_on_counter_threshold' /opt/asm-deployer/lib/asm/private_util.rb:1332:in `wait_until_available' /opt/asm-deployer/lib/asm/service_deployment.rb:1835:in `process_ansible_playbook' /opt/asm-deployer/lib/asm/type/base.rb:726:in `process_ansible' /opt/asm-deployer/lib/asm/type/server.rb:2528:in `provision_server!' /opt/asm-deployer/lib/asm/service_deployment.rb:5530:in `process_server_with_types' /opt/asm-deployer/lib/asm/service_deployment.rb:3171:in `process_server' /opt/asm-deployer/lib/asm/service_deployment.rb:1539:in `block in create_component_thread'
rackserverhost1___8.out:
Below shows the 'zypper update' command failing – specifying conflicting package "util-linux-2.36.2-2.29.x86_64"
"Checking for file conflicts: [............error]", "Detected 1 file conflict:", "", "File /usr/share/bash-completion/completions/lsblk", " from install of", " util-linux-systemd-2.37.2-150400.8.29.1.x86_64 (sles_extras)", " conflicts with file from package", " util-linux-2.36.2-2.29.x86_64 (@System)", "", "File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.", "Continue? [yes/no] (no): no"
Impact
Unable to deploy SO Resource Groups.
Cause
This issue occurs when the Storage Only Template is configured with an outdated ISO. PFxM evaluates the host packages and identifies them as non-compliant, triggering an upgrade attempt. However, because the Storage Only hosts lack the expected packages, a conflict arises, causing the deployment to fail.
Resolution
- Located the IC catalog file and extract it out.
- Upload the ISO to PFxM
- Settings → Repositories → OS Image Repositories → Add
- Select the ISO image we extracted in Step 1
- Give the ISO a unique name. Example:" PowerFlex Embedded OS SLES 15.4"
- Edit the template and change the OS Image to the Image in Step 4.
- Lifecycle → SO-Nodes Template → Modify Template → OS Image
- Save the template
- Clean up the deployment/expansion if needed and start a fresh deployment/expansion.
Impacted Version
PFMP 4.x