When using multiple NICs, VM HA does not work if you have configured zone wide NFS.

[jms345]

ISSUE TYPE

Bug Report

COMPONENT NAME

HA, Storage

CLOUDSTACK VERSION

4.11.0

CONFIGURATION

Basic networking, 3 NICs, management, Guest, storage, zone wide NFS storage

OS /ENVIRONMENT

CentOS Linux release 7.5.1804 (Core)

SUMMARY

When using multiple NICs as described above VM HA does not work if you have configured zone wide NFS.

When the power is disconnected from one of the compute nodes the management server logs show the ping timeouts but it never confirms that the host is down so in the UI its state is "Alert" not "Down". Because of this there is no attempt to restart the VMs on another of the compute nodes.

With cluster wide NFS instead VM HA works with multiple NICs.

The same happens with 2 as opposed to 3 NICs so I think it is just if you split traffic across the NICs.

I ran two comparison tests -

1. all traffic over single NIC, zone wide NFS - worked
2. management/storage on one NIC, guest on another, zone wide NFS - did not work

and I have the management server logs for both tests if needed ?

[rafaelweingartner]

@jms345 is this still a valid issue? If it is not, we can close it.

[jms345]

Still valid. I removed it because of some further testing that complicated things but it is still a bug as far as I know. Do you want me to update with details ? [image: dcplogo]

…

On 20 June 2018 at 10:58, Rafael Weingärtner ***@***.***> wrote: @jms345 <https://github.com/jms345> is this still a valid issue? If it is not, we can close it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2708 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AmTmbZbVqQDpS6Gu1WB-NRNju7YF-JzEks5t-hzYgaJpZM4UmCES> .

[rafaelweingartner]

Yes please. Otherwise, someone might close it.

[jms345]

updated

…

On 20 June 2018 at 11:03, Rafael Weingärtner ***@***.***> wrote: Yes please. Otherwise, someone might close it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2708 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AmTmbWGvbUvaeYFue1XgbnL20RcjA_Nrks5t-h3fgaJpZM4UmCES> .

[DaanHoogland]

@jms345 have you ran into this on newer versions as well? Any work done on this?

[rohityadavcloud]

@jms345 are you able to reproduce this with latest master or 4.14.0.0?

[DaanHoogland]

@jms345 there seems to be low interest in this issue. How are you dealing with this and is it still an issue?