github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-15 21:31:24 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #3115] Health Check Degraded if Resource additional address' health isn't enabled #23612

New Issue
Closed
opened 2026-06-05 06:36:31 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-05 06:36:31 -05:00
Owner
Copy Link

Originally created by @deskstorm on GitHub (May 20, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3115

Describe the Bug

I have an issue where a resource's address with disabled health checks are included with enabled health checks to mark resource as degraded.

There's a resource which I have, where Address #1 at port 443 (Enabled & Health http = on) and Addr#2 to port 80 (Disabled & health = off). As port 80 is only a backup if the port 443 fudges up, i can turn on port 80 and use that.

Testing shows that health checks will consider all addresses, even is disabled or enabled, and if even health check is turned off on additional address to the primary one with health check on.
Examples:

  • Resource Degraded = Addr#1 enabled & health enabled (shows healthy); Addr#2 disabled & health disabled
  • Resource Degraded = Addr#1 enabled & health enabled (shows healthy); Addr#2 enabled & health disabled
  • Resource Healthy = Addr#1 enabled & health enabled (shows healthy); Addr#2 disabled & health enabled (shows healthy)
  • Resource Healthy = Addr#1 enabled & health enabled (shows healthy); Addr#2 enabled & health enabled (shows healthy)

I understand some people may disable an address and want it to show degraded. But seems health check would need to be enabled to count here.
So if the health check isnt enabled it shouldn't count to the overall health check of the resource?

Environment

  • OS Type & Version: Debian
  • Pangolin Version: 1.18.4
  • Gerbil Version: 1.4.0
  • Traefik Version: 3.6.17
  • Newt Version: 1.12.5

To Reproduce

  1. Create Resource
  2. add 2x addresses
  3. enable health check on one address and leave other health check disabled
  4. resource health check should show degraded

Expected Behavior

Health check should check addresses with enabled health checks, ignoring address enabled status. and use those reports to summarise the resource health

Originally created by @deskstorm on GitHub (May 20, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/3115 ### Describe the Bug I have an issue where a resource's address with disabled health checks are included with enabled health checks to mark resource as degraded. There's a resource which I have, where Address #1 at port 443 (Enabled & Health http = on) and Addr#2 to port 80 (Disabled & health = off). As port 80 is only a backup if the port 443 fudges up, i can turn on port 80 and use that. Testing shows that health checks will consider all addresses, even is disabled or enabled, and if even health check is turned off on additional address to the primary one with health check on. Examples: - Resource Degraded = Addr#1 enabled & health enabled (shows healthy); Addr#2 disabled & health disabled - Resource Degraded = Addr#1 enabled & health enabled (shows healthy); Addr#2 enabled & health disabled - Resource Healthy = Addr#1 enabled & health enabled (shows healthy); Addr#2 disabled & health enabled (shows healthy) - Resource Healthy = Addr#1 enabled & health enabled (shows healthy); Addr#2 enabled & health enabled (shows healthy) I understand some people may disable an address and want it to show degraded. But seems health check would need to be enabled to count here. So if the health check isnt enabled it shouldn't count to the overall health check of the resource? ### Environment - OS Type & Version: Debian - Pangolin Version: 1.18.4 - Gerbil Version: 1.4.0 - Traefik Version: 3.6.17 - Newt Version: 1.12.5 ### To Reproduce 1. Create Resource 2. add 2x addresses 3. enable health check on one address and leave other health check disabled 4. resource health check should show **degraded** ### Expected Behavior Health check should check addresses with enabled health checks, ignoring address enabled status. and use those reports to summarise the resource health
GiteaMirror commented 2026-06-05 06:36:33 -05:00
Author
Owner
Copy Link

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

I think this was fixed by https://github.com/fosrl/pangolin/pull/3118. Update should be out in the next release.

<!-- gh-comment-id:4503442431 --> @oschwartz10612 commented on GitHub (May 20, 2026): I think this was fixed by https://github.com/fosrl/pangolin/pull/3118. Update should be out in the next release.
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
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#23612
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?