-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS#2892: Added known issue for IBM Cloud VPC #52820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/4710 |
|
@jeffnowicki this is ready for SME review. PTAL. Thank you. |
fdde419 to
a93cb36
Compare
|
@mjpytlak review comments... (not via PR review process... but hopefully these make sense... I sent screenshots and explanation in slack DM to you as well). change 1: change 2: |
a93cb36 to
101d8a6
Compare
Thanks @jeffnowicki. Made sense. PTAL. |
|
@MayXuQQ Ready for QE review. PTAL. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get the cluster region
$oc get machines -n openshift-machine-api
...
set the target to the cluster
$ibmcloud target -g <cluster_ID> -r <cluster_region>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MayXuQQ I'd prefer to simplify your suggestion and state: "Before executing the following command, ensure you are logged into the IBM Cloud account for your cluster and target the correct region for your cluster." I think it's reasonable for the user to know how to log into ibmcloud and target the correct region (no need to give actual commands).
@mjpytlak Please insert the above sentence as follows:
Before executing the following command, ensure you are logged into the IBM Cloud account for your cluster and target the correct region for your cluster. Verify that the internal ALB status is active by running the following command:
f226a52 to
141258f
Compare
|
/label qe-approved |
|
/hold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fail to verify this step now, and what is expected output ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeffnowicki need much change before checking the traffic ? how about add doc to the
https://github.com/openshift/installer/tree/master/docs/user
and simplify the know issue doc ?
141258f to
c641103
Compare
|
/unhold |
|
/lgtm Nice work @mjpytlak |
|
@jeffnowicki: changing LGTM is restricted to collaborators 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 kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just have a few formatting considerations for ya
/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line break might make this easier to parse, and suggest moving the link to the end (as with the previous bulleted item) so users don't misinterpret that link as the end of the bullet.
| * Intermittently, an IBM Cloud VPC cluster might fail to install because some worker machines do not start. Rather, these worker machines remain in the `Provisioned` phase. There is a workaround for this issue. From the host where you performed the initial installation, delete the failed machines and run the installation program again. (link:https://issues.redhat.com/browse/OCPBUGS-1327[*OCPBUGS#1327*]) | |
| * Intermittently, an IBM Cloud VPC cluster might fail to install because some worker machines do not start. Rather, these worker machines remain in the `Provisioned` phase. | |
| + | |
| There is a workaround for this issue. From the host where you performed the initial installation, delete the failed machines and run the installation program again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. Agreed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| + | |
| (link:https://issues.redhat.com/browse/OCPBUGS-1327[*OCPBUGS#1327*]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. All set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does kubeconfig need some formatting? (asking because I don't know 🙂)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed it does; indeed it does. Nice catch.
c641103 to
c7b7893
Compare
Version(s):
4.12
Issue:
This PR addresses ocpbugs#2892.
Link to docs preview:
Known issues (second bulleted issue)
QE review: