github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 22:55:14 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #2987] (Un-)Healthy Threshold is not being saved #11053

New Issue
Closed
opened 2026-05-06 15:44:27 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-06 15:44:27 -05:00
Owner
Copy Link

Originally created by @mdn-united on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2987

Originally assigned to: @oschwartz10612 on GitHub.

Describe the Bug

I’m having an issue where the thresholds aren’t being saved in the health checks. For example, I set the ‘Unhealthy Threshold’ to 2 and then click “Done”. Under the Targets, I also click ‘Save Target’. When I then look at the Health Checks configuration again, the ‘Unhealthy Threshold’ is back to 1. The same thing happens with the ‘Healthy Threshold’. The interval can be changed and the value is saved.
I have already updated all the components to the latest versions.

Environment

  • OS Type & Version: Debian GNU/Linux 12 (bookworm)
  • Pangolin Version: v1.18.2 EE
  • Gerbil Version: 1.4.0
  • Traefik Version: 3.6.15
  • Newt Version: 1.12.3

To Reproduce

Edit a resource. Under the target, click the ‘Health Check’ button. In the settings, enable the Health Check and then click ‘Advanced’. Change the value of ‘Healthy Threshold’ or ‘Unhealthy Threshold’ to a value other than 1. Save by clicking “Done” and then click ‘Save Targets’. Then open the Health Check again and go to ‘Advanced’. It will show a 1 again.

Image

Expected Behavior

I would expect the number entered to be saved.

Originally created by @mdn-united on GitHub (May 4, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2987 Originally assigned to: @oschwartz10612 on GitHub. ### Describe the Bug I’m having an issue where the thresholds aren’t being saved in the health checks. For example, I set the ‘Unhealthy Threshold’ to 2 and then click “Done”. Under the Targets, I also click ‘Save Target’. When I then look at the Health Checks configuration again, the ‘Unhealthy Threshold’ is back to 1. The same thing happens with the ‘Healthy Threshold’. The interval can be changed and the value is saved. I have already updated all the components to the latest versions. ### Environment - OS Type & Version: Debian GNU/Linux 12 (bookworm) - Pangolin Version: v1.18.2 EE - Gerbil Version: 1.4.0 - Traefik Version: 3.6.15 - Newt Version: 1.12.3 ### To Reproduce Edit a resource. Under the target, click the ‘Health Check’ button. In the settings, enable the Health Check and then click ‘Advanced’. Change the value of ‘Healthy Threshold’ or ‘Unhealthy Threshold’ to a value other than 1. Save by clicking “Done” and then click ‘Save Targets’. Then open the Health Check again and go to ‘Advanced’. It will show a 1 again. <img width="784" height="664" alt="Image" src="https://github.com/user-attachments/assets/751eb90f-2ae5-4e10-bd35-653e59f905b5" /> ### Expected Behavior I would expect the number entered to be saved.
GiteaMirror added the bug label 2026-05-06 15:44:27 -05:00
GiteaMirror commented 2026-05-06 15:44:29 -05:00
Author
Owner
Copy Link

@AstralDestiny commented on GitHub (May 4, 2026):

CE or EE?

<!-- gh-comment-id:4369093342 --> @AstralDestiny commented on GitHub (May 4, 2026): CE or EE?
GiteaMirror commented 2026-05-06 15:44:29 -05:00
Author
Owner
Copy Link

@gnullme commented on GitHub (May 4, 2026):

Same happening to me. I am using EE. It seems to only affect resource healthchecks.

<!-- gh-comment-id:4369717494 --> @gnullme commented on GitHub (May 4, 2026): Same happening to me. I am using EE. It seems to only affect resource healthchecks.
GiteaMirror commented 2026-05-06 15:44:29 -05:00
Author
Owner
Copy Link

@AstralDestiny commented on GitHub (May 4, 2026):

Can confirm will notify.

<!-- gh-comment-id:4369815739 --> @AstralDestiny commented on GitHub (May 4, 2026): Can confirm will notify.
GiteaMirror commented 2026-05-06 15:44:29 -05:00
Author
Owner
Copy Link

@mdn-united commented on GitHub (May 4, 2026):

EE in my case.

<!-- gh-comment-id:4370067130 --> @mdn-united commented on GitHub (May 4, 2026): EE in my case.
GiteaMirror commented 2026-05-06 15:44:30 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (May 4, 2026):

Also effects the follow redirects 🤦 . Will get fixed in the 1.18.3 release early this week.

<!-- gh-comment-id:4373189015 --> @oschwartz10612 commented on GitHub (May 4, 2026): Also effects the follow redirects 🤦 . Will get fixed in the 1.18.3 release early this week.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#11053
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?