fix(alliance): fall back Digevo prod endpoint to LATAM West - #990
Merged
Merged
Conversation
NVIDIA discovery still advertises https://prod.DIG.geforcenow.nvidiagrid.net/ for Digevo, but that hostname has no DNS records globally, so region discovery, VPC lookup, and all CloudMatch routing for Digevo accounts failed. Route Digevo to the working regional endpoint https://latam-west.dig.geforcenow.nvidiagrid.net/ (server NPA-DIG-SCL-01, region LATAM West), verified live with serverInfo, session list, session create, and first video frame at 1080p60 H264. The fallback stays within the existing HTTPS nvidiagrid.net trust policy; no protocol or ABI change.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Digevo accounts could not get past provider routing: NVIDIA discovery (\pcs.geforcenow.com/v1/serviceUrls) still advertises \https://prod.DIG.geforcenow.nvidiagrid.net/\, but that hostname has no DNS records globally (NODATA/NXDOMAIN on every resolver tested, including with LATAM EDNS client subnets). Region discovery, VPC lookup, and all CloudMatch session routing for Digevo therefore failed.
This routes Digevo to the working regional endpoint \https://latam-west.dig.geforcenow.nvidiagrid.net/\ (server \NPA-DIG-SCL-01, region LATAM West) whenever discovery returns the stale prod host. The fallback stays within the existing HTTPS
vidiagrid.net\ trust policy; no protocol or ABI change.
Changes
ative/opennow-core/src/gfn.rs: new \effective_provider_url()\ / \provider_streaming_base(); Digevo stale-host fallback applied in discovery normalization, \provider_regions, \�pc_id, and session validation.
ative/opennow-core/src/cloudmatch.rs:
equested_streaming_base()\ uses the effective provider URL.
ative/opennow-core/src/gfn/routing_tests.rs: new test for the fallback mapping and passthrough.
Verification