OPERATIONAL DEFECT DATABASE
...
...
Deploying or migrating to the vCenter Server Appliance 6.5 in a mixed IPv4 & IPv6 environment may fail with these errors. vCenter Server Appliance Deployment The deployment fails with the error: Set DNS settings action failed due to: Operation Failed. In the /var/log/vmware/applmgmt.vami.log file, you see entries similar to: 2016-10-27T06:56:15.301 [25210]ERROR:vmware.appliance.networking.impl:['/usr/bin/netmgr', 'dns_servers', '--set', '--mode', 'static', '--servers', '2013:930::1,192.168.111.1'] error , rc=17 2016-10-27T06:56:15.301 [25210]ERROR:root:Method failure = <twisted.python.failure.Failure vmware.vherd.base.pint.Error: pint.Error('com.vmware.applmgmt.err_operation_failed', 'Operation Failed.', **{'args': ''})> 2016-10-27T06:56:15.301 [25207]ERROR:root:Exception: Traceback (most recent call last): File "/opt/vmware/share/htdocs/vami/backend/vami.py", line 108, in execute method(response, locale, action, input) File "/opt/vmware/share/htdocs/vami/backend/manage-networking.py", line 166, in updateDNS data['attributes']) LocalizableException: args Migration to a vCenter Server Appliance This migration fails with the error: Error setting DNS configuration. Details : Operation Failed.. Code: com.vmware.applmgmt.err_operation_failed. Failed to set DNS In the /var/log/vmware/applmgmt.vami.log file, you see entries similar to: 2016-11-20T14:24:05.325 [10790]INFO:root:Response :<?xml version="1.0"?><response><locale>en-US</locale><requestid>getUpgradeStatus</requestid><value id="status" actions="enabled">failed</value><value</font>id="progress" actions="enabled">0</value><value id="details" actions="enabled">{"status": "error","info": [],"question": null,"progress_message": null,"warning": [],"error": {"resolution": null,"detail": [{"args": ["Operation Failed.. Code: com.vmware.applmgmt.err_operation_failed"],"id": "install.setnet.set.dns.vami","localized": "Error setting DNS configuration. Details : Operation Failed.. Code: com.vmware.applmgmt.err_operation_failed","translatable": "Error setting DNS configuration. Details : %(0)s"},{"id": "install.setnet.set.dns","localized": "Failed to set DNS","translatable": "Failed to set DNS"}],"componentKey": "setnet","problemId": null},"progress": 0}</value></response> Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.
This issue is resolved in VMware vCenter Server Appliance 6.5 Update 1, available at VMware Downloads.IMPORTANT: vCenter Server Appliance 6.5 builds have been removed as of November 14, 2017 due to a deployment-impacting issue. This issue does not impact Windows installed vCenter Servers. To resolve this issue, you must upgrade to vCenter Server Appliance 6.5 Update 1c or later. For more information, see KB 51124.
To work around this issue if you do not want to upgrade: Migration from a Windows vCenter Server: During a migration from a Windows vCenter Server disable IPv6 on the source vCenter Server.Ensure only IPv4 addresses are returned by your DNS server when performing a lookup against the vCenter Server FQDN.Once the migration is complete re-enable the IPv6 protocol, set the required IPv6 addresses, and restore the IPv6 DNS entries. Deployment vCenter Server Appliance 6.5: During a deployment of vCSA 6.5 use IPv4 values and ensure that only IPv4 addresses are returned by your DNS server when performing a lookup against the FQDN.Once the deployment is complete enable the IPv6 protocol, set the required IPv6 addresses, and restore the IPv6 DNS entries.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
