MAAS should prevent deploying nodes with PXE interface 'unconfigured' (or all NIC's as 'Unconfigured')

Bug #1513095 reported by Andres Rodriguez on 2015-11-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Lee Trager

Bug Description

MAAS allows users deploy a machine that have the PXE interface as 'Unconfigured' as well as deploying a node with *ALL* NIC's as 'Unconfigured'.

Where we saw it it was a node with 2 NIC's that were made bond0, and on deployment, the bond0 for the 'Ip Address' field, it was 'Unconfigured'.

MAAS allowed the user to deploy, but after deployment, it obviously failed to contact metadta sever because no NIC configured.

Related branches

Blake Rouse (blake-rouse) wrote :

MAAS should make sure that at lease one interface can communicate back to MAAS. I don't know if it has to be the PXE interface.

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 1.9.0
tags: added: networking ui
Lee Trager (ltrager) on 2015-11-05
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Jared Baker (shubjero) wrote :

Deploying a server with PXE enabled interface 'bond0' as 'unconfigured' is still possible in MAAS 2.0. Results in a traceback during stage config and stage final. See attached screenshot.

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

Other bug subscribers

Bug attachments