Global probe is recreated on oneuptime-probe-one pod restart, breaking existing monitors #91

Closed
opened 2026-04-05 16:18:51 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @matiaschileno on 2/12/2026

Describe the bug
When deploying OneUptime using the Helm chart, the global probe created by oneuptime-probe-one is recreated every time the pod is restarted or redeployed.
Although the probe keeps the same name, it is treated as a new probe, causing existing monitors to lose their probe connection.


To Reproduce
Steps to reproduce the behavior:

  1. Deploy OneUptime using the Helm chart with a global probe
  2. Create monitors using this probe
  3. Restart or redeploy the oneuptime-probe-one pod (Helm upgrade / pod restart)
  4. Observe that a new global probe is created and monitors lose connection

Expected behavior
The global probe should persist across pod restarts and redeployments, and existing monitors should continue to work without requiring manual updates.


Screenshots

Image Image Image

Desktop (please complete the following information):

  • OS: Linux
  • Browser: Chrome
  • Version: Latest

Smartphone (please complete the following information):

  • Device: N/A
  • OS: N/A
  • Browser: N/A
  • Version: N/A

Deployment Type
Self-hosted (Helm chart)


Additional context

  • OneUptime version: 9.3.19
  • Helm chart version: 9.5.0

Each redeployment creates a new global probe with the same name.
Monitors must be manually updated to use the new probe, and old probes must be manually removed from Admin Settings → Global Probes.

*Originally created by @matiaschileno on 2/12/2026* **Describe the bug** When deploying OneUptime using the Helm chart, the global probe created by `oneuptime-probe-one` is recreated every time the pod is restarted or redeployed. Although the probe keeps the same name, it is treated as a new probe, causing existing monitors to lose their probe connection. --- **To Reproduce** Steps to reproduce the behavior: 1. Deploy OneUptime using the Helm chart with a global probe 2. Create monitors using this probe 3. Restart or redeploy the `oneuptime-probe-one` pod (Helm upgrade / pod restart) 4. Observe that a new global probe is created and monitors lose connection --- **Expected behavior** The global probe should persist across pod restarts and redeployments, and existing monitors should continue to work without requiring manual updates. --- **Screenshots** <img width="1026" height="455" alt="Image" src="https://github.com/user-attachments/assets/ad41a316-16c2-49d4-92d4-968c4cd3456f" /> <img width="959" height="513" alt="Image" src="https://github.com/user-attachments/assets/480170f6-75fa-45b5-a1e5-21c70c89aa40" /> <img width="717" height="456" alt="Image" src="https://github.com/user-attachments/assets/9af47d84-89e3-4ae5-805e-49f3d2929535" /> --- **Desktop (please complete the following information):** - OS: Linux - Browser: Chrome - Version: Latest --- **Smartphone (please complete the following information):** - Device: N/A - OS: N/A - Browser: N/A - Version: N/A --- **Deployment Type** Self-hosted (Helm chart) --- **Additional context** - OneUptime version: **9.3.19** - Helm chart version: **9.5.0** Each redeployment creates a new global probe with the same name. Monitors must be manually updated to use the new probe, and old probes must be manually removed from **Admin Settings → Global Probes**.
MrUnknownDE added the bugbugbugbugbugbugbugbugbugbugbugbugbugbug labels 2026-04-05 16:18:51 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#91