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 | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
| 1.2 |
Fix Released
|
Critical
|
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')
e.g: http://
$ juju status
machines:
[...]
2:
agent-state: running
dns-name: nekp8.master
[...]
services:
[...]
wordpress/0:
[...]
public-
Related branches
lp:~rvb/maas/metadata-fix-hostname
- Julian Edwards (community): Approve
-
Diff: 51 lines (+15/-5)2 files modifiedsrc/metadataserver/api.py (+1/-1)
src/metadataserver/tests/test_api.py (+14/-4)
lp:~rvb/maas/metadata-fix-hostname-1.2
- Julian Edwards (community): Approve
-
Diff: 51 lines (+15/-5)2 files modifiedsrc/metadataserver/api.py (+1/-1)
src/metadataserver/tests/test_api.py (+14/-4)
- Launchpad code reviewers: Pending requested
-
Diff: 182 lines (+88/-5) (has conflicts)5 files modifiedsrc/maasserver/templates/maasserver/tag_view.html (+6/-0)
src/maasserver/tests/test_views_tags.py (+58/-0)
src/maasserver/views/tags.py (+9/-0)
src/metadataserver/api.py (+1/-1)
src/metadataserver/tests/test_api.py (+14/-4)
lp:~andreserl/maas/quantal_update_changelog
- Andres Rodriguez (community): Approve
-
Diff: 31 lines (+23/-1)1 file modifieddebian/changelog (+23/-1)
Revision history for this message
| Raphaël Badin (rvb) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → In Progress |
| description: | updated |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.