VR failing health checks on certain checks 4.18

[Chih80]

ISSUE TYPE

• Bug Report

COMPONENT NAME

VR, UI

CLOUDSTACK VERSION

4.18

CONFIGURATION

advanced networking

OS / ENVIRONMENT

CS management server running on ubuntu 22.04 and hosts running on ubuntu 20.04

SUMMARY

I keep getting ROUTER.HEALTH.CHECKS indicating "has failing checks: dns_check.py, dhcp_check.py". Everything seems to be working. My VMs are online so not sure what to make of it. I'm not sure if I should just exclude those 2 checks from global config or will there be any issues excluding those 2 checks from global config.

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

[weizhouapache]

this looks same as #8177 #8569

just to confirm, did you update the name of vms ?

[Chih80]

this looks same as #8177 #8569

just to confirm, did you update the name of vms ?

I did not update the name of the VM. As a matter of fact, I didn't really do anything. I made VMs, assign it the network and that's about it.

[weizhouapache]

this looks same as #8177 #8569
just to confirm, did you update the name of vms ?

I did not update the name of the VM. As a matter of fact, I didn't really do anything. I made VMs, assign it the network and that's about it.

ok. @Chih80
do the VMs have multiple nics ?

[Chih80]

this looks same as #8177 #8569
just to confirm, did you update the name of vms ?

I did not update the name of the VM. As a matter of fact, I didn't really do anything. I made VMs, assign it the network and that's about it.

ok. @Chih80 do the VMs have multiple nics ?

Some does but I doubt this matters. This has been happening from the get-go when all the VMs had one nic.

[weizhouapache]

I checked some similar tickets #8569 #7653 #8177 #8158

• all issues happens with 4.18.0 or 4.18.1
• shared network (Failed VR health check #8177, Virtual Router Failing Health Check Due To Missing Entries in /etc/hosts #7653, dnsmasq-dhcp - ignored #8158). network type is not specified in Router health checks failed #8569 and VR failing health checks on certain checks 4.18 #8761

I suspect it has been fixed by #8741

@Chih80
are you still facing the issue ?
what type of network do you use ?