[release-4.14] OCPBUGS-27325: Suggest workload partitioning annotation in the namespace

[openshift-cherrypick-robot]

This is an automated cherry-pick of #537

/assign suleymanakbas91

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27095 has been cloned as Jira Issue OCPBUGS-27325. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-27325: Suggest workload partitioning annotation in the namespace

In response to this:

This is an automated cherry-pick of #537

/assign suleymanakbas91

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-27325, which is invalid:

• expected dependent Jira Issue OCPBUGS-27095 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
• expected dependent Jira Issue OCPBUGS-27095 to target a version in 4.15.0, but it targets "4.16.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.

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

In response to this:

This is an automated cherry-pick of #537

/assign suleymanakbas91

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]

/jira refresh

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-27325, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-27219 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-27219 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

Requesting review from QA contact:
/cc @radeore

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.

[jakobmoellerdev]

/lgtm

[suleymanakbas91]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev, openshift-cherrypick-robot, suleymanakbas91

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

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

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27325: All pull requests linked via external trackers have merged:

• openshift/lvm-operator#541

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

In response to this:

This is an automated cherry-pick of #537

/assign suleymanakbas91

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]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@suleymanakbas91: #541 failed to apply on top of branch "release-4.13":

Applying: fix: suggest workload partitioning annotation in the namespace
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
CONFLICT (content): Merge conflict in 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 fix: suggest workload partitioning annotation in the namespace
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:

/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.