-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refine a bit dnsmasq role #1702
Conversation
Thanks for the PR! ❤️ |
f76d66a
to
ed4233d
Compare
An assertion block was missing a condition, leading to issue when we wanted to just remove a network from the configuration. In the network configuration template, the test to know more about ipv4 and ipv6 ranges was a bit too loose, leading to issues under certain conditions. We faced the same issue in the host management, leading to potentially wrong DHCP configuration. In order to ease debugging, we now generate a fact, display its content, and use that content to inject the host data in the configuration. During a re-run, the service is already stopped/disabled, and the unit file is removed. Ansible will then fail, since systemd can't find the service to stop.
ed4233d
to
3116f53
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rebtoor The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
An assertion block was missing a condition, leading to issue when we
wanted to just remove a network from the configuration.
In the network configuration template, the test to know more about ipv4
and ipv6 ranges was a bit too loose, leading to issues under certain
conditions.
We faced the same issue in the host management, leading to potentially
wrong DHCP configuration. In order to ease debugging, we now generate a
fact, display its content, and use that content to inject the host data
in the configuration.
During a re-run, the service is already stopped/disabled, and the unit
file is removed. Ansible will then fail, since systemd can't find the
service to stop.
As a pull request owner and reviewers, I checked that: