PowerFlex Management Platform - LAG Not Created On Existing DvSwitch's When Using Partial Network Automation (PNA)

If dvSwitches are created ahead of time in VC without LAG and the template calls for creating LAG, it will not be created.

PowerFlex 4.5.x automation script does not create LAG on dvSwitches if the template points to existing dvSwitches without LAG.

Deployment script fails

• Confirmation that all switch settings are correct:
  • Dell OS10 switch port-channels / VLT
  • Cisco port-channel
• After the resource group script fails, the user manually creates a lag in VC and migrates to it, a retry on the resource group is completed successfully.

The following is seen in thin-deployer logs: 

exception.log:

#<RuntimeError: env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib 

INFO [2023-11-14T19:54:02.015289] 64760: service_deployment.rb:1351:in `block in process_components': VXFM011::An error occurred during the processing of cluster components.
ERROR [2023-11-14T19:54:02.038406] 64760: service_deployment.rb:653:in `process': env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/puppetlabs/puppet/bin:/opt/puppetlabs/bin puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources --always-override vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt failed; output in /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.out
ERROR [2023-11-14T19:54:02.038551] 64760: service_deployment.rb:654:in `process': ["/opt/dependencies/dell-asm-util/lib/asm/util.rb:398:in `block in run_command_streaming'", "/opt/jruby/jruby-9.3.9.0/lib/ruby/stdlib/open3.rb:219:in `popen_run'", "/opt/jruby/jruby-9.3.9.0/lib/ruby/stdlib/open3.rb:101:in `popen3'", "/opt/dependencies/dell-asm-util/lib/asm/util.rb:366:in `block in run_command_streaming'", "org/jruby/RubyIO.java:1148:in `open'", "/opt/dependencies/dell-asm-util/lib/asm/util.rb:365:in `run_command_streaming'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1673:in `block in process_generic'", "/opt/asm-deployer/lib/asm/private_util.rb:1251:in `block in wait_until_available'", "/opt/asm-deployer/lib/asm.rb:762:in `wait_on_counter_threshold'", "/opt/asm-deployer/lib/asm/private_util.rb:1250:in `wait_until_available'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1620:in `process_generic'", "/opt/asm-deployer/lib/asm/type/base.rb:616:in `process_generic'", "/opt/asm-deployer/lib/asm/provider/cluster/vmware.rb:885:in `provision_cluster!'", "/opt/asm-deployer/lib/asm/type/base.rb:441:in `delegate'", "/opt/asm-deployer/lib/asm/type/cluster.rb:25:in `provision_cluster!'", "/opt/asm-deployer/lib/asm/service_deployment.rb:3895:in `process_cluster'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1511:in `block in create_component_thread'"]
INFO [2023-11-14T19:54:02.038907] 64760: service_deployment.rb:656:in `process': Status: Error


vcenter-xxxxx___2:

Debug: Found dvswitch: VmwareDistributedVirtualSwitch 'brp-dpf-vdi-thy-01-dvs-fe'
Error: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-fe during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-fe]/vmnic2: change from 'vSwitch0' to 'brp-dpf-vdi-thy-01-dvs-fe-Uplinks-27' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-fe during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-be]/vmnic3: change from to 'brp-dpf-vdi-thy-01-dvs-be-Uplinks-25' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration
Error: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration
Error: /Stage[main]/Asm::Resource_wrapper/Vc_dvswitch_migrate[brp-dpf-hci-thy-dn508-u11.hhsprod.mgmt:brp-dpf-vdi-thy-01-dc/brp-dpf-vdi-thy-01-dvs-be]/vmnic5: change from to 'brp-dpf-vdi-thy-01-dvs-be-Uplinks-25' failed: Could not locate specified LACP lag lag1 on dvswitch brp-dpf-vdi-thy-01-dvs-be during vmk and vmnic migration	


asm-deployer-init.log:

ERROR [2023-11-14T19:54:02.045020] 64760: util.rb:26:in `block in execute_async': env --unset=RUBYOPT --unset=GEM_HOME --unset=RUBYLIB --unset=GEM_PATH --unset=BUNDLE_BIN_PATH RUBYLIB=/opt/service/lib:/opt/asm-deployer/lib:/opt/puppetlabs/puppet/lib:/opt/dependencies/dell-asm-util/lib PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/puppetlabs/puppet/bin:/opt/puppetlabs/bin puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/resources --always-override vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt failed; output in /opt/Dell/ASM/deployments/8aaa81dd8bba32bc018bca3cf8191bff/vcenter-brp-dpf-vdi-thy-01-vc.hhsprod.mgmt__2.out

Impact 

Deployment script fails if existing dvSwitch doesn't already have an LAG configured.

If the user selects "use existing" dvSwtiches, PFxM expects the existing dvSwitch configuration to work.

Even if the template calls for having an LAG configured, PFxM will not reconfigure the uplinks of an existing dvSwitch with an LAG.

If PFxM creates the new dvSwitches, it will create the LAG successfully.

If dvSwitches are created ahead of time, the user should create LAG on them also.

If dvSwitches are created ahead of time and the user forgets to create LAG, then the script fails, manually create LAG in Vcenter / dvSwitches, migrate uplinks to them, then click "retry" on Resource Group.

Impacted Versions

PowerFlex Manager 4.5.x

Fixed In Version

PowerFlex Manager 4.6.1