Skip to content

OCPEDGE-2307: Update Arbiter Node tests based on platform type#30823

Open
vimauro wants to merge 4 commits intoopenshift:mainfrom
vimauro:vimauro/platform_none_tests
Open

OCPEDGE-2307: Update Arbiter Node tests based on platform type#30823
vimauro wants to merge 4 commits intoopenshift:mainfrom
vimauro:vimauro/platform_none_tests

Conversation

@vimauro
Copy link

@vimauro vimauro commented Mar 2, 2026

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

Summary by CodeRabbit

  • Tests
    • Enhanced tests to support platform-specific pod expectations using per-platform mappings.
    • Added runtime initialization during test setup so expected pod counts are populated from the detected platform.
    • Updated pod validation to use the runtime-populated expectations, ensuring correct counts across different platforms.

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 2, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

@vimauro: This pull request references OCPEDGE-2307 which is a valid jira issue.

Details

In response to this:

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 2, 2026

Walkthrough

Reworked arbiter topology test to initialize platform-specific pod expectations at runtime. Added expectedPodsByPlatform, runtime expectedPods with expectedPodsOnce, initExpectedPods(oc) to select counts from Infrastructure.Status.PlatformStatus.Type, imported sync, and call initialization in BeforeEach.

Changes

Cohort / File(s) Summary
Arbiter Topology Pod Configuration
test/extended/two_node/arbiter_topology.go
Replaced a single inline expectedPods map with expectedPodsByPlatform keyed by platform type; added sync import; introduced var expectedPods map[string]int and var expectedPodsOnce sync.Once; added initExpectedPods(oc) to populate expectedPods at runtime from Infrastructure.Status.PlatformStatus.Type; invoke initExpectedPods(oc) in BeforeEach; updated Arbiter pod validation to use the runtime expectedPods.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Structure And Quality ⚠️ Warning Tests in arbiter_topology.go have quality violations including missing failure messages, missing timeouts, and inconsistent patterns. Add descriptive messages to Expect calls, split combined test blocks, refactor etcd test to use exutil.WaitForPods pattern with timeout.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: updating Arbiter Node tests to adjust expectations based on platform type detected at runtime.
Stable And Deterministic Test Names ✅ Passed All 11 test titles are static and deterministic with no dynamic information like pod names, node names, or timestamps.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.5.0)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

@vimauro: This pull request references OCPEDGE-2307 which is a valid jira issue.

Details

In response to this:

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

