Enabling VCHA Fails with error : The operation is not allowed in the current state. Failed to get management network information.

Products

• VMware vCenter Server

Issue/Introduction

When trying to configure VCHA, the action fail with the following error displayed :

"The operation is not allowed in the current state.

Failed to get management network information. Verify if management interface (NIC0) is configured correctly and is reachable, and verify if correct DNS mapping is provided for forward and reverse hostname lookup."

you may see the following log extract at the time of the failure:

vsphere_client_virgo.logs

 [ERROR] p-nio-127.0.0.1-5090-exec-21 70000171 100006 200007 com.vmware.vsphere.client.h5.vcha.VchaMutationProvider            Error while calling vcha active.get com.vmware.vapi.std.errors.Error: Error (com.vmware.vapi.std.errors.error) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = InvalidState.summary,
    defaultMessage = The operation is not allowed in the current state.,
    args = [],
    params = <null>,
    localized = <null>
}, LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vcenter.vcha.error.invalidFailoverNicConfig,
    defaultMessage = Failed to get management network information. Verify if management interface (NIC0) is configured correctly and is reachable, and verify if correct DNS mapping is provided for forward and reverse hostname lookup.,
    args = [],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = ERROR
}

vpxd.log  

info vpxd[2870089] [Originator@6876 sub=FailoverClusterOperator opID=xxx:70000171-19] -- BEGIN -- com.vmware.vcenter.vcha.cluster.active.get

error vpxd[2870089] [Originator@6876 sub=FailoverClusterOperator opID=xxx:70000171-19] Exception: N3Vim5Fault12InvalidState9ExceptionE(Fault cause: vim.fault.InvalidState
--> )
--> [context]zKq7AVECAQAAACqAeAEVdnB4ZAAAQxxTbGlidm1hY29yZS5zbwAACBhCACk/QwCWmUqBU0U6AWxpYnZpbS10eXBlcy5zbwCBfmM6AYGWWDsBgcpYOwGCzxcrAnZweGQAgmQYKwKCT3kqAoKMoSgCgwew4AFsaWJjb21fdm13YXJlX3ZjZW50ZXJfcGxhdGZvcm1sZXNzYmluZGluZ3NfY3BwLnNvAIM2seABBF9zE2xpYmNvbV92bXdhcmVfdmNlbnRlcl9zdmNhY2NvdW50bWdtdF9wbGF0Zm9ybWxlc3NiaW5kaW5nc19jcHAuc28Agn0xSgEABOw3ABdFOADFD1EFsI4AbGlicHRocmVhZC5zby4wAAbf+g9saWJjLnNvLjYA[/context]
info vpxd[2870089] [Originator@6876 sub=FailoverClusterOperator opID=xxx:70000171-19] com.vcenter.vcha.cluster.active.get Request:
--> VcSpec: null
--> Partial: false
info vpxd[2870089] [Originator@6876 sub=FailoverClusterOperator opID=xxx:70000171-19] -- END -- com.vmware.vcenter.vcha.cluster.active.get

Environment

vCenter 7.0.x

Cause

This is due when the ifaces.py script cannot read the eth0 network details or fail to return the required information.

com.vmware.vcenter.vcha.cluster.activate.get API call fails to process the output returned by the script due to format mismatch 

the expected output format should be :

ifName family address netmask mac fqdn
gateway
dnsserver1 dnsserver2 dnsserver3...

while running the command on VCSA

#sudo -u vpxd /bin/sudo_py_vmw_path_wrapper.sh /usr/lib/vmware-vcha/scripts/ifaces.py eth0 -d

returns an output similar to :

/etc/profile.d/proxy.sh: line 11: Enable: command not found
eth0 4 xxx.xxx.xxx.xxx 24 ff:ff:ff:ff:ff:ff vcenter_fQDN
xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx

with the first line "/etc/profile.d/proxy.sh: line 11: Enable: command not found" not being able to be processed by the API.

Resolution

The script /etc/profile.d/proxy.sh load the proxy configuration file /etc/sysconfig/proxy

To fix the issue, review the proxy configuration file /etc/sysconfig/proxy in accordance with the following KB article :

how to configure Proxy Settings for vCenter Server

and also verify that there is no syntax error