why do you had the need to replace a working firmwareConfig.sh with a firmwareConfig.py which is eniretly broken?
and even if it would work - have you guys from Vmware ever heard about "shebang"
i guess it would be too easy for users not break CLI API's after updates
-----------------------------------------------------------
[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680] /bin/firmwareConfig.py --backup ./
Saving current state in ./firmware-backup.$$
find: ./firmware-backup.$$: No such file or directory
Error (1) saving state to ./firmware-backup.$$
Clock updated.
Time: 16:20:49 Date: 06/20/2020 UTC
ConfigBundle: ./configBundle-esx.vmware.local.tgz
-----------------------------------------------------------
[root@esx:/vmfs/volumes/5eed9527-3dea0e8a-b4f9-000c29f07680] ls -lh configBundle-esx.vmware.local.tgz
-rw-r--r-- 1 root root 472 Jun 20 16:20 configBundle-esx.vmware.local.tgz
-----------------------------------------------------------
[harry@srv-rhsoft:/downloads]$ ls
insgesamt 8,0K
drwxr-x--- 2 harry verwaltung 4,0K 2020-06-20 18:24 configBundle-esx.vmware.local
-rw-r----- 1 harry verwaltung 472 2020-06-20 18:21 configBundle-esx.vmware.local.tgz
[harry@srv-rhsoft:/downloads]$ ls -R
.:
insgesamt 8,0K
drwxr-x--- 2 harry verwaltung 4,0K 2020-06-20 18:24 configBundle-esx.vmware.local
-rw-r----- 1 harry verwaltung 472 2020-06-20 18:21 configBundle-esx.vmware.local.tgz
./configBundle-esx.vmware.local:
insgesamt 12K
-rw-r----- 1 harry verwaltung 136 2020-06-20 18:24 jumpstrt
-rw-r----- 1 harry verwaltung 107 2020-06-20 18:20 jumpstrt.gz
-rw-r----- 1 harry verwaltung 136 2020-06-20 18:20 Manifest.txt
-----------------------------------------------------------
[harry@srv-rhsoft:/downloads]$ cat configBundle-esx.vmware.local/jumpstrt
jumpstart.run-once=loadesx-upgrade-once7.0.0,tls-advanced-option6.7.0,tls-advanced-option7.0.0,vsan-config-once1.0.0,vsan-upgrade2.0.0,
[harry@srv-rhsoft:/downloads]$ cat configBundle-esx.vmware.local/Manifest.txt
RELEASELEVEL=VMware ESXi 7.0 GA
BUILDNUMBER=15843807
UUID=94554D56-F8EE-708D-F6D5-11E578F07680
KERNELOPTS=autoPartition=FALSE
USEROPTS=
yeah, someone at VMware woke upo and tested his stuff so it got fixed with the first update for ESXi 7.0
yeah, someone at VMware woke upo and tested his stuff so it got fixed with the first update for ESXi 7.0