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

🐛 Set correct labels on helm release during upgrade #1017

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

kevinrizza
Copy link
Member

@kevinrizza kevinrizza commented Jul 8, 2024

Write the correct label set to the helm release. This commit fixes an issue where the upgrades get wedged after the first upgrade when following legacy upgade semantics because the resolver relied on inaccurate version data in the helm release label

Resolves #1009

Description

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

Write the correct label set to the helm release. This commit fixes an issue
where the upgrades get wedged after the first upgrade when following
legacy upgade semantics because the resolver relied on inaccurate version
data in the helm release label

Signed-off-by: kevinrizza <krizza@redhat.com>
@kevinrizza kevinrizza requested a review from a team as a code owner July 8, 2024 17:29
Copy link

netlify bot commented Jul 8, 2024

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit 3434b9f
🔍 Latest deploy log https://app.netlify.com/sites/olmv1/deploys/668c21f63d776600071f5554
😎 Deploy Preview https://deploy-preview-1017--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Jul 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.05%. Comparing base (5c83e91) to head (3434b9f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1017      +/-   ##
==========================================
- Coverage   78.07%   78.05%   -0.02%     
==========================================
  Files          18       18              
  Lines        1254     1253       -1     
==========================================
- Hits          979      978       -1     
  Misses        193      193              
  Partials       82       82              
Flag Coverage Δ
e2e 56.65% <100.00%> (+0.10%) ⬆️
unit 53.47% <0.00%> (-0.28%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@joelanford joelanford changed the title Set correct labels on helm release during upgrade 🐛 Set correct labels on helm release during upgrade Jul 8, 2024
@joelanford joelanford enabled auto-merge July 8, 2024 17:51
@joelanford joelanford added this pull request to the merge queue Jul 8, 2024
Merged via the queue into operator-framework:main with commit 235e3d4 Jul 8, 2024
17 of 19 checks passed
perdasilva pushed a commit to LalatenduMohanty/operator-controller that referenced this pull request Aug 13, 2024
…#1017)

Write the correct label set to the helm release. This commit fixes an issue
where the upgrades get wedged after the first upgrade when following
legacy upgade semantics because the resolver relied on inaccurate version
data in the helm release label

Signed-off-by: kevinrizza <krizza@redhat.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.

Resolution fails when manually upgrading through legacy replaces chain beyond n+1
2 participants