Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Rebooted and Instances has is erroring

Description

Rebooted my host and got the following in the UI.

X Error

On the back end logs, I see:
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 515, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 560, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 218, in setup
await self._setup_impl()
File "/usr/lib/python3/dist-packages/middlewared/plugins/virt/global.py", line 390, in _setup_impl
raise CallError(result.get('error'))
middlewared.service_exception.CallError: [EFAULT] The following instances failed to update (profile change still saved):

  • Project: default, Instance: apps1: Failed to create instance update operation: Instance is busy running a "stop" operation

  • Project: default, Instance: apps2: Failed to create instance update operation: Instance is busy running a "stop" operation
    ```

Session ID: 925a5c5f-1fc6-dd5c-b499-0499ab7e2526

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk 3 days ago

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 3 days ago

The errors are occurring because the instances have been edited by hand. There isn’t much we can do here. Closing the ticket.

Michelle Johnson 3 days ago

Thank you for your report, !

This issue ticket is in the queue for review. An Engineering representative will update with further details or questions in the near future.

dasunsrule32 4 days ago
Edited

Hey Andrew, I should’ve submitted this report as the UI is erroring out based on instances not starting. That really is the bug here and not the instances starting. Yes, the instances are manually created because the UI doesn’t have a way to do nvidia currently and both of those are fixed now (You can follow along starting at the post I put there, that would be a feature request to support nvidia as a first class citizen for Incus in TNCE).

I would say the two main issues here are:

  1. UI Error because of intances that can’t start.

  2. Not being able to diagnose issues easily with instances because --show-log wasn’t working at all.

Does that make more sense?

Andrew Walker 4 days ago

At least some errors in middleware log are clearly caused by shell editing.

If you have been editing incus config from shell, reproduce the issue on a pristine setup without any unsupported tinkering.

Not Applicable
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created 4 days ago
Updated 3 days ago
Resolved 3 days ago
Configure