Add xfail for gcp not supported default geo#807
Merged
azgabur merged 1 commit intoKuadrant:mainfrom Oct 31, 2025
Merged
Conversation
Signed-off-by: Alex Zgabur <azgabur@redhat.com>
averevki
approved these changes
Oct 31, 2025
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.
Test
testsuite/tests/multicluster/load_balanced/test_change_default_geo.pyis failing with gcp provider but this is expected as gcp does not have support for default geo zone.Verification
Set up multicluster config. Then run following make command while setting
provider_secretto aws, gcp and azure. Do not forget about setting correctdns.geo_codefor each providerFor gcp is should XFAIL, rest should PASS.
Or just eye review.