ResourceSyncPendingUpdate never goes away for multiple stacks that use the same compose configuration #292

New Issue

GiteaMirror · 2025-10-31T15:07:45-05:00

GiteaMirror commented

2025-10-31 15:07:45 -05:00

Originally created by @aksvenk on GitHub (Apr 17, 2025).

Komodo version: 1.7.0

I have a resource sync to a git repo in a single flat file.
Resource sync completes successfully but the changes to similarly deployed stacks are always show as pending ResourceSyncPendingUpdate

Here is an example of 2 problematic stacks.

[[stack]]
name = "dozzle-agent-tuna"
[stack.config]
server = "tuna"
run_directory = "dozzle"
file_paths = ["compose.agent.yaml"]
git_provider = "git.homelab.net"
git_account = "bot"
repo = "homelab/stacks"
webhook_enabled = false

[[stack]]
name = "dozzle-agent-nas"
[stack.config]
server = "nas"
run_directory = "dozzle"
file_paths = ["compose.agent.yaml"]
git_provider = "git.homelab.net"
git_account = "bot"
repo = "homelab/stacks"
webhook_enabled = false

Originally created by @aksvenk on GitHub (Apr 17, 2025). **Komodo version:** 1.7.0 I have a resource sync to a git repo in a single flat file. Resource sync completes successfully but the changes to similarly deployed stacks are always show as pending `ResourceSyncPendingUpdate` Here is an example of 2 problematic stacks. ```toml [[stack]] name = "dozzle-agent-tuna" [stack.config] server = "tuna" run_directory = "dozzle" file_paths = ["compose.agent.yaml"] git_provider = "git.homelab.net" git_account = "bot" repo = "homelab/stacks" webhook_enabled = false ``` ```toml [[stack]] name = "dozzle-agent-nas" [stack.config] server = "nas" run_directory = "dozzle" file_paths = ["compose.agent.yaml"] git_provider = "git.homelab.net" git_account = "bot" repo = "homelab/stacks" webhook_enabled = false ```

GiteaMirror added the seen 👀 label 2025-10-31 15:07:45 -05:00

GiteaMirror commented

2025-10-31 15:07:47 -05:00

@mheidinger commented on GitHub (Aug 16, 2025):

Got the same issue for 3 out of 15 of my stacks. What they seem to have in common is that they have poll_for_updates = true set, all other stack don't have that set. I am aware that this is not the case for the original issue, but might be a hint?

This is an example of such a problematic stack:

[[stack]]
name = "registry"
[stack.config]
server = "myserver"
poll_for_updates = true
auto_update = true
linked_repo = "myrepo"
webhook_enabled = false
run_directory = "registry"
file_paths = ["docker-compose.yml"]

@mheidinger commented on GitHub (Aug 16, 2025): Got the same issue for 3 out of 15 of my stacks. What they seem to have in common is that they have `poll_for_updates = true` set, all other stack don't have that set. I am aware that this is not the case for the original issue, but might be a hint? This is an example of such a problematic stack: ``` [[stack]] name = "registry" [stack.config] server = "myserver" poll_for_updates = true auto_update = true linked_repo = "myrepo" webhook_enabled = false run_directory = "registry" file_paths = ["docker-compose.yml"] ```

GiteaMirror commented

2025-10-31 15:07:47 -05:00

@mbecker20 commented on GitHub (Aug 28, 2025):

Hm, I cannot reproduce with the same TOMLs, is this still an issue?

@mbecker20 commented on GitHub (Aug 28, 2025): Hm, I cannot reproduce with the same TOMLs, is this still an issue?

GiteaMirror commented

2025-10-31 15:07:47 -05:00

@mheidinger commented on GitHub (Sep 9, 2025):

Unfortunately yes, is there any more information I can give you to help troubleshoot?

@mheidinger commented on GitHub (Sep 9, 2025): Unfortunately yes, is there any more information I can give you to help troubleshoot?

GiteaMirror commented

2025-10-31 15:07:47 -05:00

@la7eralus commented on GitHub (Oct 10, 2025):

I experienced the same issue. There was a diff shown, but no visible changes were displayed. However, I can't confirm that it's limited to stacks with poll_for_updates enabled, since my stack had that option disabled.

What helped in my case was simply running an execute. Right after that, the sync state immediately changed to OK.

I think it might be encoding related or something that the UI can't display in the preview frame.

The .toml in the git repo was generated by komodo, and there have been no manual edits to the file. All was completely managed by komodo.

Side note:
The affected resource did receive an update, but it had no actual effect.

@la7eralus commented on GitHub (Oct 10, 2025): I experienced the same issue. There was a diff shown, but no visible changes were displayed. However, I can't confirm that it's limited to stacks with poll_for_updates enabled, since my stack had that option disabled. What helped in my case was simply running an execute. Right after that, the sync state immediately changed to OK. I think it might be encoding related or something that the UI can't display in the preview frame. The .toml in the git repo was generated by komodo, and there have been no manual edits to the file. All was completely managed by komodo. Side note: The affected resource did receive an update, but it had no actual effect. <img width="2290" height="860" alt="Image" src="https://github.com/user-attachments/assets/9d5e9ffa-d198-474d-aa6d-a043c2edb3de" />

GiteaMirror commented

2025-10-31 15:07:47 -05:00

@mheidinger commented on GitHub (Oct 14, 2025):

Can confirm that the workaround works, thanks!

@mheidinger commented on GitHub (Oct 14, 2025): Can confirm that the workaround works, thanks!

GiteaMirror referenced this issue

2026-04-11 09:58:32 -05:00

[GH-ISSUE #292] Server stats alert still fires even when "Send XX Alerts" is disabled in server config #2080

GiteaMirror referenced this issue

2026-04-13 14:51:37 -05:00

[GH-ISSUE #292] Server stats alert still fires even when "Send XX Alerts" is disabled in server config #3225

GiteaMirror referenced this issue