Removing a lxd remote leaves services on the lxd worker
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
New
|
Undecided
|
Unassigned |
Bug Description
I recently removed the lxd remote unit with IP address 10.44.124.140 and replaced it with 10.44.124.197. After executing `mojo run` I noticed that the lxd worker still had stray services on it.
ubuntu@
/<email address hidden>:
total 4.0K
-rw-r--r-- 1 root root 132 May 11 16:34 autopkgtest-
/<email address hidden>:
total 4.0K
-rw-r--r-- 1 root root 132 May 11 16:34 autopkgtest-
While a working lxd remote has the following services on the lxd worker:
ubuntu@
lrwxrwxrwx 1 root root 83 Jun 10 19:14 /<email address hidden> -> /var/lib/
opkgtest-
lrwxrwxrwx 1 root root 83 Jun 10 19:14 /<email address hidden> -> /var/lib/
opkgtest-
lrwxrwxrwx 1 root root 83 Jun 10 19:14 /<email address hidden> -> /var/lib/
opkgtest-
/<email address hidden>:
total 4.0K
-rw-r--r-- 1 root root 132 Jun 10 19:14 autopkgtest-
/<email address hidden>:
total 4.0K
-rw-r--r-- 1 root root 132 Jun 10 19:14 autopkgtest-
/<email address hidden>:
total 4.0K
-rw-r--r-- 1 root root 132 Jun 10 19:14 autopkgtest-
Clearly something is trying to clean up the services but ends up missing a couple. This then results in errors in the `cloud-
May 22 13:52:19 juju-4d1272-
May 22 13:52:19 juju-4d1272-
tags: | added: adt-32 |
Also if we are regularly replacing lxd remote systems then we could run into a situation where we are re-using an IP address which could then cause issues when new service files are being created.