Unable to change listening IP configured for juju controller 3.4

Bug #2063088 reported by David Negreira
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Joseph Phillips

Bug Description

I found this issue on a juju controller running on LXD.
When I rebooted my machine, the Juju controller started with a different IP, and I was unable to use it or configure it with the new IP.
I tried to fix it by modifying the IP addresses configured on /var/lib/juju/agents/machine-0/agent.conf and /var/lib/juju/agents/unit-controller-0/agent.conf which seems to work fine.

The issue seems to be with the dqlite part of Juju,
When I start jujud-machine-0.service, which I always start after snap.juju-db.daemon.service, the 'Address' parameter on /var/lib/juju/dqlite/cluster.yaml is reset to the old value, and juju service continues trying to connect to the old IP address.

This is the error message which shows that it is trying to connect to the old IP:

2024-04-22 08:22:16 WARNING juju.worker.dbaccessor connector.go:77 attempt 1117: server 10.99.27.51:17666: dial: dial tcp 10.99.27.51:17666: connect: connection refused

Changed in juju:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Joseph Phillips (manadart)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.