Unable to commision/deploy(/enlist) when having a tagged only network setup

Bug #1719316 reported by Fairbanks.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

Hello there,

Trying to deploy/commision/enlist etc... using a tagged only network is impossible with MAAS.
In a network environment where we only have tagged vlan networks i am unable to use MAAS.

I can configure the bare-metal systems to pxe-boot from this specific vlan, that all seems to go nicely, until the booted image tries to do a DHCP request. This does it using no vlan at all, ant thus fails. It would be nice if it was possible to use a PXE VLAN setting or something so that the DHCP Request uses a vlan instead of always an untagged network!

I know this maybe is a corner case, but it is a valid option, also since lots of modern hardware of Dell and HP allow to configure a VLAN for PXE Boot.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

At the moment, it is not possible to run ephemeral environments with custom network configuration. Effectively, you can't run commissiong or any other epemeral environment that requires you to tag an network interface to access the network.

I'll mark this as a wishlist, but it is not currently part of our plans.

Changed in maas:
milestone: none → next
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → 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.