fqdn of a node from a disconnected cluster doesn't have a domain part

Bug #1457504 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Raphaël Badin

Bug Description

1. Install MAAS
2. Add Chassis (i.e. Virsh)

    NOTE that at this point NO cluster interfaces are configured in the default cluster.

3. Nodes are added like:

node01
node02
node03

4. Configured Cluster Interface to manage DHCP/DNS
5. Nodes are updated to have the domain name:

node01.maas
node02.maas
node03.maas

6. If you change the configured Cluster Interface to Unmanage, it will remove the domain name from the nodes.

The problem here, is that the domain name is configured by cluster controller and not by cluster interface. So even if the cluster interfaces are not configured, the cluster controller still has a default domain name.

Related branches

description: updated
Changed in maas:
milestone: none → 1.8.0
importance: Undecided → High
Raphaël Badin (rvb)
summary: - Adding nodes via probe-and-enlist (tested with virsh) without having a
- cluster configure results in nodes not having a fqdn
+ fqdn of nodes from a disconnected cluster don't have a having a domain
+ part
Changed in maas:
status: New → Triaged
summary: - fqdn of nodes from a disconnected cluster don't have a having a domain
- part
+ fqdn of nodes from a disconnected cluster don't have a domain part
summary: - fqdn of nodes from a disconnected cluster don't have a domain part
+ fqdn of a node from a disconnected cluster doesn't have a domain part
Raphaël Badin (rvb)
Changed in maas:
status: Triaged → Fix Committed
assignee: nobody → Raphaël Badin (rvb)
Changed in maas:
status: Fix Committed → Fix Released
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.