[IPv6] DHCP6 problems prevent DHCP from starting

Bug #1594207 reported by Lloyd Parkes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned

Bug Description

The exception maasserver.exceptions.DHCPConfigurationError needs some more work done to it.

Firstly, if this exception is thrown while configuring either of DHCP or DHCP6, then neither service will be configured. In my case, DHCP6 could not be configured, but DHCP would not get configured either.

Secondly, the exception doesn't say which version of DHCP could not be configured which is unhelpful given the first problem.

In my case this exception was being thrown from line 390 of maasserver/dhcp.py.

The root cause of this in my case was having my IPv4 and IPv6 networks configured in MAAS, defining a dynamic range on my IPv4 network and then disabling the IPv6 address on my router. This caused the SLAAC assigned address on my rack controller to disappear which in turn meant that dhcp.py couldn't find an interface to attach DHCP6 to.

Revision history for this message
Lloyd Parkes (lloyd+lp) wrote :
Revision history for this message
Lloyd Parkes (lloyd+lp) wrote :
Revision history for this message
Lloyd Parkes (lloyd+lp) wrote :

Herein is evidence that very little survives first contact with my lab network. You should just look at the trimmed log.

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.1.0
Revision history for this message
Mike Pontillo (mpontillo) wrote :

Thanks for your feedback and for taking the time to file this.

We're planning on doing some additional IPv6 work for the next release of MAAS, so I'll target this for MAAS 2.1.

Changed in maas:
importance: Medium → High
tags: added: error-surface notifications
tags: removed: notifications
Changed in maas:
milestone: 2.0.1 → 2.1.0
summary: - DHCP6 problems prevent DHCP from starting
+ [IPv6] DHCP6 problems prevent DHCP from starting
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Revision history for this message
Andres Rodriguez (andreserl) wrote :

**This is an automated message**

We believe this issue has now been resolved in the latest MAAS releases. As such, we are marking this bug as Fix Released. If you believe this issue is still present, please re-open this bug report and provide any relevant information.

Thanks.

Changed in maas:
status: Triaged → Fix Released
milestone: 2.1.3 → none
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.