Here is the link to the work around.
I need to get this fixed so the web interface option will work .
For Studio 2.6, I believe the only way to get this working if you do not have the vami.hostname property set in ESX is to do the following:
1.) Manually or through the ui create a working /opt/vmware/etc/vami/ovfEnv.xml file.
2.) Once satisfied, edit /opt/vmware/share/vami/subsequentboot and comment out the line
if [ -x /opt/vmware/share/vami/vami_ovf_process ]; then
/opt/vmware/share/vami/vami_ovf_process --printovfenv > /opt/vmware/etc/vami/ovfEnv.xml
This overwrites the ovfEnv.xml with the current ovf properties with the values configured through the client on every boot. What comes from the file is used to configure the networking.
Please note though, this means that any properties you configure through the client as explained in the KB article will not be detected further on.
Sorry but been out of the loop last week or so. I deployed a new appliance and opened it through the UI. Note I did not apply the work around to this VM.
1. My vm has the ovfEnv.xml file.
2. I commented out the if loop in the subsequentboot file.
3. From the Web interface I set the local domain name to eva.vami.com. This is reflected in the etc/hosts file
on reboot, the host name reverts back to localhost and the lines added to the hosts file are removed and changed back to localhost.localdom
The host name is still not sticking. Is there some process on boot that writes out this file that can be commented out on only run on first boot?
If you have made your changes you can remove
If you want to disable this in your build profile you can also set the following properties to false:
Setting the SetHostname and SetNetwork to false in the XML worked. I was still able to use the web interface to change the values, and on reboot, the host name stuck .
Is there a way to set the default hostname to something besides localhost.localdom.
I couldn't find anywhere in the XML that that was set.