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

[backport v2.9] [SURE-9137] Add template errors to bundle and gitrepo status #3196

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

p-se
Copy link
Contributor

@p-se p-se commented Jan 9, 2025

  • Import v1alpha1 package as fleet

  • Show bundle errors in Bundle and GitRepo

Refers to #2943

  • Add E2E tests

Refers to #2943

(cherry picked from commit 235e8ef) (cherry picked from commit 3417071)

Refers to #3191

…#3114)

* Import v1alpha1 package as fleet

* Show bundle errors in Bundle and GitRepo

Refers to rancher#2943

* Add E2E tests

Refers to rancher#2943

(cherry picked from commit 235e8ef)
(cherry picked from commit 3417071)
@p-se p-se marked this pull request as ready for review January 9, 2025 15:46
@p-se p-se requested a review from a team as a code owner January 9, 2025 15:46
@p-se p-se added this to the v2.9.6 milestone Jan 9, 2025
@p-se p-se changed the title [backport v2.9] [SURE-9137] Add template errors to bundle and gitrepo status (#3114) [backport v2.9] [SURE-9137] Add template errors to bundle and gitrepo status (#3191) Jan 9, 2025
@p-se p-se changed the title [backport v2.9] [SURE-9137] Add template errors to bundle and gitrepo status (#3191) [backport v2.9] [SURE-9137] Add template errors to bundle and gitrepo status Jan 9, 2025
@@ -215,6 +220,18 @@ func (r *BundleReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctr

matchedTargets, err := r.Builder.Targets(ctx, bundle, manifestID)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want to take the opportunity to remove RetryOnConflict loops (around L150) for adding and removing finalizers here, as done for other release branches?

Copy link
Member

Choose a reason for hiding this comment

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

Is that like a one liner? Otherwise it sounds to me like a different issue/PR.

@manno manno merged commit 8f4e4b2 into rancher:release/v0.10 Jan 10, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants