HCIDOCS-470: Update IPI installer docs#81595
Conversation
|
@johnwilkins: An error was encountered searching for bug OCPBUGS-36900 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
@racedo Can I get a QE review on this? |
|
@johnwilkins: An error was encountered searching for bug OCPBUGS-36900 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
@johnwilkins: An error was encountered searching for bug OCPBUGS-36900 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
51282b3 to
9b52b8f
Compare
|
@johnwilkins: An error was encountered searching for bug OCPBUGS-36900 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
@johnwilkins: An error was encountered searching for bug OCPBUGS-36900 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
@johnwilkins: An error was encountered searching for bug HCIDOCS-470 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn 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. |
|
/label peer-review-needed |
|
/label peer-review-in-progress |
xenolinux
left a comment
There was a problem hiding this comment.
LGTM
A tiny nit to replace ' with double quotes "
/remove-label peer-review-needed
/remove-label peer-review-in-progress
/label peer-review-done
70c9c64 to
d05d06d
Compare
|
/label merge-review-needed |
|
@johnwilkins: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
adellape
left a comment
There was a problem hiding this comment.
Couple nits, but not blocking merge.
| |Redfish virtual media| `redfish-virtualmedia://<server_kvm_ip>/redfish/v1/Systems/<serial_number>` | ||
| |==== | ||
|
|
||
| To enable Redfish virtual media for Cisco UCS UCSX-210C-M6 hardware, use `redfish-virtualmedia://` in the `address` setting. The following example demonstrates using Redfish virtual media within the `install-config.yaml` file. |
There was a problem hiding this comment.
Colon since it a "the following example" lead-in?
| To enable Redfish virtual media for Cisco UCS UCSX-210C-M6 hardware, use `redfish-virtualmedia://` in the `address` setting. The following example demonstrates using Redfish virtual media within the `install-config.yaml` file. | |
| To enable Redfish virtual media for Cisco UCS UCSX-210C-M6 hardware, use `redfish-virtualmedia://` in the `address` setting. The following example demonstrates using Redfish virtual media within the `install-config.yaml` file. |
Maybe throughout the PR, too, for any sentence leading into the block/example it's describing?
| baremetal: | ||
| hosts: | ||
| - name: <hostname> | ||
| role: <master | worker> |
There was a problem hiding this comment.
While personally I, too, like the | usage, technically non-standard to guidelines and should probably be just something like:
| role: <master | worker> | |
| role: <type> |
with a callout listing the valid values. I see there are a few other IPI-related instances in other modules, too, tho. Not blocking merge.
|
@adellape: cannot checkout DetailsIn 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 kubernetes-sigs/prow repository. |
|
@adellape: cannot checkout DetailsIn 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 kubernetes-sigs/prow repository. |
|
@adellape: cannot checkout DetailsIn 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 kubernetes-sigs/prow repository. |
|
Lol typos... |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.15 |
|
@adellape: new pull request created: #82410 DetailsIn 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 kubernetes-sigs/prow repository. |
|
@adellape: new pull request created: #82411 DetailsIn 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 kubernetes-sigs/prow repository. |
|
@adellape: #81595 failed to apply on top of branch "enterprise-4.15": DetailsIn 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 kubernetes-sigs/prow repository. |
|
@johnwilkins 4.15 auto-cherrypick failed / will need a manual pick PR. |
Added Cisco firmware requirements.
Fixes: OCPBUGS-36900
See https://issues.redhat.com/browse/HCIDOCS-470 for additional details.
Preview URL: https://81595--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#bmc-addressing-for-cisco-cimc_ipi-install-installation-workflow
https://81595--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_bare_metal_ipi/ipi-install-prerequisites.html#ipi-install-firmware-requirements-for-installing-with-virtual-media_ipi-install-prerequisites
For release(s): 4.15-4.17
QE Review:
Signed-off-by: jowilkin@redhat.com