Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(appset): avoid panic when no steps in rollingSync #20357

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

CefBoud
Copy link
Contributor

@CefBoud CefBoud commented Oct 14, 2024

Closes #18817.

Description

When using Applicationset's rolling sync, having no steps in the manifest results in a panic. This PR attempts to fix that by ensuring a positive number of steps.

Additionally, applications not selected by MatchExpressions are still treated as part of Step 1 (actually Step 0 due to 1-based indexing) because the appStepMap defaults to 0 and there is no validation for the presence in the map.

These applications are not synced by the rolling sync. I suggest assigning them a value of -1 to clearly indicate that they are excluded from the sync and must be manually synced.
Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@CefBoud CefBoud requested review from a team as code owners October 14, 2024 00:38
Copy link

bunnyshell bot commented Oct 14, 2024

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@CefBoud CefBoud force-pushed the fix/appset-rolling-sync-step branch from 7027c9f to e02882c Compare October 14, 2024 00:39
Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (master@ea46572). Learn more about missing BASE report.
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##             master   #20357   +/-   ##
=========================================
  Coverage          ?   55.08%           
=========================================
  Files             ?      322           
  Lines             ?    54932           
  Branches          ?        0           
=========================================
  Hits              ?    30260           
  Misses            ?    22067           
  Partials          ?     2605           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@todaywasawesome todaywasawesome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -1018,6 +1018,16 @@ func statusStrings(app argov1alpha1.Application) (string, string, string) {
return healthStatusString, syncStatusString, operationPhaseString
}

func getAppStep(appName string, appStepMap map[string]int) string {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think for further reusability of this function, it would make more sense to return an int instead of a string here.

@CefBoud CefBoud force-pushed the fix/appset-rolling-sync-step branch from e02882c to 31e75b1 Compare October 22, 2024 22:12
Signed-off-by: cef <moncef.abboud95@gmail.com>
@CefBoud CefBoud force-pushed the fix/appset-rolling-sync-step branch from 31e75b1 to 2b40a79 Compare October 22, 2024 22:14
@CefBoud CefBoud requested a review from jannfis October 22, 2024 22:16
Copy link
Member

@jannfis jannfis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks a lot for fixing this.

@jannfis jannfis merged commit e953a2d into argoproj:master Oct 23, 2024
27 checks passed
@jannfis
Copy link
Member

jannfis commented Oct 23, 2024

/cherry-pick release-2.13

gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Oct 23, 2024
Signed-off-by: cef <moncef.abboud95@gmail.com>
jannfis pushed a commit that referenced this pull request Oct 24, 2024
Signed-off-by: cef <moncef.abboud95@gmail.com>
Co-authored-by: ABBOUD Moncef <moncef.abboud95@gmail.com>
adriananeci pushed a commit to adriananeci/argo-cd that referenced this pull request Dec 4, 2024
Signed-off-by: cef <moncef.abboud95@gmail.com>
Signed-off-by: Adrian Aneci <aneci@adobe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

applicationset controller crashes when rollingSync steps missing
4 participants