-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
CFE-853: e2e test case for DNSNameResolver and EgressFirewall integration #28683
Conversation
@bharath-b-rh: This pull request references CFE-853 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
Job Failure Risk Analysis for sha: e45eced
|
test/extended/testdata/egress-firewall/ovnk-egressfirewall-wildcard-test.yaml
Outdated
Show resolved
Hide resolved
test/extended/testdata/egress-firewall/ovnk-egressfirewall-wildcard-test.yaml
Outdated
Show resolved
Hide resolved
Job Failure Risk Analysis for sha: eea9b02
|
/retest |
Job Failure Risk Analysis for sha: e0d9b06
|
/retest |
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.
some nits
791f5f5
to
e5cebf5
Compare
/retest-required |
Job Failure Risk Analysis for sha: b03d1c5
|
/retest |
Job Failure Risk Analysis for sha: 462231d
|
/test verify |
1 similar comment
/test verify |
}) | ||
}, | ||
) | ||
|
||
// When OVNKubernetes subnet and coredns-ocp-dnsnameresolver plugins are enabled. |
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.
Instead of checking whether the cluster is techpreview you should create featuregate specific tests:
https://github.com/openshift/api?tab=readme-ov-file#defining-featuregate-e2e-tests
Example: #28719
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.
I am thinking we will make a whole new context in the next dev cycle following all instructions ^, but we wanted 1 simple test in the existing context before we even merge tech preview feature. Hopefully that makes sense
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.
thanks for the link btw!
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.
not sure if this helps, but some existing tests actually were an example for this one
origin/test/extended/builds/volumes.go
Lines 161 to 163 in 75f2c02
if !exutil.IsTechPreviewNoUpgrade(oc) { | |
g.Skip("the test is not expected to work within Tech Preview disabled clusters") | |
} |
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.
The approach of testing featuregates is fairly new as far as I know. I think it is better than checking for techpreview because it doesn't require any followup work. It should be really easy to test whether it works in the existing g.It
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.
suggestion incorporated. New Describe
block added with OCPFeatureGate
tag.
Job Failure Risk Analysis for sha: 215dccb
|
/test e2e-gcp-ovn-upgrade |
/test e2e-gcp-csi |
To do the test run here we need to wait for the last approved pr openshift/cluster-network-operator#2131 to be included to the |
/test e2e-agnostic-ovn-cmd |
/test ? |
@kyrtapz: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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-sigs/prow repository. |
/test e2e-gcp-ovn-techpreview |
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
/acknowledge-critical-fixes-only |
/label acknowledge-critical-fixes-only |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bharath-b-rh, dgoodwin, npinaeva, trozet 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 |
/test e2e-aws-ovn-serial |
@bharath-b-rh: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Job Failure Risk Analysis for sha: 09375ea
|
/test e2e-aws-ovn-serial |
8cca3af
into
openshift:master
[ART PR BUILD NOTIFIER] This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202405180141.p0.g8cca3af.assembly.stream.el9 for distgit openshift-enterprise-tests. |
e2e test case covering integration of CoreDNS and EgressFirewall as proposed in the enhancement