MAAS

[2.0a] Enabling dhcpd in two vlans on different fabrics results on dhcpd being configured only for one

Bug #1552456 reported by Andres Rodriguez on 2016-03-02

This bug report is a duplicate of: Bug #1552448: [2.0a1] After upgrade form 1.10, dhcpd is enabled on wrong interface. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	MAAS	New	Critical	Unassigned	MAAS 2.0.0

Bug Description

I have more than two fabrics with:

fabric-0 untagged vlan with only subnet of 192.168.122.1/24 -> on virbr0
fabric-3 untagged vlan with only subnet of 192.168.133.1/24 -> on virbr2

I first managed DHCP on the untagged vlan on fabric-0 and secondly, I managed untagged vlan on fabric-3. However, while PXE booting, I noticed that /var/lib/maas/dhcpd-interfaces got configured against the interface connected to the last network I decided to managed and not both:

/var/lib/maas/dhcpd-interfaces had: virbr2

Andres Rodriguez (andreserl) on 2016-03-02

Changed in maas:
importance:	Undecided → Critical
milestone:	none → 2.0.0

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1552448 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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