mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-07 13:19:07 -05:00
[GH-ISSUE #2938] Health Check still not shown on v1.18.1 #11036
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#11036
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @carloslockward on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2938
Describe the Bug
Healthcheck status still fails after updating to 1.18.1 and restarting Newt.
Environment
To Reproduce
Expected Behavior
Health Status shows "Healthy"
Other
@oschwartz10612 commented on GitHub (Apr 30, 2026):
I think this is because you migrated to 1.18.0 and not to 1.18.1 so the resource health checks were inserted incorrectly at that time. Restarting the newt might not be working because the health check status is not changing.
What you could do is upgrade again from 1.17 to 1.18.1 or unfortunately you might need to disable then re enable each health check. I think that will cause it to update the resource.
@kaat3g commented on GitHub (Apr 30, 2026):
I am also facing the same issue. I upgraded from 1.17.1 to 1.18.0 (health check not showing) and then to 1.18.1 (still not showing). The newt sites themselves are online showing uptime correctly.
As suggested by @oschwartz10612, I have tried disabling/re-enabling the resource and also disabling/re-enabling the health check for the resource without success. Additionally, I deleted/re-added the resource target without success.
@oschwartz10612 Is there something we can do in the db to correct the issue?
@carloslockward commented on GitHub (Apr 30, 2026):
I also tried to disable the health check, saving the target, re-enabling it and saving again. Still nothing :(
@kaat3g commented on GitHub (May 1, 2026):
Following up on this situation... I downgraded from 1.18.1 back to 1.17.1 and restored the db to the 1.17.1 config (from backup). I then upgraded directly from 1.17.1 to 1.18.1. All's working as expected now. Health checks on resources are showing as healthy.
If you have the backup and are able to downgrade and upgrade directly to 1.18.1, give that a shot.
Edit:
Adding logs...
@NecktiedHummingbird commented on GitHub (May 1, 2026):
Can confirm, restoring a backup to 1.17 and then upgrading directly to 1.18.1 fixes the healthchecks.
But probably not everyone has a backup (which is bad anyways, but another topic).
The logs are kinda irritating, cause the migrations tells me it applied the 1.18.0 migration, which is technically a 1.18.1 migration in my eyes.
Before the upgrade i tried recreating the ressources, creating new resources, change the healthcheck config etc. - nothing did work.
But, as already said, the upgradepath from 1.17.* to 1.18.1 fixed it:
@kaat3g commented on GitHub (May 1, 2026):
FYI. Pangolin creates backups of the db prior to upgrades. So, check directory at
config/db/backupsto pull the last db backup if you plan to restore.@NecktiedHummingbird commented on GitHub (May 1, 2026):
Yeah, i saw that the moment i restored a full backup and checking the logs 😂