OCPEDGE-2072: bump(ocp/api): pull in latest for DualReplica promotion#10471
OCPEDGE-2072: bump(ocp/api): pull in latest for DualReplica promotion#10471eggfoobar wants to merge 2 commits intoopenshift:mainfrom
Conversation
|
@eggfoobar: This pull request references OCPEDGE-2072 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 "4.22.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. |
|
/hold Waiting for API change to be merged into main |
|
[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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (21)
📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughBumps Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.11.4)Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions Comment |
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 `@go.mod`:
- Line 385: The replace directive "replace github.com/openshift/api =>
github.com/eggfoobar/api v0.0.0-20260406200249-1966dc1a21a7" needs an inline
temporary-comment and a tracking reference: add a one-line comment immediately
above that replace in go.mod stating this is a temporary fork, why it's needed,
and reference the tracking issue/PR ID (e.g. "TEMPORARY: using fork until
upstream change merged — tracking: GH-XXXX / JIRA-YYYY"). Also verify the fork's
accessibility (public vs private) and, if private, either make it accessible or
switch to a public mirror; finally ensure a real tracking mechanism exists
(create and link a GitHub issue or Jira ticket) so the replace can be removed
once upstream openshift/api is updated.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 55425338-cb61-405e-9fb5-59ae10b1a312
⛔ Files ignored due to path filters (21)
go.sumis excluded by!**/*.sumvendor/github.com/openshift/api/config/v1/types.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/types_authentication.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/types_dns.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/types_infrastructure.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/zz_generated.deepcopy.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/zz_generated.featuregated-crd-manifests.yamlis excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1/zz_generated.swagger_doc_generated.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1alpha1/types_cluster_monitoring.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1alpha1/zz_generated.deepcopy.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/config/v1alpha1/zz_generated.swagger_doc_generated.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/features/features.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/machineconfiguration/v1/types.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/machineconfiguration/v1/types_machineconfignode.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/machineconfiguration/v1/zz_generated.featuregated-crd-manifests.yamlis excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/machineconfiguration/v1/zz_generated.swagger_doc_generated.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/operator/v1/types_csi_cluster_driver.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/operator/v1/types_ingress.gois excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/operator/v1/zz_generated.featuregated-crd-manifests.yamlis excluded by!vendor/**,!**/vendor/**vendor/github.com/openshift/api/operator/v1/zz_generated.swagger_doc_generated.gois excluded by!vendor/**,!**/vendor/**vendor/modules.txtis excluded by!vendor/**,!**/vendor/**
📒 Files selected for processing (1)
go.mod
There was a problem hiding this comment.
🧹 Nitpick comments (1)
pkg/types/validation/featuregate_test.go (1)
199-205: Pin the default feature set explicitly in this case.The case name says "Default Feature Set", but it currently depends on
validInstallConfig()defaults. Settingc.FeatureSet = v1.Defaultmakes the scenario self-contained and prevents silent drift if that helper changes.♻️ Proposed tweak
{ name: "FencingCredentials is allowed in Default Feature Set", installConfig: func() *types.InstallConfig { c := validInstallConfig() + c.FeatureSet = v1.Default c.ControlPlane.Fencing = &types.Fencing{Credentials: []*types.Credential{{HostName: "host1"}, {HostName: "host2"}}} return c }(), },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@pkg/types/validation/featuregate_test.go` around lines 199 - 205, The test relies on validInstallConfig() defaults but the case claims "Default Feature Set"; update the test setup to explicitly pin the feature set by setting c.FeatureSet = v1.Default after calling validInstallConfig() so the scenario is self-contained and won't break if validInstallConfig() defaults change; modify the anonymous installConfig func that creates c, locate the usage of validInstallConfig(), and add c.FeatureSet = v1.Default (referencing c, validInstallConfig, and types.Fencing/ControlPlane.Fencing) before returning c.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@pkg/types/validation/featuregate_test.go`:
- Around line 199-205: The test relies on validInstallConfig() defaults but the
case claims "Default Feature Set"; update the test setup to explicitly pin the
feature set by setting c.FeatureSet = v1.Default after calling
validInstallConfig() so the scenario is self-contained and won't break if
validInstallConfig() defaults change; modify the anonymous installConfig func
that creates c, locate the usage of validInstallConfig(), and add c.FeatureSet =
v1.Default (referencing c, validInstallConfig, and
types.Fencing/ControlPlane.Fencing) before returning c.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: d71e99ae-69ba-440f-8982-d0880bb81a64
📒 Files selected for processing (2)
pkg/asset/agent/installconfig_test.gopkg/types/validation/featuregate_test.go
|
@eggfoobar: The following tests 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. |
Signed-off-by: ehila <ehila@redhat.com>
Signed-off-by: ehila <ehila@redhat.com>
|
/unhold |
|
@eggfoobar: This PR has been marked as verified by 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. |
No description provided.