-
Notifications
You must be signed in to change notification settings - Fork 90
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
[OCPBUGS-16644] Fix nmstate-console-plugin for Single-Stack IPv6 clusters #1200
Conversation
Hi @orenc1. Thanks for your PR. I'm waiting for a nmstate 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. 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. |
hi @qinqon , |
@orenc1: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
@@ -16,7 +16,7 @@ data: | |||
default_type application/octet-stream; | |||
keepalive_timeout 65; | |||
server { | |||
listen 9443 ssl; | |||
listen [::]:{{ .PluginPort }} ipv6only=off ssl; |
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.
Do this work for ipv4 single stack ?
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.
yes, verified this also with IPv6 single stack and IPv4 single stack
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.
@qinqon , i verified it works also on a Dual-Stack IPv4+IPv6 cluster:
$ oc get network cluster -o json | jq .status
{
"clusterNetwork": [
{
"cidr": "10.128.0.0/14",
"hostPrefix": 23
},
{
"cidr": "fd02::/48",
"hostPrefix": 64
}
],
"clusterNetworkMTU": 1400,
"networkType": "OVNKubernetes",
"serviceNetwork": [
"172.30.0.0/16",
"fd03::/112"
]
}
from the nmstate-console-plugin pod logs:
::ffff:10.128.0.137 - - [26/Jul/2023:14:57:50 +0000] "GET /plugin-manifest.json HTTP/1.1" 200 3269 "https://console-openshift-console.apps.<REDACTED>/k8s/ns/openshift-nmstate/pods/nmstate-console-plugin-5d6ff7f8bd-stqf9/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0"
/ok-to-test |
…ters When a single-stack IPv6 cluster is being used, the nginx server isn't listening on IPv6 requests, just IPv4. Changing the nginx configuration listen directive to '[::]:9443 ipv6only=off ssl' will accept connections both for IPv6 and IPv4. Also, parametrize the service port. Signed-off-by: Oren Cohen <ocohen@redhat.com>
6f5ce1d
to
46506da
Compare
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: phoracek The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…ters (nmstate#1200) When a single-stack IPv6 cluster is being used, the nginx server isn't listening on IPv6 requests, just IPv4. Changing the nginx configuration listen directive to '[::]:9443 ipv6only=off ssl' will accept connections both for IPv6 and IPv4. Also, parametrize the service port. Signed-off-by: Oren Cohen <ocohen@redhat.com>
Is this a BUG FIX or a FEATURE ?:
/kind bug
What this PR does / why we need it:
When a single-stack IPv6 cluster is being used, the nginx server isn't listening on IPv6 requests, just IPv4. Changing the nginx configuration
listen
directive to[::]:9443 ipv6only=off ssl
will accept connections both for IPv6 and IPv4. Also, parametrize the service port.Special notes for your reviewer:
Release note: