I just tried an upgrade using the VAMI, from the online repo, from vSphere 6.5 to 6.5e. The upgrade rebooted my vSphere appliance and neither the VAMI nor vSphere itself came back up. I was able to log into the appliance as root, and was able to observe that no vmware-related processes were running at all. I rebooted the appliance a second time and vSphere started but the VAMI would not start:
# systemctl -l status vami-lighttp.service● vami-lighttp.service - LSB: Lightning fast webserver with light system requirements
Loaded: loaded (/etc/rc.d/init.d/vami-lighttp; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-07-06 17:25:25 PDT; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 9551 ExecStart=/etc/rc.d/init.d/vami-lighttp start (code=exited, status=1/FAILURE)
<pre>Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: Starting LSB: Lightning fast webserver with light system requirements...
Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: Starting vami-lighttpd:Extracting SSL certificate from VECS
Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: SSL certificate extracted
Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: Duplicate config variable in conditional 0 global: server.use-ipv6
Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: 2017-07-06 17:25:25: (/build/mts/release/bora-4446656/studio/src/vami/apps/lighttpd/1.4.39/src/configfile.c.974) source: /opt/vmware/etc/lighttpd/lighttpd.conf line: 705 pos: 1 parser failed somehow near here: (EOL)
Jul 06 17:25:25 sac-vcenter01.s2prod vami-lighttp[9551]: [FAILED]
Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Control process exited, code=exited status=1
Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: Failed to start LSB: Lightning fast webserver with light system requirements.
Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Unit entered failed state.
Jul 06 17:25:25 sac-vcenter01.s2prod systemd[1]: vami-lighttp.service: Failed with result 'exit-code'.</pre>
After editing that line out of the config file the VAMI would start. My vSphere is still showing the pre-upgrade version (build 5318154) but the VAMI is showing the upgraded version (build 5705665) so my appliance is now in an indeterminate state.
Don't try this upgrade! Even making a snapshot won't save you from some grief unless you know the ESXi host your vSphere is running on, and can fix it from the command line, since it might trash your vSpherem and then you will have no vSphere running....
w
