#less /var/log/vua.log
...
--> Traceback (most recent call last):
--> File "/tmp/vuaScript-sMM75j/precheck.py", line 2315, in <module>
--> sys.exit(main(sys.argv))
--> File "/tmp/vuaScript-sMM75j/precheck.py", line 2299, in main
--> results += [testFn() for testFn in tests]
--> File "/tmp/vuaScript-sMM75j/precheck.py", line 2290, in <lambda>
--> tests.append(lambda:checkVibConflicts(version))
--> File "/tmp/vuaScript-sMM75j/precheck.py", line 1748, in checkVibConflicts
--> (up, down, new, existing) = prof.ScanVibs(oldvibs)
--> File "/tmp/vuaScript-sMM75j/esximage.zip/vmware/esximage/ImageProfile.py", line 627, in ScanVibs
--> File "/tmp/vuaScript-sMM75j/esximage.zip/vmware/esximage/VibCollection.py", line 62, in __add__
--> File "/tmp/vuaScript-sMM75j/esximage.zip/vmware/esximage/VibCollection.py", line 79, in AddVib
--> File "/tmp/vuaScript-sMM75j/esximage.zip/vmware/esximage/Vib.py", line 625, in MergeVib
ValueError: Cannot merge VIBs VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.550.0.0.1331820, VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.550.0.0.1331820 with unequal statelessready attributes: (False, True)
Very strange, so I built a custom ESXi installer image using powershell, and removed the adp94xx VIB since I don't need it as this VMware KB recommends:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2047685
I still received the same error despite having removed the VIB.
At time point, I don't have time to screw around with idiotic bugs like this, so I called VMware Support. They spent two days looking at the problem.
They then recommended to just run Update Manager to install all the pending patches which would take me to Update 1. So, this accomplished my goal despite having not fixed the issue at hand.
ESXi 5.5U1 is build number 1623387
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2047685
I still received the same error despite having removed the VIB.
At time point, I don't have time to screw around with idiotic bugs like this, so I called VMware Support. They spent two days looking at the problem.
They then recommended to just run Update Manager to install all the pending patches which would take me to Update 1. So, this accomplished my goal despite having not fixed the issue at hand.
ESXi 5.5U1 is build number 1623387
No comments:
Post a Comment