-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Adding IPv6 Troubleshooting guide #3088
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
|
Hi @DirectedSoul1. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
|
/uncc @jstuever |
|
|
||
| Below are some precautions we should follow before even attempting the OCP4.3 Ipv6 deployments. | ||
|
|
||
| * [Ipv4-BM-IPI](https://github.com/openshift-kni/baremetal-deploy/blob/master/install-steps.md#preparing-the-provision-node-for-openshift-install) has some pre-requisites which will be applied fpr ipv6 deployments as well. |
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 think it's a bad idea to link out to a GitHub repo not associated with the product.
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.
👍
If there's something specific for baremetal IPI and IPv6, we do have docs in this repo for that (/docs/user/metal). Ideally baremetal-deploy docs that are generally relevant should be added there.
| * Worker/Provisioning node | ||
| * 3 Master nodes. | ||
|
|
||
| Before starting the installation, we need to set up a DNSmasq conf file which will assign IPv6 IP's to all the nodes on `eno3` interface.A sample file is provided below. |
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.
Going fwd there be dragons ... We are pushing lab architecture assumptions on to everyone. This will immediately put us in contention with customer standards.
Added suggested changes.
|
I think this needs to be in docs/dev or docs/user/baremetal . |
…6.md Moving it to a new path.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Moving it to above suggested path(/docs/user/metal) . |
| @@ -0,0 +1,277 @@ | |||
| # IPv6 Disconnected Install Troubleshooting | |||
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.
docs/user/metal/Troubleshooting_Ipv6.md -> docs/user/metal/troubleshooting_ipv6.md
It has content like
## Create a Disconnected Registry
# BootstrapVM cannot download RHCOS image
## Bootstrap VM cannot boot up my nodes
... and more
which talk about general troubleshooting of baremetal ipi and don't seem to be related to ipv6. So i think we should split these into generic and special ipv6 files.
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
stbenjam
left a comment
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.
Looks like feedback is still unaddressed - file needs renaming for one (docs/user/metal/Troubleshooting_Ipv6.md -> docs/user/metal/troubleshooting_ipv6.md). A lot of this is specific to development environments or is general troubleshooting not specific to IPv6. I also think a lot of this could go to baremetal-deploy repo's docs.
Do you plan to revisit this? It's about to get closed.
|
|
||
| * [Ipv4-BM-IPI](https://github.com/openshift-kni/baremetal-deploy/blob/master/install-steps.md#preparing-the-provision-node-for-openshift-install) has some pre-requisites which will be applied fpr ipv6 deployments as well. | ||
|
|
||
| ### The architecture for IPv6 Disconnected Install(Nodes can vary as per requirements) |
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.
These seem specific to a development/testing environment. I don't think I'd want these documented here
|
|
||
| Below are some precautions we should follow before even attempting the OCP4 Ipv6 deployments. | ||
|
|
||
| * [Ipv4-BM-IPI](https://github.com/openshift-kni/baremetal-deploy/blob/master/install-steps.md#preparing-the-provision-node-for-openshift-install) has some pre-requisites which will be applied fpr ipv6 deployments as well. |
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 is stale
This was opened before we had all the docs we have in the baremetal-deploy repo. Since this was PR'ed, a lot of changes have been put in place. In fact, we are in the process of updating the troubleshooting docs even further in the baremetal-deploy repo. |
|
/close |
|
@stbenjam: Closed this PR. 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/test-infra repository. |
This doc needs a few additional steps, for now, I have added to the best of my knowledge.