Interesting, clean machine, no networks … I try creating a network with all default settings and it creates it in PENDING state. (this is a stand-alone machine, NOT clustered)
I create another, same thing. I delete them both, repeat, same thing.
I delete them both, revert to the command line;
# incus network create local
Network local created
# incus network create public
Network public created
# incus network ls
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| br0 | bridge | NO | | | | 9 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| enp4s0 | physical | NO | | | | 0 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| lo | loopback | NO | | | | 0 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| local | bridge | YES | 10.103.31.1/24 | fd42:d81f:c6a4:2606::1/64 | | 0 | CREATED |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| public | bridge | YES | 10.123.112.1/24 | fd42:a9c4:aef1:92d0::1/64 | | 0 | CREATED |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
Works perfectly.
incus version
Client version: 6.14
Server version: 6.14
Newly installed PC running Debian Trixie.
This kinda feels like a fix for the network create on a cluster … gone wrong (?)
Yes yes, I know, I wouldn’t dispute “it works on my machine” for a second. It does however not do that on my machine. Here’s my screenshot of trying to create the network in the UI, note the spinner on “save” that doesn’t go away. This is “click Create Network” , enter “test”, click “Create”.
# incus network ls
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| NAME | TYPE | MANAGED | IPV4 | IPV6 | DESCRIPTION | USED BY | STATE |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| br0 | bridge | NO | | | | 9 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| enp4s0 | physical | NO | | | | 0 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| lo | loopback | NO | | | | 0 | |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| local | bridge | YES | 10.103.31.1/24 | fd42:d81f:c6a4:2606::1/64 | | 2 | CREATED |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| public | bridge | YES | 10.123.112.1/24 | fd42:a9c4:aef1:92d0::1/64 | | 1 | CREATED |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
| test | bridge | YES | 10.60.123.1/24 | fd42:2afd:fb8a:71b::1/64 | | 0 | PENDING |
+--------+----------+---------+-----------------+---------------------------+-------------+---------+---------+
local and public were my previous tests, same results, works fine from the command line. Now this used to work (on other machines, this is a completely clean machine) so I’ve no idea where to start looking for the problem, other than to say it’s literally a completely clean install of everything. Started with a stock Debian Bookworm image, then upgraded to Trixie.
Thing is, on a non-clustered machine, I wouldn’t know “how” to create a “pending” network, well, historically …
Sure, will go back and look how … in the meantime, there’s nothing in the incus log, however I’ve just noticed this in the system log when creating “test2”;
Interesting … to get exactly your output, I switched to Firefox (which I typically don’t use). After setting it up with a TLS certificate with the debug window open etc, I created “test3” - it worked fine (!)
So it would seem to be a “Chromium” browser issue (?)
I had a crack at approximating the API output on Chromium (which still doesn’t work);
The full error is “ERR_NETWORK_CHANGED” … which I’ve seen somewhere else recently, it would seem Chromium spits this out sometimes in place of a meaningful error.
But I’m happy to switch to FF when managing the Incus, however it would seem there is something interesting going on under the hood …
