Unable to set pathing policy for HPP claimed devices in ESXi 7.0 U1
Article ID: 332700
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- After installing or upgrading to ESXi 7.0 U1, you are unable to change the pathing policy for HPP claimed devices.
- In the hostd.log, you see messages similar to:
2021-02-10T07:34:05.104Z error hostd[2100209] [Originator@6876 sub=Libs opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] [ConfigStore:115240376064:] [1083]Validation Error: '/hpp/preferred_path' Object does not follow UnionTag condition, scheme: <======
2021-02-10T07:34:05.104Z error hostd[2100209] [Originator@6876 sub=Libs opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] [ConfigStore:115240376064:] [1087] Failed to validate User config
2021-02-10T07:34:05.106Z info hostd[2100209] [Originator@6876 sub=Libs opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] [ConfigStore:115240376064:] ConfigStoreException: [context]zKq7AVICAgAAAHQfAQEPY29uZmlnc3RvcmUAALKCAmxpYmNvbmZpZ3N0b3JlLnNvAACchgIA1FUFAB24AgAAAAUB/zdebGlidm1rY3RsLnNvAALEIHlob3N0ZAACwGBigzu/FAFsaWJ2aW0tdHlwZXMuc28AApKBvgRp+CpsaWJ2bWFjb3JlLnNvAAS9MysE8jo5BTt9AGxpYnB0aHJlYWQuc28uMAAG/acObGliYy5zby42AA==[/context]
2021-02-10T07:34:05.106Z error hostd[2100209] [Originator@6876 sub=Default opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Failed to set hpp multipath lun policy: N14EsxConfigStore19ValidationExceptionE(Failed to validate User config)
2021-02-10T07:34:05.106Z info hostd[2100209] [Originator@6876 sub=AdapterServer opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] AdapterServer caught exception: N3Vim5Fault15HostConfigFault9ExceptionE(Fault cause: vim.fault.HostConfigFault
--> )
--> )
--> [context]zKq7AVICAgAAAHQfAQEPaG9zdGQAAK20PGxpYnZtYWNvcmUuc28AAFImHAAdkRoAQhQWARCOTmhvc3RkAAGQtlkBmCN5AcBgYoI7vxQBbGlidmltLXR5cGVzLnNvAAGSgb4AafgqAL0zKwDyOjkDO30AbGlicHRocmVhZC5zby4wAAT9pw5saWJjLnNvLjYA[/context]
2021-02-10T07:34:05.108Z info hostd[2100209] [Originator@6876 sub=Vimsvc.TaskManager opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Task Completed : haTask-ha-host-vim.host.StorageSystem.updateHppMultipathLunPolicy-401562 Status error
2021-02-10T07:34:05.108Z info hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Activation [N5Vmomi10ActivationE:0x0000001ad510e010] : Invoke done [updateHppMultipathLunPolicy] on [vim.host.StorageSystem:storageSystem]
2021-02-10T07:34:05.108Z verbose hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Arg lunId:
--> "0661343664376331662d626162632d3437"
2021-02-10T07:34:05.108Z verbose hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Arg policy:
--> (vim.host.MultipathInfo.HppLogicalUnitPolicy) {
--> policy = "FIXED", <=====
--> path = "vmhba64:C0:T3:L0",
--> }
2021-02-10T07:34:05.104Z error hostd[2100209] [Originator@6876 sub=Libs opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] [ConfigStore:115240376064:] [1087] Failed to validate User config
2021-02-10T07:34:05.106Z info hostd[2100209] [Originator@6876 sub=Libs opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] [ConfigStore:115240376064:] ConfigStoreException: [context]zKq7AVICAgAAAHQfAQEPY29uZmlnc3RvcmUAALKCAmxpYmNvbmZpZ3N0b3JlLnNvAACchgIA1FUFAB24AgAAAAUB/zdebGlidm1rY3RsLnNvAALEIHlob3N0ZAACwGBigzu/FAFsaWJ2aW0tdHlwZXMuc28AApKBvgRp+CpsaWJ2bWFjb3JlLnNvAAS9MysE8jo5BTt9AGxpYnB0aHJlYWQuc28uMAAG/acObGliYy5zby42AA==[/context]
2021-02-10T07:34:05.106Z error hostd[2100209] [Originator@6876 sub=Default opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Failed to set hpp multipath lun policy: N14EsxConfigStore19ValidationExceptionE(Failed to validate User config)
2021-02-10T07:34:05.106Z info hostd[2100209] [Originator@6876 sub=AdapterServer opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] AdapterServer caught exception: N3Vim5Fault15HostConfigFault9ExceptionE(Fault cause: vim.fault.HostConfigFault
--> )
--> )
--> [context]zKq7AVICAgAAAHQfAQEPaG9zdGQAAK20PGxpYnZtYWNvcmUuc28AAFImHAAdkRoAQhQWARCOTmhvc3RkAAGQtlkBmCN5AcBgYoI7vxQBbGlidmltLXR5cGVzLnNvAAGSgb4AafgqAL0zKwDyOjkDO30AbGlicHRocmVhZC5zby4wAAT9pw5saWJjLnNvLjYA[/context]
2021-02-10T07:34:05.108Z info hostd[2100209] [Originator@6876 sub=Vimsvc.TaskManager opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Task Completed : haTask-ha-host-vim.host.StorageSystem.updateHppMultipathLunPolicy-401562 Status error
2021-02-10T07:34:05.108Z info hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Activation [N5Vmomi10ActivationE:0x0000001ad510e010] : Invoke done [updateHppMultipathLunPolicy] on [vim.host.StorageSystem:storageSystem]
2021-02-10T07:34:05.108Z verbose hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Arg lunId:
--> "0661343664376331662d626162632d3437"
2021-02-10T07:34:05.108Z verbose hostd[2100209] [Originator@6876 sub=Solo.Vmomi opID=kjo31z83-253837-auto-5fv2-h5:70068353-a0-2e-4726 user=vpxuser:CBSP\admapop] Arg policy:
--> (vim.host.MultipathInfo.HppLogicalUnitPolicy) {
--> policy = "FIXED", <=====
--> path = "vmhba64:C0:T3:L0",
--> }
Environment
VMware vSphere ESXi 7.0.x
Cause
This issue occurs due to the failure of a validation step in the configstore.
This process fails as the host is setting 'preferredPath' first without setting the correct 'scheme'.
This process fails as the host is setting 'preferredPath' first without setting the correct 'scheme'.
Resolution
This issue is resolved in ESXi 7.0 U2.
Note: While updating, please be aware of a current issue effecting patching. Refer
Failed to load crypto64.efi Fatal error: 15 (Not found) after patching ESXi host to 7.0 Update 2
Workaround:
To workaround this issue when upgrading, roll back to a previous version of ESXi that uses the sticky bit files rather than the configstore. For more information on reverting to previous version of ESXi, see Reverting to a previous version of ESXi (1033604)
Note: While updating, please be aware of a current issue effecting patching. Refer
Failed to load crypto64.efi Fatal error: 15 (Not found) after patching ESXi host to 7.0 Update 2
Workaround:
To workaround this issue when upgrading, roll back to a previous version of ESXi that uses the sticky bit files rather than the configstore. For more information on reverting to previous version of ESXi, see Reverting to a previous version of ESXi (1033604)
Feedback
Yes
No
Powered by
