Skip to content

MGMT-24155: Use LVM operator instead of LSO for CNV dependency#10285

Open
shay23bra wants to merge 1 commit into
openshift:masterfrom
shay23bra:MGMT-24155-Use-LVM-operator-instead-of-LSO-for-CNV-dependency
Open

MGMT-24155: Use LVM operator instead of LSO for CNV dependency#10285
shay23bra wants to merge 1 commit into
openshift:masterfrom
shay23bra:MGMT-24155-Use-LVM-operator-instead-of-LSO-for-CNV-dependency

Conversation

@shay23bra
Copy link
Copy Markdown
Contributor

@shay23bra shay23bra commented May 6, 2026

Replaces the LSO dependency with LVM for CNV across all cluster topologies, as requested by the Virtualization team.
CNV now pulls LVM on SNO (OCP 4.12+), multi-node (OCP 4.15+), and returns no storage dependency for unsupported architectures (s390x, ppc64le) or older OCP versions — LSO is never pulled as a CNV dependency anymore.

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested) - unit-tests + manual creation of clusters for example:
    Before changes:
    "name": "test-cnv-multinode",        
    "openshift_version": "4.20",                                                                                                                                                                                  
    "cpu_architecture": "x86_64",
    "high_availability_mode": "Full",                                                                                                                                                                             
    "pull_secret": '"$(echo $PULL_SECRET | jq -R .)"',                                                                                                                                                            
    "olm_operators": [{"name": "cnv"}]                                                                                                                                                                            
  }'| jq '[.monitored_operators[] | select(.operator_type == "olm") | .name]'
[
  "cnv",
  "lso"
]

After changes:

curl -s -X POST "$API/clusters" -H 'Content-Type: application/json' -d '{                                                                                                                                    
    "name": "test-cnv-multinode2",        
    "openshift_version": "4.20",                                                                                                                                                                                  
    "cpu_architecture": "x86_64",
    "high_availability_mode": "Full",                                                                                                                                                                             
    "pull_secret": '"$(echo $PULL_SECRET | jq -R .)"',                                                                                                                                                            
    "olm_operators": [{"name": "cnv"}]                                                                                                                                                                            
  }'| jq '[.monitored_operators[] | select(.operator_type == "olm") | .name]'
[
  "cnv",
  "lvm"
]

  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

Summary by CodeRabbit

  • Refactor

    • Dependency selection now strictly follows LVM compatibility and version thresholds; incompatible clusters yield no dependencies.
    • Single-node vs multi-node behavior and unknown OpenShift version handling clarified.
    • Feature support reporting simplified to only indicate LVM (LSO removed).
  • Tests

    • Expanded, table-driven tests covering OpenShift versions, CPU architectures, SNO vs multi-node, and LVM/LSO selection fallbacks.

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

openshift-ci-robot commented May 6, 2026

@shay23bra: This pull request references MGMT-24155 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 bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Replaces the LSO dependency with LVM for CNV across all cluster topologies, as requested by the Virtualization team.
CNV now pulls LVM on SNO (OCP 4.12+), multi-node (OCP 4.15+), and returns no storage dependency for unsupported architectures (s390x, ppc64le) or older OCP versions — LSO is never pulled as a CNV dependency anymore.

List all the issues related to this PR

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment

  • dev-scripts environment

  • Reviewer's test appreciated

  • Waiting for CI to do a full test run

  • Manual (Elaborate on how it was tested) - unit-tests + manual creation of clusters for example:
    Before changes:
    curl -s -X POST "$API/clusters" -H 'Content-Type: application/json' -d '{ "name": "test-cnv-multinode", "openshift_version": "4.20", "cpu_architecture": "x86_64", "high_availability_mode": "Full", "pull_secret": '"$(echo $PULL_SECRET | jq -R .)"', "olm_operators": [{"name": "cnv"}] }'| jq '[.monitored_operators[] | select(.operator_type == "olm") | .name]' [ "cnv", "lso" ]
    After changes:
    curl -s -X POST "$API/clusters" -H 'Content-Type: application/json' -d '{
    "name": "test-cnv-multinode2",
    "openshift_version": "4.20",
    "cpu_architecture": "x86_64",
    "high_availability_mode": "Full",
    "pull_secret": '"$(echo $PULL_SECRET | jq -R .)"',
    "olm_operators": [{"name": "cnv"}]
    }'| jq '[.monitored_operators[] | select(.operator_type == "olm") | .name]'
    [
    "cnv",
    "lvm"
    ]

  • No tests needed

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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 openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 6, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 6, 2026

Walkthrough

