MAAS

[2.0b8] Commissioing/deploying OS doesn't configure the default domain to search

Bug #1595633 reported by Lee Trager
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Low
Unassigned
MAAS 2.2.0

Bug Description

The commissioning/deploying OS isn't configured to search any domain by default. This causes the lookup sudo does to fail and a warning is printed. These warnings are being captured in the commissioning output so any commissioning script which uses sudo creates a test.err file containing

sudo: unable to resolve host maas-test-1

This is creating 00-maas-01-lshw.err and 00-maas-07-block-devices.err when a host is commissioned with the default commissioning scripts.

See original description
Lee Trager (ltrager)
description: updated
Andres Rodriguez (andreserl)
summary: - [2.0RC1] Commissioing/deploying OS doesn't configure the default domain
+ [2.0b8] Commissioing/deploying OS doesn't configure the default domain
to search
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.0.0 → 2.2.0
Revision history for this message
Lee Trager (ltrager) wrote :

Adding the default domain name via DHCP may break things for people not expected it to be there. For now solve this as described in 1670444.

Changed in maas:
status: Triaged → Won't Fix
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.