Whenever I create a VM instance in the new Instances section, I get a validation error. The created Instance does not show up after that in the list of instances (which is empty), but every time I get a popup saying that there is a ValidationError.
This is a bug in TrueNAS, due to some internal inconsistent state.
I downloaded the db file with all the configurations settings, and I see that it’s an sqlite database file.
I opened the file inside the sqlite DB editor, and I see a bunch of tables.
How can I edit the db file to reset the Instances configuration?
I am not sure anyone here will be able to answer that as manually editing the db isn’t exactly a supported use case.
Even if you can figure it out yourself, have you considered and compared it to the amount of time it would take to redo your configuration from scratch?
Clearing it out would require some preparation if you have encrypted pools and possibly some ix-virt dataset cleanup. So don’t go and press the reset button willy-nilly.
Even if you can figure it out yourself, have you considered and compared it to the amount of time it would take to redo your configuration from scratch?
Thanks for the answer!
Unfortunately, I have multiple apps set up (most of them as custom Docker containers) and it would require time to reinstall TrueNAS and do all of it again. But also, since this error happens unexpectedly, and as far as I can tell is a bug (because any validation errors should have been reported at the point when I clicked on the Create button of the new VM), I cannot do this every time it happens in the future.
If editing the DB is not the way to go, I would hope that there is some way to reset the Instances configuration alone from within the UI? Or by ssh-ing into the TrueNAS machine?
If you believe it to be a bug, Report A Bug in the TrueNAS GUI, looks like a smile on upper right of TrueNAS Scale or on the upper right of the forum page. Report A Bug
