Hello,
After changing the host name in some places it has been doubled domain name.
Extra domain "cloud.local" has been added to FQDN.
Yes, I'm sure I set the correct hostname during the change
root @ vcenter [~] # hostname
vcenter.cloud.localroot@vcenter [ ~ ]# /usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vcenterserver 2> /dev/null |grep URL
URL: https://vcenter.cloud.local:443/vcenter.cloud.local
URL: https://vcenter.cloud.local:443/sdk
URL: https://vcenter.cloud.local:443/sdk
URL: https://vcenter.cloud.local:443/catalog/catalog.zip
I tried to restore the snapshot several times and change to other names, but a duplicate domain is always added.
My VCSA is also not connected to AD domain.
What should we do in order to fix duplicated domain name?
Thenx
Check the old Web Client and see if the domain name is duplicated in the same places. If they are NOT it’s most likely just a HTML5 client display issue.
If you have support there is no harm opening an SR and asking them to check the VCSA.
M
The problem is on HTML5 and FLEX.
Probably best to open an SR if you can then.
What’s the history of this VCSA? What was the initial install version/build? How many times has it been upgraded and to what versions/build each time?
If you do get an answer from support please post the details here.
Previously there was vCenter on Windows with a hostname without a domain and I think this is causing the problem in VCSA.
Can you explain what you did, we have the same issue.
Sorry to resurrect a 2 year old thread but since this page comes as top google result for the OP's problem I'll post a fix which I came up with.
First of all, the problem seems to be cosmetic only because our VCSA was working fine apart from displaying doubled domain name. So there should be no problem leaving it as it is AFAIK.
In this example I will use vcenter.lab.loc as correct vCenter FQDN and vcenter.lab.loc.lab.loc as "doubled".
1. Open a console to the machine running PSC (VCSA if PSC is internal).
2. Execute this command:
/opt/likewise/bin/ldapsearch -H ldap://localhost -x -D "cn=administrator,cn=users,dc=vsphere,dc=local" -W -b "cn=ServiceRegistrations,cn=LookupService,cn=Default-First-Site,cn=Sites,cn=Configuration,dc=vsphere,dc=local" -s sub "vmwLKUPPropertyName=com.vmware.vim.vcenter.instanceName" > fix_instancename.ldif
Enter administrator password.
It should create file fix_instancename.ldif containing path to instanceName variable and its value (which should be VCSA FQDN with doubled domain name), for example
...
dn: cn=Property3,cn=217602d6-4efa-4f8e-9892-ed0892eb40de,cn=ServiceRegistrations,cn=LookupService,cn=Default-First-Site, cn=Sites,cn=Configuration,dc=vsphere,dc=local
...
vmwLKUPPropertyValue: vcenter.lab.loc.lab.loc
...
The "cn=UUID" part right after the "cn=Property3" is specific to your instance of PSC/VCSA so do not copy it from my example.
3. Edit the file fix_instancename.ldif so it looks like this (it should contain just these 4 lines):
dn: cn=Property3,cn=217602d6-4efa-4f8e-9892-ed0892eb40de,cn=ServiceRegistrations,cn=LookupService,cn=Default-First-Site, cn=Sites,cn=Configuration,dc=vsphere,dc=local
changetype: modify
replace: vmwLKUPPropertyValue
vmwLKUPPropertyValue: vcenter.lab.loc
4. Execute following command which actually modifies instanceName variable
/opt/likewise/bin/ldapmodify -f fix_instancename.ldif -H ldap://localhost -x -D "cn=Administrator,cn=Users,dc=vsphere,dc=local" -W
Enter administrator password.
5. Re-login to web client. The name of VCSA should be fixed by now. Maybe reboot would be a good idea but we had no time and everything seemed to be working without it.