Container wont start after Creation, Failed pre-start check for device "eth0": Network "incusbr0"

Tony_Anytime · February 8, 2024, 1:31pm

Any ideas?

incus launch images:ubuntu/23.04 LLAMA --target RRAI
Launching LLAMA
Error: Failed instance creation: Failed pre-start check for device “eth0”: Network “incusbr0” unavailable on this server
incus launch images:ubuntu/23.04 LLAMA2 --target RRAI
Launching LLAMA2
Error: Failed instance creation: Failed pre-start check for device “eth0”: Network “incusbr0” unavailable on this server

simos · February 8, 2024, 1:53pm

You would need to check with the following command that the RRAI node has the incusbr0 network device.

incus network list RRAI:

If you migrated from LXD (I think, while an instance was running?), then the network device was kept with the old name, lxdbr0.

If indeed, then you rename to incusbr0. Requires to stop the affected containers while renaming.

Tony_Anytime · February 8, 2024, 2:07pm

It is a new install on this whole cluster, never had lxd
incus network list
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| 10.0.0.0 | bridge | YES | 10.119.230.1/24 | fd42:266e:d72f:8869::1/64 | | 0 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| eno2 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| incusbr0 | bridge | YES | 10.126.149.1/24 | fd42:ecf:4f02:b679::1/64 | | 21 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+

simos · February 8, 2024, 2:33pm

I can see a network called 10.0.0.0. Is that right? It looks like it was created by mistake.
It is not used by any instance. If you do not need it, remove it.

Do clusters share the output of incus network list? I think they do not. In that case, provide the output of all nodes in the cluster.

Finally,
use the fenced code blocks to surround the output of commands.

Tony_Anytime · February 8, 2024, 2:40pm

@ list
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | LOCATION |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| 10TBBACK | RUNNING | 10.126.149.44 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe02:9ecc (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| AD-Controller1 | RUNNING | 10.126.149.106 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe0c:29a4 (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| AD-TEST | RUNNING | 10.126.149.13 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe15:c4a2 (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| ELK-1 | RUNNING | 10.126.149.254 (eth0) | fd42:ecf:4f02:b679:216:3eff:fecd:7e3d (eth0) | CONTAINER | 0 | RRSOC |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| FLECTRA | RUNNING | 10.126.149.213 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe79:b98f (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| KALI1 | RUNNING | 10.126.149.216 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe6e:306e (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| LLAMA | STOPPED | | | CONTAINER | 0 | RRAI |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| LLAMA2 | STOPPED | | | CONTAINER | 0 | RRAI |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| MARIADB-3 | RUNNING | 10.126.149.181 (eth0) | fd42:ecf:4f02:b679:216:3eff:fec3:dd9c (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| ODOO | RUNNING | 10.126.149.139 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe23:9f49 (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| PYMAIL | RUNNING | 10.126.149.159 (eth0) | fd42:ecf:4f02:b679:216:3eff:feb3:39e9 (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| ROD-AX | RUNNING | 10.126.149.66 (eth0) | fd42:ecf:4f02:b679:216:3eff:feaf:d2af (eth0) | CONTAINER | 0 | Q5 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| RR-MARIABK | RUNNING | 10.126.149.160 (eth0) | fd42:ecf:4f02:b679:216:3eff:feae:5e3e (eth0) | CONTAINER | 0 | RRSOC |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| RRDB3 | RUNNING | 10.126.149.183 (eth0) | fd42:ecf:4f02:b679:216:3eff:fe22:764c (eth0) | CONTAINER | 0 | RRDB2 |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
| RRTEAMS-TEST1 | RUNNING | 10.126.149.151 (eth0) | fd42:ecf:4f02:b679:216:3eff:feec:5216 (eth0) | CONTAINER | 0 | RRTEAMS |
±---------------±--------±----------------------±---------------------------------------------±----------------±----------±---------+
root@RRDB2:/home/rr2020# @ network list
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| 10.0.0.0 | bridge | YES | 10.119.230.1/24 | fd42:266e:d72f:8869::1/64 | | 0 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f0 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f1 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| incusbr0 | bridge | YES | 10.126.149.1/24 | fd42:ecf:4f02:b679::1/64 | | 21 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+

It is not being used, how do I take it out?
NOt sure what you want me to fence code blocks and why?

For some reason all the servers have 10.0.0.0 bridged

simos · February 8, 2024, 2:55pm

Regarding the fenced code blocks:
It’s easier to understand what is being shown and it is visually more appealing.

WITH:

root@RRDB2:/home/rr2020# @ network list
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| 10.0.0.0 | bridge | YES | 10.119.230.1/24 | fd42:266e:d72f:8869::1/64 | | 0 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f0 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f1 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| incusbr0 | bridge | YES | 10.126.149.1/24 | fd42:ecf:4f02:b679::1/64 | | 21 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+

WITHOUT:

root@RRDB2:/home/rr2020# @ network list
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| 10.0.0.0 | bridge | YES | 10.119.230.1/24 | fd42:266e:d72f:8869::1/64 | | 0 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f0 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| enp1s0f1 | physical | NO | | | | 0 | |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+
| incusbr0 | bridge | YES | 10.126.149.1/24 | fd42:ecf:4f02:b679::1/64 | | 21 | CREATED |
±---------±---------±--------±----------------±--------------------------±------------±--------±--------+