Skip to content
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

[Bug]: IPv6 Compatibility Issue for Dashboard Backend Server #3556

Open
1 task done
chaturvedi-kna opened this issue Dec 8, 2024 · 0 comments
Open
1 task done

[Bug]: IPv6 Compatibility Issue for Dashboard Backend Server #3556

chaturvedi-kna opened this issue Dec 8, 2024 · 0 comments
Labels
kind/bug Something isn't working priority/normal An issue with the product; fix when possible untriaged Indicates the newly create issue has not been triaged yet

Comments

@chaturvedi-kna
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Deploy type

Downstream version (eg. OpenShift AI 2.4)

Version

2.13.1

Current Behavior

The ODH Dashboard backend encounters two critical issues when deployed in an IPv6-only environment:

  1. Readiness/Liveness Probe Fails:
    The server binds only to 0.0.0.0 (IPv4), which causes connection failures when the liveness probe attempts to connect to an IPv6 address.

  2. Hostname/IP Validation Failure:
    The backend throws errors due to improper handling of IPv6 addresses in API requests, specifically missing brackets around IPv6 addresses in URLs.

Expected Behavior

  • The backend should bind to an IPv6-compatible address (::) or dynamically detect the appropriate interface.
  • IPv6 addresses in API requests should be enclosed in square brackets ([]) to avoid hostname validation issues.

Steps To Reproduce

  1. Deploy the ODH Dashboard in an IPv6-only OpenShift cluster.
  2. Observe the following error in the Kubernetes event logs:
    Liveness probe failed: dial tcp [fd02:0:0:1::13c]:8080: connect: connection refused
  3. Observe the following error in the backend logs:
    Hostname/IP does not match certificate's altnames: Host: fd02. is not in the cert's altnames

Workaround (if any)

No response

What browsers are you seeing the problem on?

No response

Anything else

No response

@chaturvedi-kna chaturvedi-kna added kind/bug Something isn't working priority/normal An issue with the product; fix when possible untriaged Indicates the newly create issue has not been triaged yet labels Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working priority/normal An issue with the product; fix when possible untriaged Indicates the newly create issue has not been triaged yet
Projects
None yet
Development

No branches or pull requests

1 participant