weizhouapache commented on issue #8761:
URL: https://github.com/apache/cloudstack/issues/8761#issuecomment-2298268888
> I recently upgraded my environment to 4.15.2 and I'm seeing a similar
issue. I spent some time digging into this a bit more on my system. Here's what
I have found.
>
> **Works as expected** Step 1) Create - VPC Router using the System
Offering For Software Router - DHCP/DNS alerts are fine Step 2) Create VPC
Guest Network with DHCP enabled - DHCP/DNS alerts are fine Step 3) Create VM in
guest network - DHCP/DNS alerts are fine - VM is added to "VirtualMachines" in
/root/health_checks_data.json - DNS check - entry for VM is added into
/etc/hosts - DHCP check - entry for VM exists in /etc/dhcphosts.txt file
>
> ** Causes failed healthchecks ** Step 1) Create - VPC Router using the
System Offering For Software Router - DHCP/DNS checks pass Step 2) Create VPC
Guest Network ** without DHCP ** - DHCP/DNS checks pass Step 3) Create VM in
guest network - DHCP/DNS checks fail - Entry for this VM is added to
"VirtualMachines" in /root/health_checks_data.json - DNS check - Entry for this
VM is not added in /etc/hosts - DHCP check - No /etc/dhcphosts.txt file created
>
> ** Causes failed healthchecks ** Step 1) Create - VPC Router using the
System Offering For Software Router - DHCP/DNS alerts pass Step 2) Create VPC
Guest Network with DHCP enabled - DHCP/DNS alerts are fine Step 3) Create VM in
DHCP enabled guest network - DHCP/DNS alerts are fine - Entry for this VM is
added to "VirtualMachines" in /root/health_checks_data.json - DNS check - Entry
for this VM is added into /etc/hosts - DHCP check -Entry for this VM exists in
/etc/dhcphosts.txt file Step 4) Create VPC Guest Network ** without DHCP ** -
DHCP/DNS alerts pass Step 5) Create VM in non-DHCP enabled guest network -
DHCP/DNS checks fail - Entry for this VM is added to "VirtualMachines" in
/root/health_checks_data.json - DNS check - Entry for this VM is not added in
/etc/hosts - DHCP check - Entry for this VM does not exist in the
/etc/dhcphosts.txt file
>
> Does it make sense to add entries for machines in non-DHCP enabled
networks to /root/health_checks_data.json ??
@zenbiking
I tried to reproduce the issue, however, I was not able to.
```
root@r-337-VM:~# cat /root/health_checks_data.json
{
...
"virtualMachines":
"vmName=VPC-natted-001,macAddress=02:01:02:05:00:01,ip=172.21.0.90,dhcp=true,dns=true;vmName=VPC-natted-002-no-dhcp-dns,macAddress=02:01:02:c2:00:01,ip=172.21.1.214,dhcp=false,dns=false;"
}
}
```
The health check data indicates that dhcp/dns are not supported
(dhcp=false,dns=false) for vm on the network without Dhcp/Dns (refer to #5554).
@zenbiking
can you share the file `/root/health_checks_data.json ` in the vpc vr ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
