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

Update Rancher test script to skip sig-network test #6377

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jainpulkit22
Copy link
Contributor

@jainpulkit22 jainpulkit22 commented May 28, 2024

Update Rancher test script to skip sig-network test while running conformance and network-policy tests on a rancher cluster.
Fixes #6426.

@jainpulkit22
Copy link
Contributor Author

/test-rancher-e2e

@jainpulkit22
Copy link
Contributor Author

/test-rancher-e2e

@jainpulkit22
Copy link
Contributor Author

/test-rancher-e2e

@jainpulkit22
Copy link
Contributor Author

/test-rancher-e2e

1 similar comment
@jainpulkit22
Copy link
Contributor Author

/test-rancher-e2e

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22
Copy link
Contributor Author

/test-rancher-networkpolicy

@rajnkamr
Copy link
Contributor

/test-rancher-conformance

@rajnkamr
Copy link
Contributor

/test-rancher-networkpolicy

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

1 similar comment
@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22
Copy link
Contributor Author

/test-rancher-networkpolicy

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@rajnkamr
Copy link
Contributor

rajnkamr commented Jun 3, 2024

/test-rancher-networkpolicy

@jainpulkit22 jainpulkit22 marked this pull request as ready for review June 3, 2024 06:45
@jainpulkit22 jainpulkit22 changed the title [WIP]Update Rancher test script Update Rancher test script to skip sig-network test Jun 3, 2024
@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22 jainpulkit22 force-pushed the rancher-script branch 2 times, most recently from fc151cd to 4c54e7f Compare June 4, 2024 08:53
@rajnkamr rajnkamr added area/test/jenkins Issue about jenkins setup code area/test/infra Issues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers labels Jun 4, 2024
@@ -12,7 +12,7 @@ Kubernetes networking based on Open vSwitch

## Requirements

Kubernetes: `>= 1.16.0-0`
Kubernetes: `>= 1.19.0-0`
Copy link
Contributor

@luolanzone luolanzone Jun 4, 2024

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

Copy link
Contributor Author

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@luolanzone done PR: #6397

Copy link
Contributor

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

@@ -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\]"
Copy link
Contributor

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?

Copy link
Contributor Author

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

Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Skipping the entire test suite just because one case doesn't make sense.
  2. There is no detail or reference why the test failed so it can't justify why it should be skipped.
  3. 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.

Copy link
Contributor Author

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.

Copy link
Contributor

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.

NETWORKPOLICY_SKIP="NetworkPolicyLegacy|should allow egress access to server in CIDR block|should enforce except clause while egress access to server in CIDR block"

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

1 similar comment
@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

@jainpulkit22 jainpulkit22 marked this pull request as ready for review June 11, 2024 07:16
@jainpulkit22 jainpulkit22 marked this pull request as draft June 18, 2024 06:44
@jainpulkit22
Copy link
Contributor Author

/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
Copy link
Contributor

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.

@jainpulkit22
Copy link
Contributor Author

/test-rancher-conformance

Signed-off-by: Pulkit Jain <pulkit.jain@broadcom.com>
@jainpulkit22 jainpulkit22 marked this pull request as ready for review August 8, 2024 06:40
@jainpulkit22 jainpulkit22 marked this pull request as draft August 8, 2024 06:40
Copy link
Contributor

github-actions bot commented Nov 7, 2024

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 7, 2024
@rajnkamr rajnkamr removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test/infra Issues or PRs related to test infrastructure (Jenkins configuration, Ansible playbook, Kind wrappers area/test/jenkins Issue about jenkins setup code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[sig-network] conformance test failing on Rancher testbed
5 participants