Hi,
I've been hacking away at this problem in my lab for a few days and I am finally ready to ask for help.
I have two hosts, one is completely compliant and the host profile is created from it.
The second host has the profile applied to it during autodeploy.
After tracking down various things that were actually non-compliant it boils down to this:
The second host always shows as non-compliant after reboot and remains in maintenance mode.
It is non-compliant because of the networking.
The reference host has a dVSwitch with two NICs. I can reboot this host and it always come up, the host profile is applied and it exits maint mode and it's perfect.
The second host stays in maint mode and is non-copliant because: of several lines that I cant copy any paste but basically is saying that the dVSwitch does not exist on the host. And that i has no nics and that the PG do not exist... and looking at it no, there is the temporary vSwitch that has been created and the NICs are connected to it and the dVSwitch does exist but has no NICs.
Then the stangest bit... if I apply the profile to the second host, it becomes compliant, the dVS problems go away and it is ready to go... if I reboot it, same thing again.
I guess this indicates some sort of sequencing error on applying the HP, but damned if I can figure it out. These are completely stateless hosts, both of them. They are identical... or pretty nearly, the 2nd host does have a dual port network adapter in the riser, but at the moment, that isn't connected to anything, I am just using the two onboard NICs in both hosts.
Saying that, I haven't tried removing that dual port NIC card, I suppose it's worth a try... but I am really grasping at straws here.
Wny ideas on where I should look next? BTW I am using 5.5 in my lab and haven't upgrade to 5.5b yet.
thanks
Bill