SPLAT-2713: Update AWS CCM e2e test module version#476
Conversation
Updates the AWS CCM e2e tests module version to the latest version which includes changes like the addition of e2e tests for the BYO Security Group for AWS Network Load Balancer feat.
|
Skipping CI for Draft Pull Request. |
|
@mfbonfigli: This pull request references SPLAT-2713 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Warning Review limit reached
More reviews will be available in 48 minutes and 2 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
WalkthroughThe ChangesCloud Provider Dependency Update
Test Assertion Robustness
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 13 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (13 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/retest |
1 similar comment
|
/retest |
Attempts to fix a failing unit test that passes locally but not on CI by wrapping it into an Eventually block
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
pkg/controllers/cloud_config_sync_controller_test.go (1)
607-611: ⚡ Quick winAdd descriptive failure message to assertion.
The assertion lacks a custom failure message. Adding one would improve debuggability when the test fails by clearly explaining what condition was expected.
📝 Proposed fix to add failure message
Eventually(func() int { allCMs := &corev1.ConfigMapList{} Expect(cl.List(ctx, allCMs, &client.ListOptions{Namespace: targetNamespaceName})).To(Succeed()) return len(allCMs.Items) -}).Should(BeZero()) +}, 10*time.Second, 100*time.Millisecond).Should(BeZero(), "Expected no ConfigMaps to be created for BareMetal platform")As per coding guidelines: "Assertions should include meaningful failure messages."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@pkg/controllers/cloud_config_sync_controller_test.go` around lines 607 - 611, The Eventually assertion that checks the ConfigMap count is zero lacks a custom failure message, which makes debugging harder when the test fails. Add a descriptive failure message to the Eventually().Should(BeZero()) assertion chain to explain what condition is expected. Use the appropriate Gomega method (such as WithMessage or similar) to attach a clear error message that will be displayed if the assertion fails, explaining that all ConfigMaps in the target namespace should be cleaned up or deleted.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pkg/controllers/cloud_config_sync_controller_test.go`:
- Around line 607-611: The Eventually block that lists ConfigMaps in the
targetNamespace lacks an explicit timeout parameter, which can cause the test to
hang indefinitely if the reconciler misbehaves. Add a timeout argument to the
Eventually function call (something like Eventually(func(), timeout.Duration))
to ensure the test fails gracefully if ConfigMaps are not cleaned up within a
reasonable timeframe. Include both the timeout and optionally a polling interval
to comply with Ginkgo testing guidelines for cluster-interacting operations.
---
Nitpick comments:
In `@pkg/controllers/cloud_config_sync_controller_test.go`:
- Around line 607-611: The Eventually assertion that checks the ConfigMap count
is zero lacks a custom failure message, which makes debugging harder when the
test fails. Add a descriptive failure message to the
Eventually().Should(BeZero()) assertion chain to explain what condition is
expected. Use the appropriate Gomega method (such as WithMessage or similar) to
attach a clear error message that will be displayed if the assertion fails,
explaining that all ConfigMaps in the target namespace should be cleaned up or
deleted.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 9c0dba32-c5a4-4248-b5a6-ca9e439cf1a3
📒 Files selected for processing (1)
pkg/controllers/cloud_config_sync_controller_test.go
|
/retest |
|
@mfbonfigli: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
2 participants
What
Updates the AWS CCM e2e tests module version to the latest version, including refreshing the vendored dependencies for the test binary.
Why
The purpose is to pull down the latest test changes which include new e2e tests for the BYO Security Groups feature for AWS Network Load Balancers. The feature has already been merged in upstream and downstream AWS CCM. Updating the test dependency will ensure these e2e tests will run in downstream constantly ensuring the feature works as expected.
Summary by CodeRabbit