-
Notifications
You must be signed in to change notification settings - Fork 370
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
Update Rancher test script to skip sig-network test #6377
base: main
Are you sure you want to change the base?
Conversation
/test-rancher-e2e |
c78261c
to
85d1fc5
Compare
/test-rancher-e2e |
85d1fc5
to
04d9d13
Compare
/test-rancher-e2e |
04d9d13
to
c9232cb
Compare
/test-rancher-e2e |
1 similar comment
/test-rancher-e2e |
/test-rancher-conformance |
/test-rancher-networkpolicy |
/test-rancher-conformance |
/test-rancher-networkpolicy |
c9232cb
to
cd97439
Compare
/test-rancher-conformance |
1 similar comment
/test-rancher-conformance |
/test-rancher-networkpolicy |
cd97439
to
a8248fd
Compare
/test-rancher-conformance |
/test-rancher-networkpolicy |
a8248fd
to
48a01dc
Compare
48a01dc
to
13418c3
Compare
/test-rancher-conformance |
fc151cd
to
4c54e7f
Compare
build/charts/antrea/README.md
Outdated
@@ -12,7 +12,7 @@ Kubernetes networking based on Open vSwitch | |||
|
|||
## Requirements | |||
|
|||
Kubernetes: `>= 1.16.0-0` | |||
Kubernetes: `>= 1.19.0-0` |
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.
Hi @jainpulkit22 can you submit a seperate PR for this version update? we need to backport both here #6396
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.
sure I can, I added it here because verify docs check were failing
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.
@luolanzone done PR: #6397
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.
@jainpulkit22 , the changes are still visible in this PR as in #6397
ci/run-k8s-e2e-tests.sh
Outdated
@@ -138,6 +140,11 @@ case $key in | |||
SYSTEMD_LOGS_IMAGE="$2" | |||
shift 2 | |||
;; | |||
--rancher-testbed) | |||
RANCHER=true | |||
DEFAULT_E2E_CONFORMANCE_SKIP="${DEFAULT_E2E_CONFORMANCE_SKIP}|\[sig-network\]" |
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.
May I know the background info of this PR? Why we skip sig-network in rancher test?
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.
sig-network test is not supported in the current testing version of rancher
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.
Could you be more specific about "not supported"? Which tests fail? Due to test itself, rancher, or antrea issue? There should an issue with details first to justify the PR and to follow up.
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.
Sure, i will create an issue for the same.
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.
@jainpulkit22 I saw you mentioned [sig-network] Ingress API should support creating Ingress API operations [Conformance]
was not supported for the Rancher cluster. If so, we can only skip this test case, not the entire sig-network test suite.
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.
- Skipping the entire test suite just because one case doesn't make sense.
- There is no detail or reference why the test failed so it can't justify why it should be skipped.
- Even if the test should be skipped, the current way complicates the script unnecessarily, it should just parameterize the skipped test when invoking the script, instead of customiing the script for rancher.
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.
okay will update the code, and add more logs to the issue as well.
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.
Using [sig-network]
will cause all tests with this label to be skipped. You can refer to our configuration in the NETWORKPOLICY_SKIP
to skip individual test case.
Line 50 in 683a72f
NETWORKPOLICY_SKIP="NetworkPolicyLegacy|should allow egress access to server in CIDR block|should enforce except clause while egress access to server in CIDR block" |
4c54e7f
to
a54e210
Compare
/test-rancher-conformance |
1 similar comment
/test-rancher-conformance |
a54e210
to
9a0b722
Compare
/test-rancher-conformance |
9a0b722
to
2e2371b
Compare
/test-rancher-conformance |
2e2371b
to
17ba3b5
Compare
/test-rancher-conformance |
17ba3b5
to
7d0d723
Compare
7d0d723
to
3cd4f99
Compare
/test-rancher-conformance |
@@ -236,9 +238,9 @@ function run_conformance { | |||
|
|||
set +e | |||
if [[ "$TESTCASE" =~ "conformance" ]]; then | |||
${WORKSPACE}/ci/run-k8s-e2e-tests.sh --e2e-conformance --log-mode $MODE --image-pull-policy ${IMAGE_PULL_POLICY} --kubernetes-version "auto" > ${WORKSPACE}/test-result.log | |||
${WORKSPACE}/ci/run-k8s-e2e-tests.sh --e2e-conformance --log-mode $MODE --image-pull-policy ${IMAGE_PULL_POLICY} --kubernetes-version "auto" --rancher-testbed > ${WORKSPACE}/test-result.log |
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 we have a log rotation policy for this testbed ?, log rotation policy is a good practice to manage the growth of log files and to ensure that you have a consistent and manageable logging strategy for test-result.log. Log rotation typically involves periodically archiving old log files and deleting them after a certain period or when they reach a certain size, to prevent disk space from being exhausted.
3cd4f99
to
fc4ea11
Compare
/test-rancher-conformance |
Signed-off-by: Pulkit Jain <[email protected]>
fc4ea11
to
35f3fbb
Compare
This PR is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days. You can add a label "lifecycle/frozen" to skip stale checking. |
Update Rancher test script to skip sig-network test while running conformance and network-policy tests on a rancher cluster.
Fixes #6426.