You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on 2.10.0 Fleet 0.11.1 some GitRepos have issues deploying the latest changes and fleet gets "stuck" on an old commit. The interface does show a green "Active" next to the Git Repo, but the commit next to it is clearly outdated.
After clicking "Force Update" everything goes through, temporarily showing the message "Contents.fleet.cattle.io "<>" not found
Business impact:
Fleet not deploying latest changes
Troubleshooting steps:
ongoing
Repro steps:
no repro steps yet
Workaround:
Is a workaround available and implemented? yes
What is the workaround: press force update
Actual behavior:
fleet not deploying latest git commits
Expected behavior:
fleet to deploy things once commited
Files, logs, traces:
see JIRA
The text was updated successfully, but these errors were encountered:
SURE-9504
Issue description:
on 2.10.0 Fleet 0.11.1 some GitRepos have issues deploying the latest changes and fleet gets "stuck" on an old commit. The interface does show a green "Active" next to the Git Repo, but the commit next to it is clearly outdated.
After clicking "Force Update" everything goes through, temporarily showing the message "Contents.fleet.cattle.io "<>" not found
Business impact:
Fleet not deploying latest changes
Troubleshooting steps:
ongoing
Repro steps:
no repro steps yet
Workaround:
Is a workaround available and implemented? yes
What is the workaround: press force update
Actual behavior:
fleet not deploying latest git commits
Expected behavior:
fleet to deploy things once commited
Files, logs, traces:
see JIRA
The text was updated successfully, but these errors were encountered: