[OCPBUGS#22683] Remove reference to BM control plane node for OpenStack

[mandre]

The doc explicitly said that BM control plane nodes were supported on OpenStack platform while it's not. QE don't test it either.

We do however support BM compute nodes.

Related to OCPBUGS-22683.

Version(s):
All supported versions

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@mandre: Jira Issue OCPBUGS-22683 is in a security level that is not in the allowed security levels for this repo.
Allowed security levels for this repo are:

• Red Hat Employee
• default

In response to this:

The doc explicitly said that BM control plane nodes were supported on OpenStack platform while it's not. QE don't test it either.

We do however support BM compute nodes.

Related to OCPBUGS-22683.

Version(s):
All supported versions

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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 Aug 27 11:13:25 - Prow CI generated the docs preview:

https://71609--ocpdocs-pr.netlify.app/
https://71609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_openstack/installing-openstack-installer-custom.html
https://71609--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_openstack/installing-openstack-user.html

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

[maxwelldb]

/remove-lifecycle rotten

[maxwelldb]

/reopen

[openshift-ci]

@maxwelldb: Reopened this PR.

In response to this:

/reopen

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-ci]

@mandre: 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.

[imatza-rh]

/lgtm

[maxwelldb]

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

[openshift-cherrypick-robot]

@maxwelldb: once the present PR merges, I will cherry-pick it on top of enterprise-4.12, enterprise-4.14, enterprise-4.15, enterprise-4.16, enterprise-4.17, enterprise-4.18, enterprise-4.19, enterprise-4.20 in new PRs and assign them to you.

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: #71609 failed to apply on top of branch "enterprise-4.14":

Applying: Remove reference to BM control plane node for OpenStack
error: patch failed: modules/installation-osp-deploying-bare-metal-machines.adoc:14
error: modules/installation-osp-deploying-bare-metal-machines.adoc: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
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"
Using index info to reconstruct a base tree...
M	modules/installation-osp-deploying-bare-metal-machines.adoc
Patch failed at 0001 Remove reference to BM control plane node for OpenStack

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98085

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98086

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98087

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98088

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98089

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: new pull request created: #98090

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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]

@maxwelldb: #71609 failed to apply on top of branch "enterprise-4.12":

Applying: Remove reference to BM control plane node for OpenStack
error: patch failed: modules/installation-osp-deploying-bare-metal-machines.adoc:14
error: modules/installation-osp-deploying-bare-metal-machines.adoc: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
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"
Using index info to reconstruct a base tree...
M	modules/installation-osp-deploying-bare-metal-machines.adoc
Patch failed at 0001 Remove reference to BM control plane node for OpenStack

In response to this:

/cherry-pick enterprise-4.12
/cherry-pick enterprise-4.14
/cherry-pick enterprise-4.15
/cherry-pick enterprise-4.16
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20

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.