Incus Instances inaccessible - invalid literal for int re: subnet

Description

Restored two VMs from zvols. Both were being used on this system prior to switching to Fangtooth beta.

I configured a bridge in the networking section (not under the Incus instances page) and connected my VMs to it. Although I’ve been unable to recreate the exact sequence that led to the error, the

which seems to relate to a missing subnet values. I checked the middleware daemon log and noticed the following errors:

From then on I was unable to access instances via the GUI, and querying from the CLI returned the same error.

I tried detaching the br0 adapter from the VM cited in the error and it gave another potential clue as to what the issue might relate to:

I tried it the other way around and detached the Incus bridge from the VM which brought the service back to life after restarting the network via the GUI:

It’s worth noting that I was able to access the VMs directly whilst the error was stopping access to the GUI.

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk March 10, 2025 at 1:03 PM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk March 10, 2025 at 1:03 PM

This should be resolved in RC.1, report back if the problem persists after its out.

Linzi Moore March 6, 2025 at 2:13 PM

Simon,

Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.