OCPBUGS-49969: Removed 4.10 and 4.11 references from MetalLB docs

[dfitzmau]

Version(s):
4.12+

Issue:
OCPBUGS-49969

Link to docs preview:
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/metallb-operator/metallb-upgrading-operator.html

• SME has approved this change (Federico Paolinelli).
• QE has approved this change (Arti Sood).

[openshift-ci-robot]

@dfitzmau: No Jira issue with key OCPBUGS-499969 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

Version(s):
4.12+

Issue:
OCPBUGS-49969

Link to docs preview:

• SME has approved this change.
• QE has approved this change.

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.

[ocpdocs-previewbot]

🤖 Wed Apr 16 08:45:55 - Prow CI generated the docs preview:

https://89609--ocpdocs-pr.netlify.app/
https://89609--ocpdocs-pr.netlify.app/openshift-dedicated/latest/operators/admin/olm-adding-operators-to-cluster.html
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/metallb-operator/metallb-upgrading-operator.html
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/operators/admin/olm-adding-operators-to-cluster.html
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/operators/user/olm-installing-operators-in-namespace.html
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/preparing-for-users.html
https://89609--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/operators/admin/olm-adding-operators-to-cluster.html
https://89609--ocpdocs-pr.netlify.app/openshift-rosa/latest/operators/admin/olm-adding-operators-to-cluster.html

[openshift-ci-robot]

@dfitzmau: This pull request references Jira Issue OCPBUGS-49969, which is invalid:

• expected the bug to target the "4.19.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:

Version(s):
4.12+

Issue:
OCPBUGS-49969

Link to docs preview:

• SME has approved this change.
• QE has approved this change.

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]

@dfitzmau: 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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@dfitzmau: Jira Issue OCPBUGS-49969: All pull requests linked via external trackers have merged:

• openshift/openshift-docs#89609

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

In response to this:

Version(s):
4.12+

Issue:
OCPBUGS-49969

Link to docs preview:
https://89609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/metallb-operator/metallb-upgrading-operator.html

• SME has approved this change (Federico Paolinelli).
• QE has approved this change (Arti Sood).

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.

[dfitzmau]

/cherrypick enterprise-4.19

[dfitzmau]

/cherrypick enterprise-4.18

[dfitzmau]

/cherrypick enterprise-4.17

[dfitzmau]

/cherrypick enterprise-4.16

[dfitzmau]

/cherrypick enterprise-4.15

[dfitzmau]

/cherrypick enterprise-4.14

[dfitzmau]

/cherrypick enterprise-4.13

[dfitzmau]

/cherrypick enterprise-4.12

[openshift-cherrypick-robot]

@dfitzmau: #89609 failed to apply on top of branch "enterprise-4.16":

Applying: OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs
.git/rebase-apply/patch:32: trailing whitespace.
* You used OperatorHub to install the MetalLB Operator. 
.git/rebase-apply/patch:501: trailing whitespace.
If you need to manually control upgrading the MetalLB Operator, set the `installPlanApproval` parameter to `Manual`. 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/olm-installing-from-operatorhub-using-cli.adoc
M	operators/admin/olm-adding-operators-to-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging operators/admin/olm-adding-operators-to-cluster.adoc
CONFLICT (content): Merge conflict in operators/admin/olm-adding-operators-to-cluster.adoc
Removing modules/olm-updating-metallb-operatorgroup.adoc
Auto-merging modules/olm-installing-from-operatorhub-using-cli.adoc
CONFLICT (content): Merge conflict in modules/olm-installing-from-operatorhub-using-cli.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

In response to this:

/cherrypick enterprise-4.16

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.

[openshift-cherrypick-robot]

@dfitzmau: #89609 failed to apply on top of branch "enterprise-4.15":

Applying: OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs
.git/rebase-apply/patch:32: trailing whitespace.
* You used OperatorHub to install the MetalLB Operator. 
.git/rebase-apply/patch:501: trailing whitespace.
If you need to manually control upgrading the MetalLB Operator, set the `installPlanApproval` parameter to `Manual`. 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/olm-installing-from-operatorhub-using-cli.adoc
A	networking/networking_operators/metallb-operator/metallb-upgrading-operator.adoc
M	operators/admin/olm-adding-operators-to-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging operators/admin/olm-adding-operators-to-cluster.adoc
CONFLICT (content): Merge conflict in operators/admin/olm-adding-operators-to-cluster.adoc
Auto-merging networking/metallb/metallb-upgrading-operator.adoc
CONFLICT (content): Merge conflict in networking/metallb/metallb-upgrading-operator.adoc
Removing modules/olm-updating-metallb-operatorgroup.adoc
Auto-merging modules/olm-installing-from-operatorhub-using-cli.adoc
CONFLICT (content): Merge conflict in modules/olm-installing-from-operatorhub-using-cli.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

