vCenter HA fails on deployment at 40% with the error methodfault.summary

[bluechip01]

Just wondering if anybody has seen the above error when deploying the vcha

I have identical host names on the active/passive nodes

I am installing the advanced option and the active/passive nodes will have different ip's if there is a failover

Before I clicked finish I made sure that all nodes could ping each other

Also the host names are in lower case there is no mixed case

also getting the error below in the vcha.log

Any help would be greatly appreciated

ClusterPersistence::DoFetchDataSync] Open of file /etc/vmware-vcha/clusterconfig failed: No such file or directory

2018-03-16T11:40:21.174Z warning vcha[7FE9B84B37C0] [Originator@6876 sub=Cluster] [ClusterManagerImpl::ReadPersistentObject] Couldn't open clusterconfig

2018-03-16T11:40:21.174Z error vcha[7FE9B84B37C0] [Originator@6876 sub=Cluster] [ClusterPersistence::DoFetchDataSync] Open of file /etc/vmware-vcha/vmmetadata failed: No such file or directory

2018-03-16T11:40:21.174Z warning vcha[7FE9B84B37C0] [Originator@6876 sub=Cluster] [ClusterManagerImpl::ReadPersistentObject] Couldn't open vmmetadata

2018-03-16T11:40:21.174Z error vcha[7FE9B84B37C0] [Originator@6876 sub=Cluster] [ClusterPersistence::DoFetchDataSync] Open of file /etc/vmware-vcha/kvstore failed: No such file or directory

2018-03-16T11:40:21.174Z warning vcha[7FE9B84B37C0] [Originator@6876 sub=Cluster] [ClusterManagerImpl::ReadPersistentObject] Couldn't open kvstore

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::DsStateChange: Csi::Cluster::ClusterManagerImpl (listeners = 1)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::VmStateChange: Csi::Cluster::ClusterManagerImpl (listeners = 1)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::DumpStateChange: Csi::Cluster::ClusterManagerImpl (listeners = 2)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::ClusterConfigChange: Csi::Cluster::ClusterManagerImpl (listeners = 3)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::HostAgentCnxChange: Csi::Cluster::ClusterManagerImpl (listeners = 2)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=Default] [Notification::AddListener] Adding listener of type Csi::Notifications::CompleteClusterStateChange: Vcha::ClusterMgr (listeners = 1)

2018-03-16T11:40:21.174Z verbose vcha[7FE9B84B37C0] [Originator@6876 sub=ClusterMgr] Starting common cluster manager (CCM)...

[pwilk]

I believe you should do a clean retry of enabling HA. Restart vCenter server, remove /etc/vmware-vcha/clusterconfig and try enabling it again.

Please let me know if that works for you.

[bluechip01]

Thanks

I tried this but if you remove these files you can no longer re-enable vcha in the gui and you get errors about missing files in the prepare-vcha.log

[pwilk]

Force enable HA through SSH. I'll post the detailed guide later on as now I'm travelling

[jimfa]

Hello @pwilk , did you get around to write that blog on how to force vcha through ssh? Could contain helpfull information for me.