Nodes are deployed with wrong domain name.

Bug #1078744 reported by Raphaël Badin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raphaël Badin
Raphaël Badin

Bug Description

When DNS is managed, nodes are deployed with the wrong domain name (i.e. running 'hostname -f' returns a wrong domain name).

Apparently, node.hostname is used instead of node.fqdn.

The result is that juju uses the wrong hostname for a node. That hostname is used to connect services together.

In the following example, node.hostname is 'nekp8.local' and node.fqdn is 'nekp8.master' (DNS is managed and the domain name is 'master')
$ juju status
    agent-state: running
    dns-name: nekp8.master
      public-address: nekp8.local

Related branches

Revision history for this message
Raphaël Badin (rvb) wrote :

After some investigation, I found the problem: juju uses 'hostname -f' to find the hostname used for the 'public-address' field. That hostname is set by cloud-init which, in turn, fetches that from the metadata service.

Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → In Progress
description: updated
Raphaël Badin (rvb)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints