Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] TrueNAS disconnected due to single field not returned #191

Open
nanzer opened this issue Dec 12, 2024 · 4 comments · May be fixed by #198
Open

[Bug] TrueNAS disconnected due to single field not returned #191

nanzer opened this issue Dec 12, 2024 · 4 comments · May be fixed by #198
Labels
bug Something isn't working

Comments

@nanzer
Copy link

nanzer commented Dec 12, 2024

Describe the issue

Integration claims that it can't connect to the TrueNAS instance, but debug logs show this is false. The update/check_available query fails and causes the whole integration to break.

How to reproduce the issue

  1. Install latest version of TrueNAS, HomeAssistant in docker, and the integration
  2. Try to initialize the integration.
  3. Inspect logs with debug mode turned on.
  4. See many fields populate including drives, processor information, etc, but fail at update/check_available causing the whole integration to die

Expected behavior

The integration should not report a connection failure when there isn't one

Screenshots

image

Software versions

  • Home Assistant version: HA 2024.12.2 in docker
  • TrueNAS integration version: v1.3.1
  • TrueNAS version: TrueNAS-13.0-U6.3

Traceback/Error logs

2024-12-11 22:16:30.441 DEBUG (SyncWorker_3) [custom_components.truenas.api] TrueNAS truenas.lan query: jail, get, {}
2024-12-11 22:16:30.486 DEBUG (SyncWorker_3) [custom_components.truenas.api] TrueNAS truenas.lan query response: []
2024-12-11 22:16:30.487 DEBUG (SyncWorker_1) [custom_components.truenas.api] TrueNAS truenas.lan query: vm, get, {}
2024-12-11 22:16:30.520 DEBUG (SyncWorker_1) [custom_components.truenas.api] TrueNAS truenas.lan query response: []
2024-12-11 22:16:30.521 DEBUG (SyncWorker_4) [custom_components.truenas.api] TrueNAS truenas.lan query: cloudsync, get, {}
2024-12-11 22:16:30.571 DEBUG (SyncWorker_4) [custom_components.truenas.api] TrueNAS truenas.lan query response: []
2024-12-11 22:16:30.572 DEBUG (SyncWorker_2) [custom_components.truenas.api] TrueNAS truenas.lan query: replication, get, {}
2024-12-11 22:16:30.607 DEBUG (SyncWorker_2) [custom_components.truenas.api] TrueNAS truenas.lan query response: []
2024-12-11 22:16:30.607 DEBUG (SyncWorker_0) [custom_components.truenas.api] TrueNAS truenas.lan query: pool/snapshottask, get, {}
2024-12-11 22:16:30.641 DEBUG (SyncWorker_0) [custom_components.truenas.api] TrueNAS truenas.lan query response: []
2024-12-11 22:16:30.642 DEBUG (SyncWorker_1) [custom_components.truenas.api] TrueNAS truenas.lan query: update/check_available, post, {}
2024-12-11 22:16:40.659 WARNING (SyncWorker_1) [custom_components.truenas.api] TrueNAS truenas.lan unable to fetch data "update/check_available" (no_response)
2024-12-11 22:16:40.660 DEBUG (MainThread) [custom_components.truenas.coordinator] Finished fetching truenasvm data in 12.448 seconds (success: False)

Additional context

I did a round of updates on my VMs and containers and noticed that my TrueNAS integration stopped working shortly after. I'm not sure which one of the updates caused it, but I've tried rolling back the TrueNAS integration to 1.3b2 to no avail. I have also repeatedly deleted and recreated my TrueNAS entity in homeassistant, tried referring to it using hostname and IP, enabled and disabled SSL, rerolled API keys, etc.

Not sure whether the updates caused the breakage or not, I only noticed afterward because I was checking my dashboards

@nanzer nanzer added the bug Something isn't working label Dec 12, 2024
@logandirks
Copy link

Same boat,

Logger: custom_components.truenas.api
Source: custom_components/truenas/api.py:117
integration: TrueNAS (documentation, issues)
First occurred: December 13, 2024 at 3:07:38 PM (2038 occurrences)
Last logged: 1:45:27 PM

TrueNAS XXX.XXX.XXX.XXX unable to fetch data "chart/release" (404)

@nanzer
Copy link
Author

nanzer commented Dec 17, 2024

I think we have different issues - I don't get a 404. When I set up a new instance, its able to grab a full list of disks, specs, etc, but fails on an error 500:

TrueNAS truenas.lan unable to fetch data "reporting/get_data" (500)
TrueNAS truenas.lan unable to fetch data "update/check_available" (no_response)

@sandstheman
Copy link

Same here having migratde to latest TrueNAS scale release from TrueNAS Core:

Logger: custom_components.truenas.api
Source: custom_components/truenas/api.py:117
integration: TrueNAS ([documentation](https://github.com/tomaae/homeassistant-truenas), [issues](https://github.com/tomaae/homeassistant-truenas/issues))
First occurred: 00:39:26 (47 occurrences)
Last logged: 01:26:09

TrueNAS 192.168.2.25 unable to fetch data "chart/release" (404)
TrueNAS 192.168.2.25 unable to fetch data "pool" (no_response)
TrueNAS vault.london.jassal.co unable to fetch data "pool" (no_response)
TrueNAS vault.london.jassal.co unable to fetch data "chart/release" (404)

@jacobohpea
Copy link

Same but on an old version of trunas that fails to return disk tempature

2024-12-30 09:44:16.086 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS unable to fetch data "disk/temperatures" (no_response)

Then the entire integration fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants