OpenNebula

There appear to be conditions which the onedb fsck cannot reconcile.

One example scenario (but not limited to this) is where a VM was deployed, but the vnet it was referencing has since been deleted.
When running onedb fsck, this inconsistency is detected, however the expectation is that onedb automatically resolves these items.
If scenarios exist where it cannot repair the error, these items should be highlighted in the output to indicate that the administrator will need to investigate/repair that scenario manually.

$ onedb fsck -u user -d opennebula
...
VM 21059 is using VNet 761, but it does not exist 
...

Possible suggestion at end of fsck output, list items not automatically repaired.

...
======================================
Total errors found: 10
======================================
Total errors repaired: 9
======================================
Total errors not repaired: 1
Investigate and reconcile as required:

VM 21059 is using VNet 761, but it does not exist