AH28
Contributor
Contributor

vMA 5.1.0.0 does not retain name/domain upon reboot

I'm trying to the latest vMA (5.1.0.0 Build 782391) build and cannot figure out why it will not retain it's hostname. I follow the 'Deploy vMA' steps completely and verify the name is updated, but when I reboot it returns to 'localhost.localdom'. The same goes for joining the domain, if I update the name and then follow the correct steps to join the domain, after it reboots (as it asks for after joining the domain), it reverts back to 'localhost.localdom'. I verify each time that the object is created in AD, so it definitely is joining the domain but losing it's settings on reboot! It does however retain the Static IP, Gateway, DNS and Time Zone info. Any ideas?

vMA installed on vCenter Server 5.0.0 Build 804277. ESXi 5.0.0 (VMKernel Release Build 821926).

Tags (3)
0 Kudos
8 Replies
cssavard
Contributor
Contributor

I'm having the same issue, were you able to fix it ?

0 Kudos
AH28
Contributor
Contributor

I was not able to get past this issue and thus put the deployment on hold... Smiley Sad

0 Kudos
cssavard
Contributor
Contributor

Thanks for the quick reply, I have searched a little bit more on this issue and I will try to change it using the CLI. I'll keep you updated about my progress !

0 Kudos
cssavard
Contributor
Contributor

I was able to get it working !! Here's how I did it :

You need to create a valid DNS entry for you server before making the change on the vma instance as it was not working until I added the hostname alias to the DNS.

I logged on the VMA console with the user vi-admin

switched to root user (sudo -i)

Launched the Suse network configuration utility :

system-config-network-tui

Follow the on-screen instructions.

Once done, reboot and voilà !

I hope it works for you as well

0 Kudos
alex_wu
Enthusiast
Enthusiast

I met the same issue, and tried to do as you mentioned, but it does not work.

0 Kudos
AH28
Contributor
Contributor

This did not work for me, it still reverts back after reboot.

0 Kudos
MarkBK
Contributor
Contributor

Nothing worked for me until I created the PTR record in DNS for the vMA

0 Kudos