[release-4.15] OCPBUGS-30347: chore: update feature annotations for lvms

[jakobmoellerdev]

No description provided.

[openshift-ci-robot]

@jakobmoellerdev: This pull request explicitly references no jira issue.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev

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 [jakobmoellerdev]

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

[suleymanakbas91]

/lgtm

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.77%. Comparing base (81fdbf2) to head (284d63f).

Additional details and impacted files

@@              Coverage Diff              @@
##           release-4.15     #586   +/-   ##
=============================================
  Coverage         81.77%   81.77%           
=============================================
  Files                24       24           
  Lines              1838     1838           
=============================================
  Hits               1503     1503           
  Misses              226      226           
  Partials            109      109           

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-30346 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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:

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.

[suleymanakbas91]

/lgtm

[jakobmoellerdev]

/override ci/prow/lvm-operator-e2e-aws-sno

[openshift-ci]

@jakobmoellerdev: Overrode contexts on behalf of jakobmoellerdev: ci/prow/lvm-operator-e2e-aws-sno

Details

In response to this:

/override ci/prow/lvm-operator-e2e-aws-sno

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]

@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/lvm-operator-e2e-aws-sno	284d63f	link	true	/test lvm-operator-e2e-aws-sno

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

[jakobmoellerdev]

/jira refresh

[openshift-ci-robot]

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

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-30346 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-30346 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @radeore

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.

[openshift-ci-robot]

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

• openshift/lvm-operator#586

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

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[jakobmoellerdev]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@jakobmoellerdev: new pull request created: #598

Details

In response to this:

/cherry-pick 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]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@jakobmoellerdev: #586 failed to apply on top of branch "release-4.13":

Applying: chore: update feature annotations for lvms
Using index info to reconstruct a base tree...
M	bundle/manifests/lvms-operator.clusterserviceversion.yaml
M	config/manifests/bases/clusterserviceversion.yaml.in
M	config/manifests/bases/lvms-operator.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manifests/bases/lvms-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in config/manifests/bases/lvms-operator.clusterserviceversion.yaml
Auto-merging config/manifests/bases/clusterserviceversion.yaml.in
CONFLICT (content): Merge conflict in config/manifests/bases/clusterserviceversion.yaml.in
Auto-merging bundle/manifests/lvms-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: update feature annotations for lvms
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".

Details

In response to this:

/cherry-pick release-4.13

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.