PowerFlex 3.X: Volumes können nicht zu vorhandenem Service hinzugefügt werden

Wenn die asmManager.log auf dem PFxM überprüft wird, werden möglicherweise Einträge wie die folgenden angezeigt.

INFO  [2022-12-07T09:18:13.504666] 12352: service_deployment.rb:1255:in `block in process_components': An error occurred during the processing of storage components.
ERROR [2022-12-07T09:18:13.506285] 12352: service_deployment.rb:622:in `process': sudo puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/resources/<VCENTER_NAME>.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/resources --always-override <VCENTER_NAME> failed; output in /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/<VCENTER_NAME>.outERROR [2022-12-07T09:18:13.506466] 12352: service_deployment.rb:623:in `process': ["/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:384:in `block in run_command_streaming'", "/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:212:in `popen_run'", "/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:102:in `popen3'", "/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:352:in `block in run_command_streaming'", "org/jruby/RubyIO.java:1171:in `open'", "/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:351:in `run_command_streaming'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1575:in `block in process_generic'", "/opt/asm-deployer/lib/asm/private_util.rb:1079:in `block in wait_until_available'", "/opt/asm-deployer/lib/asm.rb:502:in `wait_on_counter_threshold'", "/opt/asm-deployer/lib/asm/private_util.rb:1078:in `wait_until_available'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1518:in `process_generic'", "/opt/asm-deployer/lib/asm/type/base.rb:578:in `process_generic'", "/opt/asm-deployer/lib/asm/provider/elementmanager/scaleio.rb:4099:in `create_batch_scaleio_datastores'", "/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `block in process_multiple_volumes'", "org/jruby/RubyArray.java:1779:in `each_slice'", "/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `process_multiple_volumes'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1979:in `process_multi_scaleio_storage'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1320:in `block in create_multi_components_thread'"]

In der exception.log sehen wir:

#<RuntimeError: sudo puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/resources/<VCENTER_NAME>.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/resources --always-override <VCENTER_NAME> failed; output in /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/<VCENTER_NAME>.out>
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:384:in `block in run_command_streaming'
/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:212:in `popen_run'
/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:102:in `popen3'
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:352:in `block in run_command_streaming'
org/jruby/RubyIO.java:1171:in `open'
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:351:in `run_command_streaming'
/opt/asm-deployer/lib/asm/service_deployment.rb:1575:in `block in process_generic'
/opt/asm-deployer/lib/asm/private_util.rb:1079:in `block in wait_until_available'
/opt/asm-deployer/lib/asm.rb:502:in `wait_on_counter_threshold'
/opt/asm-deployer/lib/asm/private_util.rb:1078:in `wait_until_available'
/opt/asm-deployer/lib/asm/service_deployment.rb:1518:in `process_generic'
/opt/asm-deployer/lib/asm/type/base.rb:578:in `process_generic'
/opt/asm-deployer/lib/asm/provider/elementmanager/scaleio.rb:4099:in `create_batch_scaleio_datastores'
/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `block in process_multiple_volumes'
org/jruby/RubyArray.java:1779:in `each_slice'
/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `process_multiple_volumes'
/opt/asm-deployer/lib/asm/service_deployment.rb:1979:in `process_multi_scaleio_storage'
/opt/asm-deployer/lib/asm/service_deployment.rb:1320:in `block in create_multi_components_thread'

Wenn wir zu /opt/Dell/ASM/deployments/<JOB_ID>/ gehen und VCENTER_NAME.out> überprüfen<, sehen wir Einträge wie die folgenden.

Error: /Stage[main]/Asm::Resource_wrapper/Asm::Fcdatastore[x.x.local:<DATASTORE_NAME>]/Esx_datastore[x.x.local:<DATASTORE_NAME>]/ensure: change from 'absent' to 'present' failed: Unable to perform the operation because the following exception occurred:- 
 Existing VMFS partition on disk, cannot create datastore on /vmfs/devices/disks/eui.5c3e682f06560c0fc6afcb0e00000010
Debug: Asm::Fcdatastore[x.x.local:<DATASTORE_NAME>]: Resource is being skipped, unscheduling all events
Debug: Datastore not found with id: c6afcb0e00000010 searching on datastore name: <DATASTORE_NAME>
Debug: Creating VMFS volume <DATASTORE_NAME> on device eui.5c3e682f06560c0fc6afcb0e00000010
Error: Unable to perform the operation because the following exception occurred:- 
 Existing VMFS partition on disk, cannot create datastore on /vmfs/devices/disks/eui.5c3e682f06560c0fc6afcb0e00000010
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/errors.rb:157:in `fail'

Entfernen Sie die vorhandenen VMFS-Daten von der Festplatte in vCenter.
Wiederholen Sie die Bereitstellungs- oder Update-Servicedetails.
Sobald in PFxM alles grün angezeigt wird, versuchen Sie erneut, die Volumes hinzuzufügen.