Skip to content

OCPBUGS-79576: Mark raw FC/iSCSI multipath members as ineligible#10142

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
yoavsc0302:OCPBUGS-79576-option-b-with-revert
Apr 15, 2026
Merged

OCPBUGS-79576: Mark raw FC/iSCSI multipath members as ineligible#10142
openshift-merge-bot[bot] merged 2 commits intoopenshift:masterfrom
yoavsc0302:OCPBUGS-79576-option-b-with-revert

Conversation

@yoavsc0302
Copy link
Copy Markdown
Contributor

@yoavsc0302 yoavsc0302 commented Apr 14, 2026

Two commits:

  1. Revert PR OCPBUGS-79576: Prefer multipath disk in ABI disk selection #10091 — The GetPreferredDiskID approach is bypassed by the "already matches" early return in applyRootDeviceHints(): if Phase 1 auto-selects a raw FC/iSCSI path and it appears in the acceptable disk list, the function returns before GetPreferredDiskID is ever called. Confirmed on s390x FC multipath hardware.

  2. Mark raw FC/iSCSI multipath members as ineligible — Raw FC and iSCSI disks that are members of a multipath device are now marked as ineligible at the validator level. Writing to a raw path instead of the multipath device causes installation failure (ENODEV) when multipathd reclaims the disk. By making them ineligible at the source, they are filtered out from all disk selection paths (SaaS, ZTP, ABI), no bypass is possible, and they show as ineligible in the UI with a clear reason.

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)
  • 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

Release Notes

  • Bug Fixes

    • Disks that are members of multipath setups (e.g., FC/iSCSI holders) are now correctly detected and marked ineligible for installation.
  • Refactor

    • Disk selection for installation targets made deterministic when multiple matches exist (chooses the first acceptable disk).
    • Removed an unused disk-selection utility and related tests.

This reverts merge commit a63f435 (PR openshift#10091).

The GetPreferredDiskID approach is bypassed by the "already matches"
short-circuit in applyRootDeviceHints: if the service auto-selected
a raw FC/iSCSI path and it appears in the acceptable list, the code
returns early without ever calling GetPreferredDiskID.

The correct fix is to mark raw FC/iSCSI multipath members as
ineligible at the validator level (next commit).
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@yoavsc0302: This pull request references Jira Issue OCPBUGS-79576, which is invalid:

  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Two commits:

  1. Revert PR OCPBUGS-79576: Prefer multipath disk in ABI disk selection #10091 — The GetPreferredDiskID approach is bypassed by the "already matches" early return in applyRootDeviceHints(): if Phase 1 auto-selects a raw FC/iSCSI path and it appears in the acceptable disk list, the function returns before GetPreferredDiskID is ever called. Confirmed on s390x FC multipath hardware.

  2. Mark raw FC/iSCSI multipath members as ineligible — Raw FC and iSCSI disks that are members of a multipath device are now marked as ineligible at the validator level. Writing to a raw path instead of the multipath device causes installation failure (ENODEV) when multipathd reclaims the disk. By making them ineligible at the source, they are filtered out from all disk selection paths (SaaS, ZTP, ABI), no bypass is possible, and they show as ineligible in the UI with a clear reason.

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)
  • 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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 14, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

Walkthrough

Disk selection logic was refactored: the shared GetPreferredDiskID helper was removed and replaced by local selection logic (direct first-disk indexing or a new local multipath-aware helper). Validation was extended to mark FC/iSCSI disks that are multipath members as not eligible.

Changes

Cohort / File(s) Summary
Disk selection changes
cmd/agentbasedinstaller/host_config.go, internal/controller/controllers/bmh_agent_controller.go, internal/host/hostutil/host_utils.go
Removed exported GetPreferredDiskID. host_config.go now picks acceptableDisks[0].ID directly; controller uses new local getDiskID that prefers DriveTypeMultipath then falls back to first disk.
Multipath-member validation
internal/hardware/validator.go, internal/hardware/validator_test.go
Added diskIsMultipathMember reason and hasMultipathHolder check; FC/iSCSI disks listed as holders of a multipath device are marked not eligible. Tests updated/added to assert this behavior.
Test removals/adjustments
cmd/agentbasedinstaller/host_config_test.go
Removed two tests that asserted multipath-vs-raw-FC selection preference when multiple disks matched WWN hints.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 9 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (9 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: marking raw FC/iSCSI multipath members as ineligible, which is the core objective of the second commit and primary focus of the PR.
Description check ✅ Passed The description follows the template structure, includes a clear summary of both commits with rationale, identifies the change as a bug fix, confirms no tests needed, and completes all required checklist items.
Stable And Deterministic Test Names ✅ Passed All Ginkgo test names in modified test files use static, descriptive strings with no dynamic content, generated identifiers, timestamps, or variable interpolation.
Test Structure And Quality ✅ Passed New and modified test cases follow established patterns with proper structure, assertions, and resource cleanup across both files.
Microshift Test Compatibility ✅ Passed PR does not add new Ginkgo e2e tests; only modifies unit tests for assisted-service backend using mock data with no live cluster interaction.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR modifies unit tests in internal packages, not new Ginkgo e2e tests as required by the check.
Topology-Aware Scheduling Compatibility ✅ Passed PR does not introduce scheduling constraints, pod affinity, node selectors, topology spread constraints, tolerations, or topology-aware scheduling logic. Changes focus on bare metal hardware validation and disk selection during cluster installation.
Ote Binary Stdout Contract ✅ Passed PR modifies only library package code with no process-level functions; all new/modified functions use dependency-injected loggers or return formatted errors stored in data structures.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The pull request modifies only unit tests, not e2e tests. Both modified test files are package-level unit tests within internal packages that test specific functions in isolation using local mocks and assertions. The custom check specifically targets Ginkgo e2e tests, which this PR does not add.

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

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

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

@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 14, 2026
@openshift-ci openshift-ci Bot requested review from celebdor and mlorenzofr April 14, 2026 20:19
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 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.

🧹 Nitpick comments (1)
internal/controller/controllers/bmh_agent_controller.go (1)

1295-1305: Consider adding a guard for empty input slice.

The function assumes disks is non-empty when accessing disks[0].ID on line 1304. While the current call site at line 1282 guards with len(acceptable) > 0, defensive coding would protect against future misuse.

🛡️ Optional: Add defensive check
 func getDiskID(disks []*models.Disk) string {
+	if len(disks) == 0 {
+		return ""
+	}
 	for _, disk := range disks {
 		if strings.EqualFold(string(disk.DriveType), string(models.DriveTypeMultipath)) {
 			return disk.ID
 		}
 	}
 	return disks[0].ID
 }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@internal/controller/controllers/bmh_agent_controller.go` around lines 1295 -
1305, getDiskID assumes disks is non-empty and will panic on disks[0].ID; add a
defensive empty-slice guard at the start of getDiskID (e.g., if len(disks) == 0
{ return "" }) so the function safely returns an empty string when no disks are
provided (alternatively consider changing signature to return (string, error) if
callers need explicit error handling); update any callers or tests if they rely
on a non-empty return.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@internal/controller/controllers/bmh_agent_controller.go`:
- Around line 1295-1305: getDiskID assumes disks is non-empty and will panic on
disks[0].ID; add a defensive empty-slice guard at the start of getDiskID (e.g.,
if len(disks) == 0 { return "" }) so the function safely returns an empty string
when no disks are provided (alternatively consider changing signature to return
(string, error) if callers need explicit error handling); update any callers or
tests if they rely on a non-empty return.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 155b91ad-d759-4f3b-93d7-5cfaa0b0eac7

📥 Commits

Reviewing files that changed from the base of the PR and between a333ea8 and 37496d6.

📒 Files selected for processing (6)
  • cmd/agentbasedinstaller/host_config.go
  • cmd/agentbasedinstaller/host_config_test.go
  • internal/controller/controllers/bmh_agent_controller.go
  • internal/hardware/validator.go
  • internal/hardware/validator_test.go
  • internal/host/hostutil/host_utils.go
💤 Files with no reviewable changes (2)
  • cmd/agentbasedinstaller/host_config_test.go
  • internal/host/hostutil/host_utils.go

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 14, 2026

Codecov Report

❌ Patch coverage is 95.83333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 44.37%. Comparing base (a333ea8) to head (b587c8e).
⚠️ Report is 5 commits behind head on master.

Files with missing lines Patch % Lines
internal/hardware/validator.go 94.11% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10142      +/-   ##
==========================================
+ Coverage   44.29%   44.37%   +0.08%     
==========================================
  Files         415      415              
  Lines       72735    72825      +90     
==========================================
+ Hits        32215    32316     +101     
+ Misses      37606    37596      -10     
+ Partials     2914     2913       -1     
Files with missing lines Coverage Δ
cmd/agentbasedinstaller/host_config.go 43.82% <100.00%> (ø)
...nal/controller/controllers/bmh_agent_controller.go 73.80% <100.00%> (+0.12%) ⬆️
internal/host/hostutil/host_utils.go 57.57% <ø> (+1.21%) ⬆️
internal/hardware/validator.go 80.33% <94.11%> (+0.68%) ⬆️

... and 3 files with indirect coverage changes

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

Raw FC and iSCSI disks that are members of a multipath device are
not eligible for installation. Writing to a raw path instead of the
multipath device causes installation failure (ENODEV) when multipathd
reclaims the disk.

Mark these disks as ineligible at the validator level so they are
excluded from all disk selection paths (SaaS, ZTP, ABI) and show
as ineligible in the UI.
@yoavsc0302 yoavsc0302 force-pushed the OCPBUGS-79576-option-b-with-revert branch from 37496d6 to b587c8e Compare April 15, 2026 06:45
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.

🧹 Nitpick comments (1)
internal/hardware/validator.go (1)

235-240: Trim holder tokens before lookup to avoid edge-case false negatives.

If disk.Holders ever contains spacing ("dm-0, dm-1"), direct map lookup can miss valid multipath holders.

♻️ Proposed hardening
 	holders := strings.Split(disk.Holders, ",")
 	for _, holder := range holders {
+		holder = strings.TrimSpace(holder)
+		if holder == "" {
+			continue
+		}
 		if _, exists := multipathDiskNamesMap[holder]; exists {
 			return fmt.Errorf(diskIsMultipathMember, holder)
 		}
 	}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@internal/hardware/validator.go` around lines 235 - 240, The loop that checks
disk.Holders splits on commas but does not trim whitespace, so lookups on
multipathDiskNamesMap can miss entries like " dm-1"; update the holder handling
inside the loop in validator.go (the loop over holders created by strings.Split
in the function that checks multipath membership) to call
strings.TrimSpace(holder) and skip empty tokens before doing the map lookup; use
the trimmed token for the exists check and the error message
(fmt.Errorf(diskIsMultipathMember, trimmedHolder)).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@internal/hardware/validator.go`:
- Around line 235-240: The loop that checks disk.Holders splits on commas but
does not trim whitespace, so lookups on multipathDiskNamesMap can miss entries
like " dm-1"; update the holder handling inside the loop in validator.go (the
loop over holders created by strings.Split in the function that checks multipath
membership) to call strings.TrimSpace(holder) and skip empty tokens before doing
the map lookup; use the trimmed token for the exists check and the error message
(fmt.Errorf(diskIsMultipathMember, trimmedHolder)).

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 60aa4063-6544-4467-bea9-8520fe6a10d6

📥 Commits

Reviewing files that changed from the base of the PR and between 37496d6 and b587c8e.

📒 Files selected for processing (2)
  • internal/hardware/validator.go
  • internal/hardware/validator_test.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • internal/hardware/validator_test.go

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

openshift-ci Bot commented Apr 15, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avishayt, yoavsc0302

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 [avishayt,yoavsc0302]

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

@yoavsc0302
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 Apr 15, 2026
@adriengentil
Copy link
Copy Markdown
Contributor

/test ?

@adriengentil
Copy link
Copy Markdown
Contributor

/test edge-e2e-oci-assisted-bm-iscsi-4-22
Oracle uses single iscsi disks, let's make sure it's not impacted

@yoavsc0302
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@yoavsc0302: This pull request references Jira Issue OCPBUGS-79576, which is invalid:

  • expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.22.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Apr 15, 2026

This looks consistent with the code that previously existed (for iSCSI) from #6612 (which was later removed by #7192), and adds identical checks for FC.
/lgtm

@zaneb
Copy link
Copy Markdown
Member

zaneb commented Apr 15, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@zaneb: This pull request references Jira Issue OCPBUGS-79576, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

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.

@yoavsc0302
Copy link
Copy Markdown
Contributor Author

/cherrypick release-4.22 release-4.21 release-4.20

Note: auto cherry-pick to release-4.21 and release-4.20 will likely fail because the original fix (#10091) was manually backported to those branches with adapted code, so the revert commit won't match. Commenting anyway for documentation, will prepare manual backports.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@yoavsc0302: once the present PR merges, I will cherry-pick it on top of release-4.22 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.22 release-4.21 release-4.20

Note: auto cherry-pick to release-4.21 and release-4.20 will likely fail because the original fix (#10091) was manually backported to those branches with adapted code, so the revert commit won't match. Commenting anyway for documentation, will prepare manual backports.

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.

@yoavsc0302
Copy link
Copy Markdown
Contributor Author

/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 Apr 15, 2026
@adriengentil
Copy link
Copy Markdown
Contributor

/retest

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 15, 2026

@yoavsc0302: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit da7ffa8 into openshift:master Apr 15, 2026
25 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@yoavsc0302: Jira Issue OCPBUGS-79576: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-79576 has been moved to the MODIFIED state.

Details

In response to this:

Two commits:

  1. Revert PR OCPBUGS-79576: Prefer multipath disk in ABI disk selection #10091 — The GetPreferredDiskID approach is bypassed by the "already matches" early return in applyRootDeviceHints(): if Phase 1 auto-selects a raw FC/iSCSI path and it appears in the acceptable disk list, the function returns before GetPreferredDiskID is ever called. Confirmed on s390x FC multipath hardware.

  2. Mark raw FC/iSCSI multipath members as ineligible — Raw FC and iSCSI disks that are members of a multipath device are now marked as ineligible at the validator level. Writing to a raw path instead of the multipath device causes installation failure (ENODEV) when multipathd reclaims the disk. By making them ineligible at the source, they are filtered out from all disk selection paths (SaaS, ZTP, ABI), no bypass is possible, and they show as ineligible in the UI with a clear reason.

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)
  • 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

Release Notes

  • Bug Fixes

  • Disks that are members of multipath setups (e.g., FC/iSCSI holders) are now correctly detected and marked ineligible for installation.

  • Refactor

  • Disk selection for installation targets made deterministic when multiple matches exist (chooses the first acceptable disk).

  • Removed an unused disk-selection utility and related tests.

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-cherrypick-robot
Copy link
Copy Markdown

@yoavsc0302: new pull request created: #10150

Details

In response to this:

/cherrypick release-4.22 release-4.21 release-4.20

Note: auto cherry-pick to release-4.21 and release-4.20 will likely fail because the original fix (#10091) was manually backported to those branches with adapted code, so the revert commit won't match. Commenting anyway for documentation, will prepare manual backports.

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.

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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