MAAS

Hostname not set prior to commissioning

Bug #1058986 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned

Bug Description

When MAAS pxe-boots a node to commission it, it should provide the hostname for that node. This is what appears to be provided at the moment:

Booting (amd64) under MAAS direction...
nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:maas-precise-12.04-amd64-ephemeral-20120424 iscsi_target_ip=192.168.1.25 iscsi_target_port=3260 iscsi_initiator=node-0025904ce7ac.cloud.mallards ip=dhcp ro root=LABEL=cloudimg-rootfs overlayroot=tmpfs cloud-config-url=http://192.168.1.25/MAAS/metadata/latest/by-id/node-cb93491a-0ae5-11e2-8397-d4ae527ac129/?op=get_preseed log_host=192.168.1.25 log_port=514 console=tty1 console=ttyS0

When the machine comes up, it currently thinks its name is "ubuntu". It would be preferable for it to know its hostname at this stage, so that information could be provided to dhcpd and thence to the DNS system.

Mark Shuttleworth (sabdfl)
summary: - When commissioning a machine, MAAS should provide its hostname
+ MAAS should provide commissioning hostname
Julian Edwards (julian-edwards)
summary: - MAAS should provide commissioning hostname
+ Hostname not set prior to commissioning
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Possibly a dupe of bug 1046405

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

Other bug subscribers

Remote bug watches

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