AutoDeploy configuration lost

[ftoppi]

Hello everyone.

I have a blade server running vSphere 5 with AutoDeploy for about a month now. I configured it (depot, HA package, deployrule based on MAC address, host profile, answer file) and it's been running fine.

I've rebooted it plenty of times, it always came up correctly, virtual machines are running fine with VDS, vMotion, software iSCSI, etc. Standard features.

Now I want to configure my other blades using AutoDeploy (new deployrule, same host profile, new answer file) and everything goes wrong.

When I want to list anything related to AutoDeploy, it returns no value. Get-ESXImageProfile, Get-ESXSoftwareChannel, Get-DeployRule, Get-DeployRuleSet, etc cmdlets return no value (and no error).

Now I don't dare to reboot that running blade server because I'm afraid it won't come up again.

What's going on ? Is it just a display bug or is it worse ? How can I fix it ?

Any ideas and suggestions welcome.

FT

[AdamCSC · Accepted solution]

Verify that the config looks good on the deployment server.  This is good doc for overall troubleshooting

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2000988

Also, check the rules etc for any issues.  This is good info on those commands.

http://blogs.vmware.com/vsphere/2012/01/troubleshooting-auto-deploy-rules.html

AutoDeploy GUI is a nice addition to using this product in your environment.  I have had an overall more stable deployment using this tool than without it.

http://labs.vmware.com/flings/autodeploygui

Worst case it is not too painful if you just uninstall the AutoDeploy (clean up any of the old directories as needed) then reinstall it.  You'll have to rebuild your deployment rules but it is not too big of a deal as long as you do not have to reboot the servers while you are in the rebuild process.

[ftoppi]

Thanks for the information.

I checked the AutoDeploy files (config, database), nothing seems corrupted or problematic.

I've temporarilly installed ESX on another blade with a hard drive, vMotioned the virtual machines and then rebooted the AutoDeploy host. It booted fine.

But as no rule shows up, I decided to go with your idea.

I uninstalled AutoDeploy, rebooted and installed it again with GUI. I deleted the old profile, removed the blade from the cluster and began a new deployment.

I followed the PDF up until the answer file part. There I have an error which shows up and I can't get further.

Anyway, I created a "host profile answer file" to tune the profile for the host and now it boots again correctly (just like before) AND I still have the rules in the AutoDeploy GUI.

I hope they won't go away this time, it's kind of a pain in the *ss if I have to do the same to my 20 blades next time.

Thanks for your help