Symptoms

Upgrade failing due to obtain platform service status on host with return 1.LCM.log: 2020-01-30T13:58:41.336+0000 WARN [pool-6-thread-1] com.vce.commons.vcm.PlatformServiceClient PlatformServiceClient.checkPlatformServiceStatus:196 - Failed to obtain platform service status on host with return 1 2020-01-30T13:58:41.636+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:42.636+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:43.636+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:44.636+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:45.637+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:46.637+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:47.637+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:48.638+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:49.638+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:50.638+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader AbstractESXiHostUpgrader$2.progress:513 - The ESXi host upgrade progress is :: 90 2020-01-30T13:58:51.336+0000 INFO [pool-6-thread-1] com.vce.commons.vcm.PlatformServiceClient PlatformServiceClient.isPlatformServiceReady:117 - Get platform service status for, try count is 3 2020-01-30T13:58:51.638+0000 INFO [Thread-542] com.vce.lcm.service.upgrade.AbstractESXiHostUpgrader ..................... ..................... ..................... ..................... 2020-01-30T13:58:53.345+0000 WARN [pool-6-thread-1] com.vce.commons.vcm.PlatformServiceClient PlatformServiceClient.checkPlatformServiceStatus:196 - Failed to obtain platform service status on host with return 1 platform_svc.log: 2020-01-31T01:45:10Z platform_svc.cli: [MainThread] ERROR - Failed processing command: firmware.list. error:([Errno 2] No such file or directory). Please make sure platform-service is running! 2020-01-31T02:15:17Z platform_svc.cli: [MainThread] ERROR - Failed processing command: firmware.list. error:([Errno 2] No such file or directory). Please make sure platform-service is running! 2020-01-31T02:45:23Z platform_svc.cli: [MainThread] ERROR - Failed processing command: firmware.list. error:([Errno 2] No such file or directory). Please make sure platform-service is running! 2020-01-31T08:32:35Z platform_svc.cli: [MainThread] ERROR - Failed processing command: techsuprep.bmclog.get. error:([Errno 2] No such file or directory). Please make sure platform-service is running!

Cause

PTAgent Account vxpsvc may not be active

Resolution

To resolve this issue, follow the steps below: Connect to the ESXi node using SSH.Check if the PTAdmin account is active. /opt/vxrail/tools/ipmitool user list 1 ID Name Callin Link Auth IPMI Msg Channel Priv Limit 1 true false false NO ACCESS 2 root true true true ADMINISTRATOR 3 true false false NO ACCESS 4 true false false NO ACCESS 5 true false false NO ACCESS 6 true false false NO ACCESS 7 true false false NO ACCESS 8 true false false NO ACCESS 9 true false false NO ACCESS 10 true false false NO ACCESS 11 true false false NO ACCESS 12 true false false NO ACCESS 13 true false false NO ACCESS 14 true false false NO ACCESS 15 vxpsvc true true true ADMINISTRATOR 16 PTAdmin true true true ADMINISTRATO If the account is not active then we need to correct it by running: /opt/dell/DellPTAgent/tools/ipmitool_static channel setaccess 1 16 callin=on ipmi=on link=on privilege=4 Check if vxpsvc_ptagent_op account is present under system account list by running: esxcli system account list If vxpsvc_ptagent_op account is present under system account list then try to create test account. See if there is a error below. esxcli system account add -i test -p "VxR@il123!" -c "VxR@il123!" A general system error occurred: passwd: Module is unknown 6. If creating test account fails, check the PAM.d [root@ServerName: cd /etc/pam.d [root@ServerName: /etc/pam.d] cat passwd password requisite /lib/security//pam_passwdqc.so retry=3 min=disabled,disabled,disabled,7,7 password required /lib/security//pam_deny.so password sufficient /lib/security//pam_unix.so use_authtok nullok shadow sha512 remember=5 [root@ServerName:/etc/pam.d] cat .#passwd #%PAM-1.0 # Change only through host advanced option "Security.PasswordQualityControl". password requisite /lib/security/$ISA/pam_passwdqc.so retry=3 min=disabled,disabled,disabled,7,7 password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok shadow sha512 password required /lib/security/$ISA/pam_deny.so 7. Save original copy by running the command: [root@ServerName:/etc/pam.d] cp passwd ee.passwd 8. Copy default settings to current config: [root@ServerName:/etc/pam.d] cp .#passwd passwd 9. Remove the test which was created in step 4 by running: esxcli system account remove -i test 10. Restart "PTAgent, platform service, VXRM management agents" and retry the upgrade.

Support Cases