Summary by CodeRabbit

  • Tests
  • Enhanced test configuration to support platform-specific pod expectations
  • Implemented runtime initialization of pod expectations based on infrastructure platform detection

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

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/two_node/arbiter_topology.go`:
- Around line 56-64: The BeforeSuite reads infra.Status.PlatformStatus.Type
without checking for nil; update the g.BeforeSuite initialization to guard
against a nil PlatformStatus by using infra.Status.PlatformStatus.Type when
infra.Status.PlatformStatus != nil, otherwise fall back to infra.Status.Platform
(or infra.Status.PlatformType) to derive platformType, then continue to
lowercase it and lookup expectedPodsByPlatform; reference the
variables/functions infra, PlatformStatus, Platform, platformType,
expectedPodsByPlatform and expectedPods to locate and apply the change.

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 02e33c2 and 5bc4c3f.

📒 Files selected for processing (1)
  • test/extended/two_node/arbiter_topology.go

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

@vimauro: This pull request references OCPEDGE-2307 which is a valid jira issue.

Details

In response to this:

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

Summary by CodeRabbit

  • Tests
  • Enhanced tests to support platform-specific pod expectations.
  • Implemented runtime initialization so tests determine expected pod counts based on detected platform.
  • Improved test setup to ensure platform-dependent expectations are applied before validation.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
test/extended/two_node/arbiter_topology.go (1)

58-67: ⚠️ Potential issue | 🔴 Critical

Guard PlatformStatus before dereferencing Type to avoid panic.

At Line 62, infra.Status.PlatformStatus.Type is accessed without checking whether PlatformStatus is nil. That can panic and fail the spec setup path. Please fall back to infra.Status.Platform when PlatformStatus is nil.

Proposed fix
 func initExpectedPods(oc *exutil.CLI) {
 	expectedPodsOnce.Do(func() {
 		infra, err := oc.AdminConfigClient().ConfigV1().Infrastructures().Get(context.Background(), "cluster", metav1.GetOptions{})
 		o.Expect(err).To(o.BeNil(), "Expected to retrieve infrastructure details without error")
-		platformType := strings.ToLower(string(infra.Status.PlatformStatus.Type))
+		platformType := strings.ToLower(string(infra.Status.Platform))
+		if infra.Status.PlatformStatus != nil {
+			platformType = strings.ToLower(string(infra.Status.PlatformStatus.Type))
+		}
 
 		var ok bool
 		expectedPods, ok = expectedPodsByPlatform[platformType]
 		o.Expect(ok).To(o.BeTrue(), "Expected to find expected pods for platform %s", platformType)
 	})
 }
#!/bin/bash
set -euo pipefail

# Verify InfrastructureStatus fields and pointer semantics.
rg -n --type go 'type InfrastructureStatus struct|PlatformStatus\s+\*PlatformStatus|Platform\s+PlatformType'

# Verify the dereference site in this file.
rg -n --type go -C2 'PlatformStatus\.Type' test/extended/two_node/arbiter_topology.go
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/two_node/arbiter_topology.go` around lines 58 - 67, The code in
initExpectedPods dereferences infra.Status.PlatformStatus.Type without guarding
PlatformStatus; update initExpectedPods to check if infra.Status.PlatformStatus
!= nil and use infra.Status.PlatformStatus.Type when present, otherwise fall
back to infra.Status.Platform, then normalize to lowercase as before and lookup
expectedPodsByPlatform; ensure you still call expectedPodsOnce.Do and keep the
same expectations (o.Expect) around the lookup (referencing initExpectedPods,
expectedPodsOnce, infra.Status.PlatformStatus.Type and infra.Status.Platform).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@test/extended/two_node/arbiter_topology.go`:
- Around line 58-67: The code in initExpectedPods dereferences
infra.Status.PlatformStatus.Type without guarding PlatformStatus; update
initExpectedPods to check if infra.Status.PlatformStatus != nil and use
infra.Status.PlatformStatus.Type when present, otherwise fall back to
infra.Status.Platform, then normalize to lowercase as before and lookup
expectedPodsByPlatform; ensure you still call expectedPodsOnce.Do and keep the
same expectations (o.Expect) around the lookup (referencing initExpectedPods,
expectedPodsOnce, infra.Status.PlatformStatus.Type and infra.Status.Platform).

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 5bc4c3f and 0c3cc1a.

📒 Files selected for processing (1)
  • test/extended/two_node/arbiter_topology.go

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

Copy link
Contributor

@eggfoobar eggfoobar left a comment

Choose a reason for hiding this comment

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

Looks great, small suggestion on which keys to use

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

@vimauro: This pull request references OCPEDGE-2307 which is a valid jira issue.

Details

In response to this:

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

Summary by CodeRabbit

  • Tests
  • Enhanced tests to support platform-specific pod expectations via per-platform mappings.
  • Added runtime initialization so tests populate expected pod counts based on the detected platform during setup.
  • Updated test validation to use the runtime-populated expectations, ensuring correct pod counts across platforms.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
test/extended/two_node/arbiter_topology.go (1)

58-66: ⚠️ Potential issue | 🔴 Critical

Critical: platformType is undefined and PlatformStatus is dereferenced unsafely.

Line 65 won’t compile (platformType is not declared), and Line 64 can panic when infra.Status.PlatformStatus == nil.

🔧 Proposed fix
 func initExpectedPods(oc *exutil.CLI) {
 	expectedPodsOnce.Do(func() {
 		infra, err := oc.AdminConfigClient().ConfigV1().Infrastructures().Get(context.Background(), "cluster", metav1.GetOptions{})
 		o.Expect(err).To(o.BeNil(), "Expected to retrieve infrastructure details without error")
 
+		platformType := infra.Status.Platform
+		if infra.Status.PlatformStatus != nil {
+			platformType = infra.Status.PlatformStatus.Type
+		}
+
 		var ok bool
-		expectedPods, ok = expectedPodsByPlatform[infra.Status.PlatformStatus.Type]
+		expectedPods, ok = expectedPodsByPlatform[platformType]
 		o.Expect(ok).To(o.BeTrue(), "Expected to find expected pods for platform %s", platformType)
 	})
 }
#!/bin/bash
# Read-only verification: confirm unsafe dereference and undefined identifier usage in initializer.
rg -n -C3 'func initExpectedPods|PlatformStatus\.Type|platformType' test/extended/two_node/arbiter_topology.go
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/two_node/arbiter_topology.go` around lines 58 - 66, The
initExpectedPods function references an undefined platformType and unsafely
dereferences infra.Status.PlatformStatus; update initExpectedPods to first check
that infra.Status.PlatformStatus is non-nil, then assign platformType :=
infra.Status.PlatformStatus.Type, and use that variable in the lookup
expectedPods, ok = expectedPodsByPlatform[platformType] and in the o.Expect
message; if PlatformStatus is nil, fail the expectation with a clear error
(e.g., o.Expect(infra.Status.PlatformStatus).ToNot(o.BeNil(), "Expected
Infrastructure PlatformStatus to be set")) before accessing Type.
🧹 Nitpick comments (2)
test/extended/two_node/arbiter_topology.go (2)

26-51: Reduce duplication in per-platform expected pod maps.

The two platform maps are nearly identical; extracting a shared base and applying per-platform overrides will lower drift risk.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/two_node/arbiter_topology.go` around lines 26 - 51, The two
maps under expectedPodsByPlatform are almost identical; define a single base map
(e.g., baseExpectedPods map[string]int) containing the common entries, then
build expectedPodsByPlatform using copies of that base for
v1.BareMetalPlatformType and v1.NonePlatformType, applying per-platform
overrides (for example add "openshift-kni-infra": 1 to the BareMetal copy).
Ensure you copy the base map when assigning to each platform (do not reuse the
same map reference) so subsequent mutations won't affect other entries; update
references to expectedPodsByPlatform accordingly.

59-66: Avoid o.Expect(...) inside sync.Once.Do(...) initializer.

If an assertion panics once, sync.Once can still be marked done, leaving expectedPods unset for subsequent specs in the same process.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/two_node/arbiter_topology.go` around lines 59 - 66, The current
sync.Once initializer (expectedPodsOnce.Do) performs test assertions via
o.Expect which can panic and leave the Once marked done without setting
expectedPods; change the initializer to only perform non-panic assignments and
capture any error into a local variable (e.g. initErr) and the platform type
into a local variable, then after expectedPodsOnce.Do(...) run
o.Expect(initErr).To(o.BeNil(), ...) and assert that expectedPods was found
(using the captured platform) outside the Do block; specifically update the
expectedPodsOnce.Do closure to set infra, initErr, platformType and expectedPods
from expectedPodsByPlatform (setting an ok flag) but do not call o.Expect inside
the closure, then perform the o.Expect checks for err and ok immediately after
the Do call.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@test/extended/two_node/arbiter_topology.go`:
- Around line 58-66: The initExpectedPods function references an undefined
platformType and unsafely dereferences infra.Status.PlatformStatus; update
initExpectedPods to first check that infra.Status.PlatformStatus is non-nil,
then assign platformType := infra.Status.PlatformStatus.Type, and use that
variable in the lookup expectedPods, ok = expectedPodsByPlatform[platformType]
and in the o.Expect message; if PlatformStatus is nil, fail the expectation with
a clear error (e.g., o.Expect(infra.Status.PlatformStatus).ToNot(o.BeNil(),
"Expected Infrastructure PlatformStatus to be set")) before accessing Type.

---

Nitpick comments:
In `@test/extended/two_node/arbiter_topology.go`:
- Around line 26-51: The two maps under expectedPodsByPlatform are almost
identical; define a single base map (e.g., baseExpectedPods map[string]int)
containing the common entries, then build expectedPodsByPlatform using copies of
that base for v1.BareMetalPlatformType and v1.NonePlatformType, applying
per-platform overrides (for example add "openshift-kni-infra": 1 to the
BareMetal copy). Ensure you copy the base map when assigning to each platform
(do not reuse the same map reference) so subsequent mutations won't affect other
entries; update references to expectedPodsByPlatform accordingly.
- Around line 59-66: The current sync.Once initializer (expectedPodsOnce.Do)
performs test assertions via o.Expect which can panic and leave the Once marked
done without setting expectedPods; change the initializer to only perform
non-panic assignments and capture any error into a local variable (e.g. initErr)
and the platform type into a local variable, then after expectedPodsOnce.Do(...)
run o.Expect(initErr).To(o.BeNil(), ...) and assert that expectedPods was found
(using the captured platform) outside the Do block; specifically update the
expectedPodsOnce.Do closure to set infra, initErr, platformType and expectedPods
from expectedPodsByPlatform (setting an ok flag) but do not call o.Expect inside
the closure, then perform the o.Expect checks for err and ok immediately after
the Do call.

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 0c3cc1a and b6f644d.

📒 Files selected for processing (1)
  • test/extended/two_node/arbiter_topology.go

@eggfoobar
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 2, 2026
@vimauro
Copy link
Author

vimauro commented Mar 2, 2026

/retest

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 2, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

@vimauro: This pull request references OCPEDGE-2307 which is a valid jira issue.

Details

In response to this:

Update Arbiter Node tests based on platform type since we are adding a CI lane for platform:none here openshift/release#75055

Summary by CodeRabbit

  • Tests
  • Enhanced tests to support platform-specific pod expectations using per-platform mappings.
  • Added runtime initialization during test setup so expected pod counts are populated from the detected platform.
  • Updated pod validation to use the runtime-populated expectations, ensuring correct counts across different platforms.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
test/extended/two_node/arbiter_topology.go (1)

58-66: ⚠️ Potential issue | 🔴 Critical

Guard PlatformStatus before dereferencing Type (panic risk).

At Line 64, infra.Status.PlatformStatus.Type is dereferenced unconditionally. PlatformStatus can be nil, which can panic during setup and fail the suite.

🔧 Proposed fix
 func initExpectedPods(oc *exutil.CLI) {
 	expectedPodsOnce.Do(func() {
 		infra, err := oc.AdminConfigClient().ConfigV1().Infrastructures().Get(context.Background(), "cluster", metav1.GetOptions{})
 		o.Expect(err).To(o.BeNil(), "Expected to retrieve infrastructure details without error")
 
+		platformType := infra.Status.Platform
+		if infra.Status.PlatformStatus != nil {
+			platformType = infra.Status.PlatformStatus.Type
+		}
+
 		var ok bool
-		expectedPods, ok = expectedPodsByPlatform[infra.Status.PlatformStatus.Type]
-		o.Expect(ok).To(o.BeTrue(), "Expected to find expected pods for platform %s", infra.Status.PlatformStatus.Type)
+		expectedPods, ok = expectedPodsByPlatform[platformType]
+		o.Expect(ok).To(o.BeTrue(), "Expected to find expected pods for platform %s", platformType)
 	})
 }
#!/bin/bash
# Verify InfrastructureStatus field types and optionality, and current dereference site.
set -euo pipefail

echo "== InfrastructureStatus / PlatformStatus definitions =="
rg -n -C3 'type InfrastructureStatus struct|PlatformStatus \*PlatformStatus|Platform\s+PlatformType' --type go

echo
echo "== Current dereference in arbiter_topology.go =="
rg -n -C2 'PlatformStatus\.Type|expectedPodsByPlatform\[' test/extended/two_node/arbiter_topology.go
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/extended/two_node/arbiter_topology.go` around lines 58 - 66, The code
dereferences infra.Status.PlatformStatus.Type inside initExpectedPods without
guarding for a nil PlatformStatus which can panic; update initExpectedPods to
first check infra.Status.PlatformStatus for nil and fail the test with a clear
o.Expect message if it's nil, otherwise read the platform into a local variable
(e.g. platform := infra.Status.PlatformStatus.Type) and use that key when
looking up expectedPodsByPlatform and assigning expectedPods; ensure the error
message in the o.Expect(ok) includes the platform variable and that the
nil-PlatformStatus case is explicitly handled to avoid a panic.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@test/extended/two_node/arbiter_topology.go`:
- Around line 58-66: The code dereferences infra.Status.PlatformStatus.Type
inside initExpectedPods without guarding for a nil PlatformStatus which can
panic; update initExpectedPods to first check infra.Status.PlatformStatus for
nil and fail the test with a clear o.Expect message if it's nil, otherwise read
the platform into a local variable (e.g. platform :=
infra.Status.PlatformStatus.Type) and use that key when looking up
expectedPodsByPlatform and assigning expectedPods; ensure the error message in
the o.Expect(ok) includes the platform variable and that the nil-PlatformStatus
case is explicitly handled to avoid a panic.

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between b6f644d and 7d2cb57.

📒 Files selected for processing (1)
  • test/extended/two_node/arbiter_topology.go

@eggfoobar
Copy link
Contributor

/label tide/merge-method-squash
/lgtm

@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. lgtm Indicates that a PR is ready to be merged. labels Mar 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eggfoobar, vimauro

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@vimauro
Copy link
Author

vimauro commented Mar 2, 2026

/retest

@openshift-ci-robot
Copy link

@vimauro: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified via CI

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.

@vimauro
Copy link
Author

vimauro commented Mar 3, 2026

/verified by @vimauro via CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 3, 2026
@openshift-ci-robot
Copy link

@vimauro: This PR has been marked as verified by @vimauro via CI.

Details

In response to this:

/verified by @vimauro via CI

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.

@vimauro
Copy link
Author

vimauro commented Mar 3, 2026

/retest

@vimauro
Copy link
Author

vimauro commented Mar 3, 2026

looks like there is currently a known issue in CI preventing the last test to succeeds. This has been already reported on Slack.

tag "rhel-coreos" has an invalid io.openshift.build.versions or io.openshift.build.version-display-names label: the display name "Red Hat Enterprise Linux CoreOS 9.8" must only be alphanumerics, spaces, and symbols in [():-]

@eggfoobar
Copy link
Contributor

/test images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

@vimauro: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images 7d2cb57 link true /test images

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants