MAAS, using amt, cannot guarantee that the correct machine is being contacted

Bug #1276450 reported by Juan L. Negron
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned

Bug Description

When using MAAS with a node managed with AMT power management tools, there is no guarantee that MAAS will power on/off/cycle the correct node.

Normally, with IPMI, a static IP address is used for power management. When using AMT there is no guarantee that the IP address that the node had when commissioned, will persist. This creates a situation where MAAS could try to power on/off the wrong machine.

This behavior was observed in the micro clusters.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1276450] [NEW] MAAS, using amt, cannot guarantee that the correct machine is being contacted

Can you confirm that you have enough IP addresses in your DHCP range?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Ok we think we know what's going on here.

We suspect that the nodes enlisted but were not accepted for commissioning until after the initial DHCP lease had run out. This would not be a problem for the regular boot etc but the power address parameter would now obviously be wrong.

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 14.04
Revision history for this message
Julian Edwards (julian-edwards) wrote :

I think it can be fixed by assigning the static MAC/IP map when enlisting rather than waiting until the node is accepted.

information type: Public → Private
information type: Private → Public
Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
tags: added: maas-hwe
Changed in maas:
assignee: Andres Rodriguez (andreserl) → nobody
Revision history for this message
Tycho Andersen (tycho-s) wrote :

So I think this is fixed in part by http://bazaar.launchpad.net/~maas-maintainers/maas/trunk/revision/1944 , although the DNS issues would also be good to fix.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

What are the "DNS issues"? They are not mentioned elsewhere here.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I think this was fixed, re-open if not.

Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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