The goal is to deploy a CentOS 6.4 linux VM, mount a NFS share, run a script from the NFS share (Puppet).
All scripts work and accomplish the task but when they are combined in a workflow to automate using VCAC they fail due to the VM not getting a GW address. The IP is set, but not DNS, or the search suffix or the GW.
1. Gugent installed and working.
2. Test the Gugent and I can see it is communicating.
3. If I add the network profile it assings an IP.
4. VM deploys, boots, gets DHCP, then is assigned the static IP.
5. Reboots, check network settings and the GW is set to 0.0.0.0
6. I check /usr/share/gugent/GuestAgent.log and it is passing all of the required info in the network profile.
Odd. I am testing with just DHCP. Is it a CentOS bug? Anyone try this on RHEL6?
If you want to use Network Profiles and have the information pull through successfully you'll need to use a vCenter Customisation spec. Get rid of DHCP.
Im using a vcenter customization spec for RHEL6. Same as Windows, I use the spec to set DHCP so the VCAC Linux client can communicate with VCAC. Once that spec is comlete the VCAC workflow takes over and should apply the correct IP scheme. It applies only the IP address and SM. No GW, DNS, or DNS search domain. I got it to work using pure DHCP and no network profile for CentOS. This does however work fine with Windows.
Gotcha. DHCP isn't required for that initial communication. The network profile information is a appended to the object as a custom property during the "Building Machine" phase. This is then fed into the customisation spec during the customisation process. Once that is complete the guest agent would be able to talk back to vCAC for whatever additional operations you need. I don't know 100% but I'd suggest that the initial DHCP is where it's breaking for you.
Cool thanks. So in the customization spec what do I set for networking? Either I chose DHCP or an IP, but I want the IP to come from the network profile range.
Set it to "Prompt User for IP" in the Customisation Spec. That will be populated by the IP from the Network Profile.
Ill try that and I'm deploying a RHEL6 box to test if the network profile will apply the GW IP correctly. If so it would seem to be a bug in CentOS. If not I know Ive missed something. I appreciate your feedback and ill make sure to update this with the solution when i figure it out.
Oh, one thing that I just thought of.... when you build the CentOS template in vSphere, set the OS type to RedHat. The CentOS type doesn't allow customisation while RedHat does.