maas dns entry missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned |
Bug Description
juju 1.24.6
MAAS 1.8.2+bzr4041-
2. Can't find node on MAAS DNS Server
nexenta@ubuntu:~$ juju status --format tabular
[Services]
NAME STATUS EXPOSED CHARM
[Units]
ID STATE VERSION MACHINE PORTS PUBLIC-ADDRESS
[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.24.6 dim-care.maas /MAAS/api/
1 started 1.24.6 stupid-things.maas /MAAS/api/
nexenta@ubuntu:~$ dig dim-care.maas
; <<>> DiG 9.9.5-3ubuntu0.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48918
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;dim-care.maas. IN A
;; ANSWER SECTION:
dim-care.maas. 300 IN A 172.17.0.106
;; AUTHORITY SECTION:
maas. 300 IN NS maas.
;; ADDITIONAL SECTION:
maas. 300 IN A 172.17.0.4
;; Query time: 0 msec
;; SERVER: 172.17.
;; WHEN: Wed Oct 14 15:08:48 PDT 2015
;; MSG SIZE rcvd: 88
nexenta@ubuntu:~$ dig stupid-things.maas
; <<>> DiG 9.9.5-3ubuntu0.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49183
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;stupid-
;; AUTHORITY SECTION:
maas. 300 IN SOA maas. nobody.example.com. 232 600 1800 604800 300
;; Query time: 0 msec
;; SERVER: 172.17.
;; WHEN: Wed Oct 14 15:09:31 PDT 2015
;; MSG SIZE rcvd: 101
So I can't ssh to node via juju ssh stupid-things.maas
tags: | added: adoption charmers cpp |
Changed in maas: | |
milestone: | 1.8.3 → 1.8.4 |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
no longer affects: | maas/1.8 |
Hi Anton,
Can you please attach:
1. MAAS logs (/var/log/ maas/*. log)
2. syslog
3. On the machine that you are running juju from, what's in /etc/resolv.conf
That being said, I'll be marking this bug as incomplete until the information requested is provided.
Thanks.