jujud caches (lack of) DNS servers

Bug #1298755 reported by Ryan Finnie on 2014-03-28
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned
juju-core
Medium
Unassigned

Bug Description

We restarted an agent at a time when resolv.conf was empty. The correct DNS servers were inserted a minute later, but jujud never picked up on this until it was once again restarted.

2014-03-24 15:20:03 INFO juju machine.go:109 machine agent machine-4 start
2014-03-24 15:20:03 DEBUG juju.agent agent.go:237 Reading agent config, format: format 1.16
2014-03-24 15:20:03 INFO juju runner.go:253 worker: start "api"
2014-03-24 15:20:03 INFO juju apiclient.go:111 state/api: dialing "wss://bootstrapnode.internal:17070/"
2014-03-24 15:20:03 ERROR juju apiclient.go:116 state/api: websocket.Dial wss://bootstrapnode.internal:17070/: lookup bootstrapnode.internal.: no DNS servers
2014-03-24 15:20:03 ERROR juju runner.go:211 worker: exited "api": websocket.Dial wss://bootstrapnode.internal:17070/: lookup bootstrapnode.internal.: no DNS servers
2014-03-24 15:20:03 INFO juju runner.go:245 worker: restarting "api" in 3s

[very, very large cut]

2014-03-28 00:24:35 INFO juju runner.go:253 worker: start "api"
2014-03-28 00:24:35 INFO juju apiclient.go:111 state/api: dialing "wss://bootstrapnode.internal:17070/"
2014-03-28 00:24:35 ERROR juju apiclient.go:116 state/api: websocket.Dial wss://bootstrapnode.internal:17070/: lookup bootstrapnode.internal.: no DNS servers
2014-03-28 00:24:35 ERROR juju runner.go:211 worker: exited "api": websocket.Dial wss://bootstrapnode.internal:17070/: lookup bootstrapnode.internal.: no DNS servers
2014-03-28 00:24:35 INFO juju runner.go:245 worker: restarting "api" in 3s
2014-03-28 00:24:37 INFO juju machine.go:109 machine agent machine-4 start
2014-03-28 00:24:37 DEBUG juju.agent agent.go:237 Reading agent config, format: format 1.16
2014-03-28 00:24:37 INFO juju runner.go:253 worker: start "api"
2014-03-28 00:24:37 INFO juju apiclient.go:111 state/api: dialing "wss://bootstrapnode.internal:17070/"
2014-03-28 00:24:37 INFO juju apiclient.go:121 state/api: connection established

(The retry should probably also have a backoff to every few minutes.)

Curtis Hovey (sinzui) on 2014-03-28
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: addressability
Changed in juju-core:
importance: High → Medium
tags: added: network
Anastasia (anastasia-macmood) wrote :

Re-targeting to be addressed in Juju 2.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.1.0
Changed in juju-core:
status: Triaged → Won't Fix
Curtis Hovey (sinzui) on 2017-02-17
Changed in juju:
milestone: 2.1-rc2 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers