OCPBUGS-23156: Rebase lvms registry.access.redhat.com lvms4 lvms operator bundle v4.14.1-4

[jakobmoellerdev]

Which issue(s) this PR addresses:
Rebases on top of lvms 4.14.1 which contains the latest CSI sidecars for OCP 4.14

EDIT: Moved to OCPBUGS for smooth backport

[openshift-ci-robot]

@jakobmoellerdev: This pull request references USHIFT-1782 which is a valid jira issue.

In response to this:

Which issue(s) this PR addresses:
Rebases on top of lvms 4.14.1 which contains the latest CSI sidecars for OCP 4.14

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/test-infra repository.

[jakobmoellerdev]

/cherrypick release-4.14

[openshift-cherrypick-robot]

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

In response to this:

/cherrypick release-4.14

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/test-infra repository.

[openshift-ci-robot]

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-23156, which is invalid:

• expected the bug to target the "4.15.0" version, but no target version was set

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.

In response to this:

Which issue(s) this PR addresses:
Rebases on top of lvms 4.14.1 which contains the latest CSI sidecars for OCP 4.14

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/test-infra repository.

[jakobmoellerdev]

/jira refresh

[openshift-ci-robot]

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-23156, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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 kubernetes/test-infra repository.

[jakobmoellerdev]

/cc @copejon

[ggiguash]

/approve

[openshift-ci]

@jakobmoellerdev: 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/microshift-metal-cache	4b2af30	link	true	/test microshift-metal-cache

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[copejon]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash, jakobmoellerdev

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [copejon,ggiguash]

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]

@jakobmoellerdev: Jira Issue OCPBUGS-23156: All pull requests linked via external trackers have merged:

• openshift/microshift#2598

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

In response to this:

Which issue(s) this PR addresses:
Rebases on top of lvms 4.14.1 which contains the latest CSI sidecars for OCP 4.14

EDIT: Moved to OCPBUGS for smooth backport

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/test-infra repository.

[openshift-cherrypick-robot]

@jakobmoellerdev: #2598 failed to apply on top of branch "release-4.14":

Applying: update last_lvms_rebase.sh
Using index info to reconstruct a base tree...
M	scripts/auto-rebase/last_lvms_rebase.sh
Falling back to patching base and 3-way merge...
Auto-merging scripts/auto-rebase/last_lvms_rebase.sh
CONFLICT (content): Merge conflict in scripts/auto-rebase/last_lvms_rebase.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 update last_lvms_rebase.sh
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.14

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/test-infra repository.

[jakobmoellerdev]

/cherrypick release-4.14

[openshift-cherrypick-robot]

@jakobmoellerdev: #2598 failed to apply on top of branch "release-4.14":

Applying: update last_lvms_rebase.sh
Using index info to reconstruct a base tree...
M	scripts/auto-rebase/last_lvms_rebase.sh
Falling back to patching base and 3-way merge...
Auto-merging scripts/auto-rebase/last_lvms_rebase.sh
CONFLICT (content): Merge conflict in scripts/auto-rebase/last_lvms_rebase.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 update last_lvms_rebase.sh
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.14

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/test-infra repository.