dnsmasq configuration does not match/check interface settings

Bug #1748186 reported by Olivier Bourdon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bifrost
Fix Released
Undecided
Olivier Bourdon

Bug Description

Let's assume Bifrost machine comes with 2 net itfs, one public to got to the outside net (eth0)
and one private to serve on an internal/restricted network for the provisioning of VMs (eth1)

when running the playbook, you can specify which interface Bifrost will use for dnsmasq (vibr0 by default) using:
ansible-playbook -i inventory/target install.yaml -e network_interface=eth1

However if eth1 is not on a 192.168.1.0/24 subnet and due to the default dhcp_* values in
playbooks/roles/bifrost-ironic-install/defaults/main.yml your might very well end up into
a non-functional /etc/dnsmasq.conf configuration

The very least would be to check value for coherency and potentially correct values if possible

Changed in bifrost:
assignee: nobody → Olivier Bourdon (olivierbourdon38)
status: New → In Progress
Revision history for this message
Olivier Bourdon (olivierbourdon38) wrote :
Changed in bifrost:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/bifrost 5.1.0

This issue was fixed in the openstack/bifrost 5.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.