GetDependencies now checks LVM feature compatibility by CPU architecture and OpenShift version, returning no dependencies when LVM is incompatible. For compatible clusters it prefers LVM (including when OCP version is empty), but falls back to LSO for SNO or multi-node clusters that don't meet LVM version/support thresholds. GetDependenciesFeatureSupportID reports only IDLVM. Tests were converted to table-driven cases covering OCP versions, architectures, and SNO vs multi-node scenarios.

Changes

CNV Dependency Selection

Layer / File(s) Summary
Feature Support Declaration
internal/operators/cnv/cnv_operator.go
GetDependenciesFeatureSupportID now returns only models.FeatureSupportLevelIDLVM (LSO removed from reported IDs).
Dependency Resolution Logic
internal/operators/cnv/cnv_operator.go
GetDependencies adds an architecture compatibility check for LVM (returns empty deps when incompatible); for compatible clusters returns LVM when OpenShift version is empty; for SNO returns LVM only if minimum LVM version threshold is met (otherwise falls back to LSO); for multi-node returns LVM only when multi-node LVM support threshold is met (otherwise falls back to LSO).
Tests — Dependency Table
internal/operators/cnv/cnv_operator_test.go
Replaced simpler tests with a richer table-driven DescribeTable that calls GetDependencies with parameters (OCP version, CPU architecture, control-plane count) and asserts the exact dependency slice (including empty deps and LSO vs LVM expectations).
Tests — Preflight Requirements
internal/operators/cnv/cnv_operator_test.go
Refactored GetPreflightRequirements tests into parameterized table entries asserting requirements.Dependencies and requirements.OperatorName across CNV config and cluster permutations (various OCP versions and SNO HPP settings).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning Tests lack meaningful assertion failure messages (required by criterion 4) and GetPreflightRequirements tests multiple unrelated behaviors (required by criterion 1). Add descriptive messages to assertions, e.g., Expect(deps).To(Equal(expectedDeps), "dependency check failed"). Split GetPreflightRequirements into separate focused tests for dependencies vs CPU/memory requirements.
✅ Passed checks (11 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically summarizes the main change: replacing LSO with LVM as the CNV operator's storage dependency.
Description check ✅ Passed The description comprehensively covers the change scope, version thresholds, architecture handling, testing approach with examples, and properly fills all key template sections.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed All test names are stable. No fmt.Sprintf, string concatenation, generated identifiers, timestamps, or dynamic values in test names. Test parameters correctly placed in test bodies.
Microshift Test Compatibility ✅ Passed PR modifies only unit tests in internal/operators/cnv/, not e2e tests. The check applies only to new Ginkgo e2e tests, which are absent from this PR.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The test file contains Ginkgo unit tests, not e2e tests. The custom check applies only to Ginkgo e2e tests and is not applicable to this PR.
Topology-Aware Scheduling Compatibility ✅ Passed Topology-aware. SNO vs multi-node handled via IsSingleNodeCluster(). HPP SNO-only, version-gated. No affinity rules, topology constraints, or control-plane selectors.
Ote Binary Stdout Contract ✅ Passed PR modifies CNV operator code and unit tests but does not contain OTE binary code. The check is only applicable to OTE binaries. No process-level stdout writes found in modified files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The custom check applies to Ginkgo e2e tests, but this PR only modifies unit tests in internal/operators/cnv/. The test file is not in an e2e directory. Check is not applicable to this PR.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

@openshift-ci openshift-ci Bot requested review from jhernand and pastequo May 6, 2026 12:56
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2026
Copy link
Copy Markdown

@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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@internal/operators/cnv/cnv_operator.go`:
- Around line 77-88: The version-compare errors from
common.BaseVersionGreaterOrEqual are currently ignored in the CNV dependency
logic; update the checks in the function (the block using
common.IsSingleNodeCluster and the subsequent multi-node check) to capture the
error return from common.BaseVersionGreaterOrEqual and propagate it back to the
caller instead of discarding it—i.e., for both calls that reference
lvm.LvmsMinOpenshiftVersion4_12 and lvm.LvmMinMultiNodeSupportVersion, check the
error and return nil, err when non-nil; keep the existing behavior of returning
[]string{lvm.Operator.Name}, nil when isSupported is true, otherwise continue
flow.
🪄 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: 9737446d-b865-468d-9f15-fcb642d2d1e0

📥 Commits

Reviewing files that changed from the base of the PR and between b8b5e5d and 54b760d.

📒 Files selected for processing (2)
  • internal/operators/cnv/cnv_operator.go
  • internal/operators/cnv/cnv_operator_test.go

Comment thread internal/operators/cnv/cnv_operator.go Outdated
@codecov
Copy link
Copy Markdown

codecov Bot commented May 6, 2026

Codecov Report

❌ Patch coverage is 90.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 44.42%. Comparing base (9511483) to head (bc2dcb1).
⚠️ Report is 12 commits behind head on master.

Files with missing lines Patch % Lines
internal/operators/cnv/cnv_operator.go 90.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10285      +/-   ##
==========================================
+ Coverage   44.35%   44.42%   +0.07%     
==========================================
  Files         416      417       +1     
  Lines       72792    73213     +421     
==========================================
+ Hits        32284    32522     +238     
- Misses      37577    37736     +159     
- Partials     2931     2955      +24     
Files with missing lines Coverage Δ
internal/operators/cnv/cnv_operator.go 77.12% <90.00%> (+2.26%) ⬆️

... and 8 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@rccrdpccl
Copy link
Copy Markdown
Contributor

@shay23bra should we drop dependencies in older OCP versions too?

@shay23bra
Copy link
Copy Markdown
Contributor Author

@shay23bra should we drop dependencies in older OCP versions too?

@rccrdpccl The ticket said: "If an architecture does not have it, it's fine to pull nothing." - So I assumed it was for all scenarios that do not have it, but maybe I was wrong and it should be only for 4.15+ ?

@shay23bra shay23bra force-pushed the MGMT-24155-Use-LVM-operator-instead-of-LSO-for-CNV-dependency branch 2 times, most recently from 7b8104c to 4d5b82a Compare May 7, 2026 09:03
@shay23bra
Copy link
Copy Markdown
Contributor Author

shay23bra commented May 7, 2026

For older versions that didn’t have LVM - multi-node OCP < 4.15 and SNO < 4.12, the existing LSO dependency is preserved as a fallback since LVM is not supported for those configurations.

@shay23bra shay23bra force-pushed the MGMT-24155-Use-LVM-operator-instead-of-LSO-for-CNV-dependency branch from 4d5b82a to bc2dcb1 Compare May 7, 2026 09:04
Copy link
Copy Markdown

@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: 2

🤖 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 `@internal/operators/cnv/cnv_operator_test.go`:
- Around line 54-64: The test entries that expect LSO should be changed to
expect no storage dependency: update each Entry that currently uses
[]string{lso.Operator.Name} to an empty slice (e.g., []string{}) for both
single-node and multi-node cases so GetDependencies and GetPreflightRequirements
assert no dependency; likewise update the duplicate block (lines around 351-362)
the same way and then remove the now-unused lso test import. Ensure you modify
the specific test entries that reference lso.Operator.Name and any related
import cleanup.

In `@internal/operators/cnv/cnv_operator.go`:
- Around line 78-89: The method currently falls back to returning
lso.Operator.Name for older OCP versions; change the logic so that when LVM is
not supported for the cluster (both single-node and multi-node checks using
common.BaseVersionGreaterOrEqual against lvm.LvmsMinOpenshiftVersion4_12 and
lvm.LvmMinMultiNodeSupportVersion) the function returns an empty slice (or nil)
instead of []string{lso.Operator.Name}, and then remove the unused lso import;
ensure this keeps the behavior aligned with GetDependenciesFeatureSupportID
which only reports LVM support.
🪄 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: 620c67e7-a6d9-4a56-b313-5d37e3b68dbf

📥 Commits

Reviewing files that changed from the base of the PR and between 54b760d and 7b8104c.

📒 Files selected for processing (2)
  • internal/operators/cnv/cnv_operator.go
  • internal/operators/cnv/cnv_operator_test.go

Comment thread internal/operators/cnv/cnv_operator_test.go
Comment thread internal/operators/cnv/cnv_operator.go
// to allow CNV ARM operator
if cluster.CPUArchitecture == common.ARM64CPUArchitecture || cluster.CPUArchitecture == common.MultiCPUArchitecture {
return make([]string, 0), nil
if !featuresupport.IsFeatureCompatibleWithArchitecture(models.FeatureSupportLevelIDLVM, cluster.OpenshiftVersion, cluster.CPUArchitecture) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If LVM not supported, return no dependencies? Isn't this contradicting For older versions that didn’t have LVM - multi-node OCP < 4.15 and SNO < 4.12, the existing LSO dependency is preserved as a fallback since LVM is not supported for those configurations. or am I reading it wrong?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nevermind, it's architecture specific 😅
sorry

@rccrdpccl
Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rccrdpccl, shay23bra

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:
  • OWNERS [rccrdpccl,shay23bra]

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

Copy link
Copy Markdown

@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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@internal/operators/cnv/cnv_operator.go`:
- Around line 92-94: GetDependenciesFeatureSupportID currently only returns
FeatureSupportLevelIDLVM but GetDependencies can also return lso.Operator.Name
for older OCP versions, so update the operator.GetDependenciesFeatureSupportID
implementation to include both feature IDs; modify the return so it includes
models.FeatureSupportLevelIDLVM and models.FeatureSupportLevelIDLSO (ensure you
reference the GetDependenciesFeatureSupportID function and the
models.FeatureSupportLevelIDLSO constant when making the 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: Enterprise

Run ID: cad88009-4799-477a-ba02-7b171e063f83

📥 Commits

Reviewing files that changed from the base of the PR and between 7b8104c and bc2dcb1.

📒 Files selected for processing (2)
  • internal/operators/cnv/cnv_operator.go
  • internal/operators/cnv/cnv_operator_test.go

Comment on lines 92 to 94
func (o *operator) GetDependenciesFeatureSupportID() []models.FeatureSupportLevelID {
return []models.FeatureSupportLevelID{models.FeatureSupportLevelIDLSO, models.FeatureSupportLevelIDLVM}
return []models.FeatureSupportLevelID{models.FeatureSupportLevelIDLVM}
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find how GetDependenciesFeatureSupportID is used to understand if this inconsistency matters
rg -n "GetDependenciesFeatureSupportID" --type=go -C5

Repository: openshift/assisted-service

Length of output: 34862


🏁 Script executed:

sed -n '60,95p' internal/operators/cnv/cnv_operator.go

Repository: openshift/assisted-service

Length of output: 1261


Add FeatureSupportLevelIDLSO to GetDependenciesFeatureSupportID to match all possible dependencies.

GetDependencies returns lso.Operator.Name for older OCP versions (SNO < 4.12, multi-node < 4.15), but GetDependenciesFeatureSupportID returns only FeatureSupportLevelIDLVM. This inconsistency breaks the contract that GetDependenciesFeatureSupportID should return all potential feature IDs that GetDependencies could return. Callers using this method for feature support validation will incorrectly pass compatibility checks when LSO is required but not included.

Update line 93 to:

return []models.FeatureSupportLevelID{models.FeatureSupportLevelIDLVM, models.FeatureSupportLevelIDLSO}
🤖 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 `@internal/operators/cnv/cnv_operator.go` around lines 92 - 94,
GetDependenciesFeatureSupportID currently only returns FeatureSupportLevelIDLVM
but GetDependencies can also return lso.Operator.Name for older OCP versions, so
update the operator.GetDependenciesFeatureSupportID implementation to include
both feature IDs; modify the return so it includes
models.FeatureSupportLevelIDLVM and models.FeatureSupportLevelIDLSO (ensure you
reference the GetDependenciesFeatureSupportID function and the
models.FeatureSupportLevelIDLSO constant when making the change).

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 991996c and 2 for PR HEAD bc2dcb1 in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD eb2dc70 and 1 for PR HEAD bc2dcb1 in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD babc11d and 0 for PR HEAD bc2dcb1 in total

@shay23bra
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/hold

Revision bc2dcb1 was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 10, 2026
@shay23bra
Copy link
Copy Markdown
Contributor Author

/retest-required

@shay23bra
Copy link
Copy Markdown
Contributor Author

/retest

@gamli75
Copy link
Copy Markdown
Contributor

gamli75 commented May 10, 2026

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 10, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD babc11d and 2 for PR HEAD bc2dcb1 in total

@shay23bra
Copy link
Copy Markdown
Contributor Author

/retest-required

@bfournie
Copy link
Copy Markdown
Contributor

The agent-compact-ipv4-iso-no-registry test is failing because:

  • lvm requires an additional non-installation disk, i.e.
    {ID:lvm-requirements-satisfied Status:failure Message:Logical Volume Manager requires at least one non-installation HDD/SSD disk on the host}
  • vcpu must be 10 in order for the role to be assigned as master

I've made a dev-scripts fix here openshift-metal3/dev-scripts#1891 and confirmed the iso-no-registry test passes with those changes.

@andfasano
Copy link
Copy Markdown
Contributor

I wasn't expecting a failure in this job (one that consumes operators btw)

/test e2e-agent-compact-ipv4-iso-no-registry

@bfournie
Copy link
Copy Markdown
Contributor

/test e2e-agent-compact-ipv4-iso-no-registry

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 12, 2026

@shay23bra: The following tests 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/edge-verify-generated-code bc2dcb1 link true /test edge-verify-generated-code
ci/prow/edge-e2e-ai-operator-ztp bc2dcb1 link unknown /test edge-e2e-ai-operator-ztp

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.

@shay23bra
Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 13, 2026
@bfournie
Copy link
Copy Markdown
Contributor

/test e2e-agent-compact-ipv4-iso-no-registry

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants