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

OCPBUGS-41587: E2E: Adjust performance_update suite for hypershift #1157

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SargunNarula
Copy link
Contributor

  • Updated tests to skip MCP resource verification on Hypershift, where MCP concept does not apply.
  • Profile applying is made consistent
  • Removed deprecated API client.
  • Added test suite run in makefile

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 4, 2024

@SargunNarula: This pull request references CNF-13487 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.18.0" version, but no target version was set.

In response to this:

  • Updated tests to skip MCP resource verification on Hypershift, where MCP concept does not apply.
  • Profile applying is made consistent
  • Removed deprecated API client.
  • Added test suite run in makefile

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 4, 2024
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 4, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 4, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 4, 2024
@SargunNarula SargunNarula changed the title WIP CNF-13487: Adjust performance_update suite for hypershift CNF-13487: Adjust performance_update suite for hypershift Sep 10, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 10, 2024
@SargunNarula SargunNarula changed the title CNF-13487: Adjust performance_update suite for hypershift OCPBUGS-41587: E2E: Adjust performance_update suite for hypershift Sep 10, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 10, 2024
@openshift-ci-robot
Copy link
Contributor

@SargunNarula: This pull request references Jira Issue OCPBUGS-41587, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gsr-shanks

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

  • Updated tests to skip MCP resource verification on Hypershift, where MCP concept does not apply.
  • Profile applying is made consistent
  • Removed deprecated API client.
  • Added test suite run in makefile

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.

Makefile Outdated
@@ -274,7 +274,7 @@ pao-functests-mixedcpus: $(BINDATA)
pao-functests-hypershift: $(BINDATA)
@echo "Cluster Version"
hack/show-cluster-version.sh
hack/run-test.sh -t "./test/e2e/performanceprofile/functests/0_config ./test/e2e/performanceprofile/functests/1_performance ./test/e2e/performanceprofile/functests/3_performance_status ./test/e2e/performanceprofile/functests/6_mustgather_testing" -p "-vv --label-filter="!openshift" -r --fail-fast --flake-attempts=2 --timeout=2h --junit-report=report.xml" -m "Running Functional Tests over Hypershift"
hack/run-test.sh -t "./test/e2e/performanceprofile/functests/0_config ./test/e2e/performanceprofile/functests/1_performance ./test/e2e/performanceprofile/functests/2_performance_update ./test/e2e/performanceprofile/functests/3_performance_status ./test/e2e/performanceprofile/functests/6_mustgather_testing" -p "-vv --label-filter="!openshift" -r --fail-fast --flake-attempts=2 --timeout=2h --junit-report=report.xml" -m "Running Functional Tests over Hypershift"
Copy link
Contributor

Choose a reason for hiding this comment

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

We need a separate make target for that see #1168

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Revised with the new target.

)

type checkFunction func(context.Context, *corev1.Node) (string, error)

var _ = Describe("[rfe_id:28761][performance] Updating parameters in performance profile", func() {
var workerRTNodes []corev1.Node
var profile, initialProfile *performancev2.PerformanceProfile
var performanceMCP string
var resourcePool string
Copy link
Contributor

Choose a reason for hiding this comment

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

let's use poolName instead

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Revised, Thanks.


By("Waiting when mcp finishes updates")
mcps.WaitForCondition(performanceMCP, machineconfigv1.MachineConfigPoolUpdated, corev1.ConditionTrue)
testlog.Infof("Waiting when %s finishes updates", resourcePool)
Copy link
Contributor

Choose a reason for hiding this comment

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

Why did we replace By with testlog.Infof?

Copy link
Contributor

Choose a reason for hiding this comment

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

@SargunNarula can you replace this with By(fmt.Sprintf instead of testlog.Info

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The motivation was to keep log statements consistent. Revised with By().

@Tal-or
Copy link
Contributor

Tal-or commented Sep 18, 2024

Good work, left some comments

@Tal-or
Copy link
Contributor

Tal-or commented Sep 23, 2024

please add this test-suite under the pao-functests-update-only-hypershift makefile target and run:
/test e2e-pao-updating-profile-hypershift

Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

@Tal-or: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-operator
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-techpreview
  • /test e2e-gcp-pao
  • /test e2e-gcp-pao-updating-profile
  • /test e2e-gcp-pao-workloadhints
  • /test e2e-hypershift
  • /test e2e-hypershift-pao
  • /test e2e-no-cluster
  • /test e2e-upgrade
  • /test images
  • /test unit
  • /test verify
  • /test vet

The following commands are available to trigger optional jobs:

  • /test e2e-telco5g-cnftests
  • /test lint
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-operator
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-ovn-techpreview
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao-updating-profile
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao-workloadhints
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-hypershift
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-hypershift-pao
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-no-cluster
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-upgrade
  • pull-ci-openshift-cluster-node-tuning-operator-master-images
  • pull-ci-openshift-cluster-node-tuning-operator-master-lint
  • pull-ci-openshift-cluster-node-tuning-operator-master-unit
  • pull-ci-openshift-cluster-node-tuning-operator-master-verify
  • pull-ci-openshift-cluster-node-tuning-operator-master-vet

In response to this:

please add this test-suite under the pao-functests-update-only-hypershift makefile target and run:
/test e2e-pao-updating-profile-hypershift

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.

@Tal-or
Copy link
Contributor

Tal-or commented Sep 24, 2024

/test help

Copy link
Contributor

openshift-ci bot commented Sep 24, 2024

@Tal-or: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-operator
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-techpreview
  • /test e2e-gcp-pao
  • /test e2e-gcp-pao-updating-profile
  • /test e2e-gcp-pao-workloadhints
  • /test e2e-hypershift
  • /test e2e-hypershift-pao
  • /test e2e-no-cluster
  • /test e2e-pao-updating-profile-hypershift
  • /test e2e-upgrade
  • /test images
  • /test unit
  • /test verify
  • /test vet

The following commands are available to trigger optional jobs:

  • /test e2e-telco5g-cnftests
  • /test lint
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-operator
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-aws-ovn-techpreview
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao-updating-profile
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-gcp-pao-workloadhints
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-hypershift
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-hypershift-pao
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-no-cluster
  • pull-ci-openshift-cluster-node-tuning-operator-master-e2e-upgrade
  • pull-ci-openshift-cluster-node-tuning-operator-master-images
  • pull-ci-openshift-cluster-node-tuning-operator-master-lint
  • pull-ci-openshift-cluster-node-tuning-operator-master-unit
  • pull-ci-openshift-cluster-node-tuning-operator-master-verify
  • pull-ci-openshift-cluster-node-tuning-operator-master-vet

In response to this:

/test help

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.

@Tal-or
Copy link
Contributor

Tal-or commented Sep 24, 2024

/test e2e-pao-updating-profile-hypershift

@Tal-or
Copy link
Contributor

Tal-or commented Oct 1, 2024

/retest
The failure related to:
openshift/release#57238

@Tal-or
Copy link
Contributor

Tal-or commented Oct 1, 2024

/retest

1 similar comment
@SargunNarula
Copy link
Contributor Author

/retest

@Tal-or
Copy link
Contributor

Tal-or commented Oct 6, 2024

{"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:169","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2024-10-04T16:08:19Z"}

We need to increase the timeout of the this lane

@Tal-or
Copy link
Contributor

Tal-or commented Oct 6, 2024

openshift/release#57500

@SargunNarula
Copy link
Contributor Author

/retest

@Tal-or
Copy link
Contributor

Tal-or commented Oct 8, 2024

/lgtm

@Tal-or
Copy link
Contributor

Tal-or commented Nov 6, 2024

/test e2e-pao-updating-profile-hypershift

3 similar comments
@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@SargunNarula
Copy link
Contributor Author

/retest

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@SargunNarula
Copy link
Contributor Author

/retest

@Tal-or
Copy link
Contributor

Tal-or commented Nov 18, 2024

/test e2e-pao-updating-profile-hypershift

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@Tal-or
Copy link
Contributor

Tal-or commented Nov 20, 2024

You're trying to get MCP on Hypershift. MCP CRD are not exist on Hypershift platform

  [FAILED] in [BeforeAll] - /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:1161 @ 11/20/24 13:29:42.748
• [FAILED] [20.126 seconds]
[rfe_id:28761][performance] Updating parameters in performance profile ContainerRuntimeConfig [BeforeAll] when is not given should run high-performance runtimes class with runc as container-runtime [tier-2, openshift]
  [BeforeAll] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:1157
  [It] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:1168
  [FAILED] cannot get MCP "clusters/52cc3a83cf2bb1b34dfb-us-east-1a"
  Unexpected error:
      <*meta.NoKindMatchError | 0xc0008187c0>: 
      no matches for kind "MachineConfigPool" in version "machineconfiguration.openshift.io/v1"
      {
          GroupKind: {
              Group: "machineconfiguration.openshift.io",
              Kind: "MachineConfigPool",
          },
          SearchedVersions: ["v1"],
      }
  occurred
  In [BeforeAll] at: /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:1161 @ 11/20/24 13:29:42.748

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@Tal-or
Copy link
Contributor

Tal-or commented Nov 21, 2024

This is the failure from the the last run on the ci/prow/e2e-gcp-pao-updating-profile

  [FAILED] in [BeforeEach] - /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:98 @ 11/21/24 11:05:12.562
• [FAILED] [0.794 seconds]
[rfe_id:28761][performance] Updating parameters in performance profile [BeforeEach] Updating of nodeSelector parameter and node labels [test_id:27484]Verifies that node is reverted to plain worker when the extra labels are removed [tier-2, openshift]
  [BeforeEach] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:91
  [It] /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:473
  [FAILED] Unexpected error:
      <*errors.errorString | 0xc000592690>: 
      failed to find performance profile with specified node selector map[node-role.kubernetes.io/worker-test:]
      {
          s: "failed to find performance profile with specified node selector map[node-role.kubernetes.io/worker-test:]",
      }
  occurred
  In [BeforeEach] at: /go/src/github.com/openshift/cluster-node-tuning-operator/test/e2e/performanceprofile/functests/2_performance_update/updating_profile.go:98 @ 11/21/24 11:05:12.562

- Updated tests to skip MCP resource verification on Hypershift, where MCP concept does not apply.
- Profile applying is made consistent
- Removed deprecated API client.
- Added test suite run in makefile

Signed-off-by: Sargun Narula <[email protected]>

Added label filter on update only hypershift target

 - The pao-functests-update-only-hypershift lane is designed to run
   the performance update suite exclusively on the HyperShift platform,
   requiring tests to be filtered for HyperShift.

Signed-off-by: Sargun Narula <[email protected]>
@SargunNarula
Copy link
Contributor Author

/retest

1 similar comment
@mrniranjan
Copy link
Contributor

/retest

@mrniranjan
Copy link
Contributor

/retest-required

@SargunNarula
Copy link
Contributor Author

/test e2e-pao-updating-profile-hypershift

@Tal-or
Copy link
Contributor

Tal-or commented Nov 22, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2024
Copy link
Contributor

openshift-ci bot commented Nov 22, 2024

@SargunNarula: all tests passed!

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.

@shajmakh
Copy link
Contributor

shajmakh commented Nov 22, 2024

this is tests adjustments PR and doesn't risk breaking the product
/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants