OCPBUGS-83598: Add missing generateIPAMLifecycle in ClusterUDN manifest#31018
OCPBUGS-83598: Add missing generateIPAMLifecycle in ClusterUDN manifest#31018mkowalski wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@mkowalski: This pull request references Jira Issue OCPBUGS-83598, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/payload-job periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview |
|
@mkowalski: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/78eb1530-39a7-11f1-9c7b-9526bc13e938-0 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Walkthrough
Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 9 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (9 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mkowalski 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@test/extended/networking/network_segmentation.go`:
- Line 1336: The generated YAML puts `ipam:` and `lifecycle:` at the same indent
because generateIPAMLifecycle(...) returns a string with hardcoded leading
spaces; update generateIPAMLifecycle to either accept an indent/prefix parameter
or to return an unindented block so the caller (the template concatenating ` +
generateIPAMLifecycle(params) + `) can indent it under the existing `ipam:`
line; ensure the final output nests `lifecycle:` under `ipam:` (i.e., `ipam:`
line followed by the properly indented lifecycle block) and adjust any callers
of generateIPAMLifecycle accordingly (the function name generateIPAMLifecycle is
the unique symbol to change).
🪄 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: Pro Plus
Run ID: 68838cf7-6fd7-491f-80e5-00a9d33ab908
📒 Files selected for processing (1)
test/extended/networking/network_segmentation.go
|
Scheduling required tests: |
…efinedNetwork manifest The generateClusterUserDefinedNetworkManifest function was missing the generateIPAMLifecycle call, unlike its counterpart generateUserDefinedNetworkManifest. This caused ClusterUserDefinedNetwork manifests to be generated without IPAM lifecycle configuration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
14f585b to
7fc5d5a
Compare
|
Scheduling required tests: |
|
/payload-job e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview |
|
@mkowalski: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6eec3270-39d0-11f1-9cb3-bb972e4fa1f4-0 |
|
@mkowalski: 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. |
Summary
generateIPAMLifecycle(params)call ingenerateClusterUserDefinedNetworkManifest, matching the existing pattern ingenerateUserDefinedNetworkManifestClusterUserDefinedNetworkmanifests were generated without IPAM lifecycle configurationTest plan
ClusterUserDefinedNetworkmanifests now include IPAM lifecycle configuration when specifiedUserDefinedNetworkmanifest generation is unaffected🤖 Generated with Claude Code
Summary by CodeRabbit