maas dns entry missing

Bug #1508501 reported by Anton Skriptsov on 2015-10-21
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Undecided
Unassigned

Bug Description

juju 1.24.6
MAAS 1.8.2+bzr4041-0ubuntu1~trus all

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.0/nodes/node-ac72ae64-72b5-11e5-88f8-005056b9a096/ trusty arch=amd64 cpu-cores=4 mem=12288M
1 started 1.24.6 stupid-things.maas /MAAS/api/1.0/nodes/node-0e1e7140-72b9-11e5-ba86-005056b9a096/ trusty arch=amd64 cpu-cores=4 mem=12288M

nexenta@ubuntu:~$ dig dim-care.maas

; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> dim-care.maas
;; 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.0.4#53(172.17.0.4)
;; WHEN: Wed Oct 14 15:08:48 PDT 2015
;; MSG SIZE rcvd: 88

nexenta@ubuntu:~$ dig stupid-things.maas

; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> stupid-things.maas
;; 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-things.maas. IN A

;; AUTHORITY SECTION:
maas. 300 IN SOA maas. nobody.example.com. 232 600 1800 604800 300

;; Query time: 0 msec
;; SERVER: 172.17.0.4#53(172.17.0.4)
;; 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
Andres Rodriguez (andreserl) wrote :

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.

Changed in maas:
status: New → Incomplete
milestone: none → 1.8.3

Ok. Will collect logs shortly
Thanks

On Wed, Oct 21, 2015 at 7:08 PM, Andres Rodriguez <email address hidden>
wrote:

> 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.
>
> ** Changed in: maas
> Status: New => Incomplete
>
> ** Changed in: maas
> Milestone: None => 1.8.3
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1508501
>
> Title:
> maas dns entry missing
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> juju 1.24.6
> MAAS 1.8.2+bzr4041-0ubuntu1~trus all
>
>
> 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.0/nodes/node-ac72ae64-72b5-11e5-88f8-005056b9a096/ trusty
> arch=amd64 cpu-cores=4 mem=12288M
> 1 started 1.24.6 stupid-things.maas
> /MAAS/api/1.0/nodes/node-0e1e7140-72b9-11e5-ba86-005056b9a096/ trusty
> arch=amd64 cpu-cores=4 mem=12288M
>
> nexenta@ubuntu:~$ dig dim-care.maas
>
> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> dim-care.maas
> ;; 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.0.4#53(172.17.0.4)
> ;; WHEN: Wed Oct 14 15:08:48 PDT 2015
> ;; MSG SIZE rcvd: 88
>
> nexenta@ubuntu:~$ dig stupid-things.maas
>
> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> stupid-things.maas
> ;; 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-things.maas. IN A
>
> ;; AUTHORITY SECTION:
> maas. 300 IN SOA maas. nobody.example.com.
> 232 600 1800 604800 300
>
> ;; Query time: 0 msec
> ;; SERVER: 172.17.0.4#53(172.17.0.4)
> ;; 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1508501/+subscriptions
>

Changed in maas:
milestone: 1.8.3 → 1.8.4
Download full text (3.6 KiB)

nexenta@ubuntu:/var/log$ sudo cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.3.199.30

10.3.199.30 its our lab DNS and DHCP server

On Wed, Oct 21, 2015 at 8:17 AM, Anton Skriptsov <
<email address hidden>> wrote:

