ccycv opened a new issue, #8158:
URL: https://github.com/apache/cloudstack/issues/8158
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
VR - DHCP
~~~
##### CLOUDSTACK VERSION
~~~
ACS 4.18.1 with router upgraded to 4.18.1
~~~
##### CONFIGURATION
~~~
Shared and Advanced network configuration with multiple CIDR in different
zones. DHCP service provided by dnsmasq.
~~~
##### OS / ENVIRONMENT
~~~
Cloudstack + VMware
~~~
##### SUMMARY
The DHCP service on the CloudStack guest router is ignoring DHCP requests
for specific IP classes post deployment. Manually adding missing classes to the
configuration resolves the issue temporarily.
##### STEPS TO REPRODUCE
~~~
- The issue occurs when the system is configured with multiple CIDRs and
DHCP options for some classes are missing.
- Comparing the `dhcp-option` entries from a router with a working
configuration to the one with issues shows a lack of certain DHCP options for
the non-working IP classes.
- After adding the missing classes manually to `cloud.conf`, the issue seems
to be resolved, suggesting a bug in DHCP configuration generation or
application.
[root@r-6143-VMAMS:/etc/dnsmasq.d#](mailto:root@r-6143-VMAMS:/etc/dnsmasq.d#)
cat cloud.conf
listen-address=127.0.0.1,23.29.xxx.130
dhcp-range=set:interface-eth0-0,23.29.xxx.130,static
dhcp-option=tag:interface-eth0-0,15,my.host
dhcp-option=tag:interface-eth0-0,6,23.29.xxx.130,8.8.8.8
dhcp-option=tag:interface-eth0-0,3,23.29.xxx.129
dhcp-option=eth0,26,1500
dhcp-option=tag:interface-eth0-0,1,255.255.255.224
[root@r-6143-VMAMS:/etc/dnsmasq.d#](mailto:root@r-6143-VMAMS:/etc/dnsmasq.d#)
root@r-6143-VMAMS:~# grep -v '^#\|^$' /etc/dnsmasq.conf domain-needed
bogus-priv resolv-file=/etc/dnsmasq-resolv.conf
local=/my.host/
except-interface=eth1
except-interface=eth2
except-interface=lo
no-dhcp-interface=eth1
no-dhcp-interface=eth2
expand-hosts
domain=my.host
domain=my.host
domain=my.host
dhcp-range=217.79.xxx.129,static
dhcp-hostsfile=/etc/dhcphosts.txt
dhcp-ignore=tag:!known
dhcp-option=15,"my.host "
dhcp-option=vendor:MSFT,2,1i
dhcp-boot=pxelinux.0
enable-tftp
tftp-root=/opt/tftpboot
dhcp-lease-max=2100
domain=shape.host
log-facility=/var/log/dnsmasq.log
conf-dir=/etc/dnsmasq.d
dhcp-optsfile=/etc/dhcpopts.txt
localise-queries
dhcp-option=option:router,217.79.xxx.129
dhcp-option=6,217.79.xxx.130,8.8.8.8
dhcp-client-update
~~~
##### EXPECTED RESULTS
~~~
The expected result is that all the IP classes should be served by the DHCP
without needing manual intervention. All IP ranges should have appropriate
`dhcp-option` configurations applied automatically.
~~~
##### ACTUAL RESULTS
~~~
Some IP classes are being ignored by the DHCP service, leading to instances
not receiving an IP upon boot. This issue is observed across different CIDRs in
the same zone and requires manual addition of missing `dhcp-option`
configurations to resolve.
~~~
--
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]