In response to this:

/cherrypick enterprise-4.15

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.

[openshift-cherrypick-robot]

@dfitzmau: #89609 failed to apply on top of branch "enterprise-4.14":

Applying: OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs
.git/rebase-apply/patch:32: trailing whitespace.
* You used OperatorHub to install the MetalLB Operator. 
.git/rebase-apply/patch:501: trailing whitespace.
If you need to manually control upgrading the MetalLB Operator, set the `installPlanApproval` parameter to `Manual`. 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/olm-installing-from-operatorhub-using-cli.adoc
A	networking/networking_operators/metallb-operator/metallb-upgrading-operator.adoc
M	operators/admin/olm-adding-operators-to-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging operators/admin/olm-adding-operators-to-cluster.adoc
CONFLICT (content): Merge conflict in operators/admin/olm-adding-operators-to-cluster.adoc
Auto-merging networking/metallb/metallb-upgrading-operator.adoc
CONFLICT (content): Merge conflict in networking/metallb/metallb-upgrading-operator.adoc
Removing modules/olm-updating-metallb-operatorgroup.adoc
Auto-merging modules/olm-installing-from-operatorhub-using-cli.adoc
CONFLICT (content): Merge conflict in modules/olm-installing-from-operatorhub-using-cli.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

In response to this:

/cherrypick enterprise-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-sigs/prow repository.

[openshift-cherrypick-robot]

@dfitzmau: new pull request created: #92248

In response to this:

/cherrypick enterprise-4.19

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.

[openshift-cherrypick-robot]

@dfitzmau: new pull request created: #92249

In response to this:

/cherrypick enterprise-4.18

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.

[openshift-cherrypick-robot]

@dfitzmau: #89609 failed to apply on top of branch "enterprise-4.13":

Applying: OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs
.git/rebase-apply/patch:32: trailing whitespace.
* You used OperatorHub to install the MetalLB Operator. 
.git/rebase-apply/patch:501: trailing whitespace.
If you need to manually control upgrading the MetalLB Operator, set the `installPlanApproval` parameter to `Manual`. 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/olm-installing-from-operatorhub-using-cli.adoc
A	networking/networking_operators/metallb-operator/metallb-upgrading-operator.adoc
M	operators/admin/olm-adding-operators-to-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging operators/admin/olm-adding-operators-to-cluster.adoc
CONFLICT (content): Merge conflict in operators/admin/olm-adding-operators-to-cluster.adoc
Auto-merging networking/metallb/metallb-upgrading-operator.adoc
CONFLICT (content): Merge conflict in networking/metallb/metallb-upgrading-operator.adoc
Removing modules/olm-updating-metallb-operatorgroup.adoc
Auto-merging modules/olm-installing-from-operatorhub-using-cli.adoc
CONFLICT (content): Merge conflict in modules/olm-installing-from-operatorhub-using-cli.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

In response to this:

/cherrypick enterprise-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-sigs/prow repository.

[openshift-cherrypick-robot]

@dfitzmau: #89609 failed to apply on top of branch "enterprise-4.12":

Applying: OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs
.git/rebase-apply/patch:32: trailing whitespace.
* You used OperatorHub to install the MetalLB Operator. 
.git/rebase-apply/patch:501: trailing whitespace.
If you need to manually control upgrading the MetalLB Operator, set the `installPlanApproval` parameter to `Manual`. 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/nw-metalLB-basic-upgrade-operator.adoc
M	modules/olm-installing-from-operatorhub-using-cli.adoc
A	networking/networking_operators/metallb-operator/metallb-upgrading-operator.adoc
M	operators/admin/olm-adding-operators-to-cluster.adoc
Falling back to patching base and 3-way merge...
Auto-merging operators/admin/olm-adding-operators-to-cluster.adoc
CONFLICT (content): Merge conflict in operators/admin/olm-adding-operators-to-cluster.adoc
Auto-merging networking/metallb/metallb-upgrading-operator.adoc
CONFLICT (content): Merge conflict in networking/metallb/metallb-upgrading-operator.adoc
Removing modules/olm-updating-metallb-operatorgroup.adoc
Auto-merging modules/olm-installing-from-operatorhub-using-cli.adoc
CONFLICT (content): Merge conflict in modules/olm-installing-from-operatorhub-using-cli.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-web-console.adoc
Removing modules/olm-deleting-metallb-operators-from-a-cluster-using-cli.adoc
Auto-merging modules/nw-metalLB-basic-upgrade-operator.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-499969: Removed 4.10 and 4.11 references from MetalLB docs

In response to this:

/cherrypick enterprise-4.12

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.

[openshift-cherrypick-robot]

@dfitzmau: new pull request created: #92250

In response to this:

/cherrypick enterprise-4.17

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.