> Ok. Will collect logs shortly
> Thanks
>
> On Wed, Oct 21, 2015 at 7:08 PM, Andres Rodriguez <<email address hidden>
> > wrote:
>
>> 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.
>>
>> ** Changed in: maas
>> Status: New => Incomplete
>>
>> ** Changed in: maas
>> Milestone: None => 1.8.3
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1508501
>>
>> Title:
>> maas dns entry missing
>>
>> Status in MAAS:
>> Incomplete
>>
>> Bug description:
>> juju 1.24.6
>> MAAS 1.8.2+bzr4041-0ubuntu1~trus all
>>
>>
>> 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.0/nodes/node-ac72ae64-72b5-11e5-88f8-005056b9a096/ trusty
>> arch=amd64 cpu-cores=4 mem=12288M
>> 1 started 1.24.6 stupid-things.maas
>> /MAAS/api/1.0/nodes/node-0e1e7140-72b9-11e5-ba86-005056b9a096/ trusty
>> arch=amd64 cpu-cores=4 mem=12288M
>>
>> nexenta@ubuntu:~$ dig dim-care.maas
>>
>> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> dim-care.maas
>> ;; 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.0.4#53(172.17.0.4)
>> ;; WHEN: Wed Oct 14 15:08:48 PDT 2015
>> ;; MSG SIZE rcvd: 88
>>
>> nexenta@ubuntu:~$ dig stupid-things.maas
>>
>> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> stupid-things.maas
>> ;; 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-things.maas. ...

Read more...

Mark W Wenning (mwenning) wrote :

Workaround : try adding the lines

nameserver <my-maas-ip>
search maas

To the resolv.conf file

That works in my lab.

Kyle (v-kypife) wrote :

Looks like this might be resolved already, but if anyone is looking for a more permanent solution if you are getting annoyed by resolv.conf being overwritten, you could also modify:

/etc/resolvconf/resolv.conf.d/base { or head or tail }

and add:

nameserver <my-maas-ip>
search maas

Gavin Panella (allenap) wrote :

I don't think that workaround will work for Anton's bug as described. He's seeing a situation where one node's address is being published via DNS and one which isn't. That seems like it's a genuine bug in MAAS. I will ask someone more recently familiar with this code to comment.

LaMont Jones (lamont) wrote :

I have a couple of questions, if this situation is still in play:
1) what does this produce: dig axfr maas. @172.17.0.4
2) does the problem go away if you restart the cluster and region controllers?

lamont

Gavin Panella (allenap) on 2016-01-25
Changed in maas:
status: Incomplete → New
status: New → Incomplete

Hi!
On friday I have switched to devel branch, and right now I can't reproduce
that issue.
If do, I will email you

Thanks for questions

On Mon, Jan 25, 2016 at 5:58 PM, LaMont Jones <email address hidden>
wrote:

> I have a couple of questions, if this situation is still in play:
> 1) what does this produce: dig axfr maas. @172.17.0.4
> 2) does the problem go away if you restart the cluster and region
> controllers?
>
> lamont
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1508501
>
> Title:
> maas dns entry missing
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> juju 1.24.6
> MAAS 1.8.2+bzr4041-0ubuntu1~trus all
>
>
> 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.0/nodes/node-ac72ae64-72b5-11e5-88f8-005056b9a096/ trusty
> arch=amd64 cpu-cores=4 mem=12288M
> 1 started 1.24.6 stupid-things.maas
> /MAAS/api/1.0/nodes/node-0e1e7140-72b9-11e5-ba86-005056b9a096/ trusty
> arch=amd64 cpu-cores=4 mem=12288M
>
> nexenta@ubuntu:~$ dig dim-care.maas
>
> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> dim-care.maas
> ;; 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.0.4#53(172.17.0.4)
> ;; WHEN: Wed Oct 14 15:08:48 PDT 2015
> ;; MSG SIZE rcvd: 88
>
> nexenta@ubuntu:~$ dig stupid-things.maas
>
> ; <<>> DiG 9.9.5-3ubuntu0.5-Ubuntu <<>> stupid-things.maas
> ;; 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-things.maas. IN A
>
> ;; AUTHORITY SECTION:
> maas. 300 IN SOA maas. nobody.example.com.
> 232 600 1800 604800 300
>
> ;; Query time: 0 msec
> ;; SERVER: 172.17.0.4#53(172.17.0.4)
> ;; 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1508501/+subscriptions
>

Gavin Panella (allenap) wrote :

Anton, thanks for your reply. I'm going to assume this does not manifest in trunk.

Changed in maas:
status: Incomplete → Invalid
no longer affects: maas/1.8
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers