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 >
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: /bugs.launchpad .net/bugs/ 1508501 0ubuntu1~ trus all 1.0/nodes/ node-ac72ae64- 72b5-11e5- 88f8-005056b9a0 96/ trusty 1.0/nodes/ node-0e1e7140- 72b9-11e5- ba86-005056b9a0 96/ trusty 5-Ubuntu <<>> dim-care.maas 0.4#53( 172.17. 0.4) 5-Ubuntu <<>> stupid-things.maas things. maas. IN A 0.4#53( 172.17. 0.4) /bugs.launchpad .net/maas/ +bug/1508501/ +subscriptions
> 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:/
>
> Title:
> maas dns entry missing
>
> Status in MAAS:
> Incomplete
>
> 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/
> arch=amd64 cpu-cores=4 mem=12288M
> 1 started 1.24.6 stupid-things.maas
> /MAAS/api/
> arch=amd64 cpu-cores=4 mem=12288M
>
> 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
>
> To manage notifications about this bug go to:
> https:/
>