Repository navigation
fix(reproducer): enable IPv6 forwarding for network routing - #4226
Conversation
|
Hi @pderenda. Thanks for your PR. I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. 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-sigs/prow repository. |
PR Summary by QodoEnable IPv6 forwarding during reproducer network setup
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 53m 23s |
b4ea10c to
37070e9
Compare
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 55m 05s |
|
/ok-to-test |
IPv6 forwarding and Router Advertisement acceptance were not properly configured during premetal provisioning, causing failures in IPv6-enabled scenarios when OCP VMs on IPv6 networks become unreachable with 'no route to host' errors. This change enables: - IPv6 forwarding on all interfaces (net.ipv6.conf.all.forwarding) - IPv6 Router Advertisement acceptance on all interfaces (accept_ra=2) - IPv6 Router Advertisement acceptance on new interfaces (default.accept_ra=2) Signed-off-by: PDerenda <pderenda@redhat.com>
37070e9 to
1479332
Compare
|
Build succeeded (check pipeline). ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 19m 54s |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evallesp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f09c64d
into
openstack-k8s-operators:main
IPv6 forwarding was not enabled during premetal provisioning, causing failures in IPv6-enabled scenarios when OCP VMs on IPv6 networks become unreachable with 'no route to host' errors.