Skip to content

Conversation

@maxcao13
Copy link
Member

We need to isolate HPA parallel tests because of resource contention with other parallelized tests.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 22, 2025
@openshift-ci-robot
Copy link

@maxcao13: This pull request references Jira Issue OCPBUGS-61376, which is valid.

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

Requesting review from QA contact:
/cc @prozehna

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

In response to this:

We need to isolate HPA parallel tests because of resource contention with other parallelized tests.

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.

@xueqzhan
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 22, 2025
@neisw
Copy link
Contributor

neisw commented Oct 22, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 22, 2025
We need to isolate HPA parallel tests because of resource contention with other parallelized tests.

Signed-off-by: Max Cao <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 22, 2025
@maxcao13
Copy link
Member Author

The tests require openshift/kubernetes#2492 to actually show that the isolation solves the OCPBUGS problem since the HPA tests are currently disabled.

But my multi-pr test command in that PR is not playing well right now: openshift/kubernetes#2492 (comment)

@neisw
Copy link
Contributor

neisw commented Oct 22, 2025

lgtm - but I want to verify via the job results before tagging

@neisw
Copy link
Contributor

neisw commented Oct 23, 2025

/lgtm

Won't see those test as they are skipped currently

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maxcao13, neisw, xueqzhan

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@maxcao13
Copy link
Member Author

/retest

@neisw
Copy link
Contributor

neisw commented Oct 23, 2025

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 23, 2025
@openshift-ci-robot
Copy link

@neisw: The verified label has been added.

In response to this:

/verified bypass

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.

@neisw
Copy link
Contributor

neisw commented Oct 23, 2025

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 23, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d629cf1 and 2 for PR HEAD 3007cfa in total

@openshift-trt
Copy link

openshift-trt bot commented Oct 24, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 3007cfa

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many applies" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "apply" requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "create" requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "patch" requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "update" requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:generation-analyzer]objects in ns/openshift-commatrix-test should have generation increasing monotonically" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:generation-analyzer]objects in ns/openshift-commatrix-test should not have too many generations" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:initial-and-final-operator-log-scraper]operators in in ns/openshift-commatrix-test should not submit invalid apply statements" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not exit a moderate amount of times" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not exit an excessive amount of times" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not fail to start" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 High - "[sig-network][Feature:commatrix][apigroup:config.openshift.io][Serial] should validate the communication matrix ports match the node's listening ports [Suite:openshift/conformance/serial]" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 3007cfa

  • "Import the release payload "nightly-arm64" from an external source" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many applies" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "apply" requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "create" requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "patch" requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:audit-log-analyzer]users in ns/openshift-commatrix-test must not produce too many invalid "update" requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:generation-analyzer]objects in ns/openshift-commatrix-test should have generation increasing monotonically" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:generation-analyzer]objects in ns/openshift-commatrix-test should not have too many generations" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:initial-and-final-operator-log-scraper]operators in in ns/openshift-commatrix-test should not submit invalid apply statements" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not exit a moderate amount of times" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not exit an excessive amount of times" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[Monitor:kubelet-container-restarts][sig-architecture] platform pods in ns/openshift-commatrix-test should not fail to start" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[sig-network][Feature:commatrix][apigroup:config.openshift.io][Serial] should validate the communication matrix ports match the node's listening ports [Suite:openshift/conformance/serial]" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 450d258 and 1 for PR HEAD 3007cfa in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 367ab40 and 0 for PR HEAD 3007cfa in total

@openshift-ci-robot
Copy link

/hold

Revision 3007cfa was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@maxcao13: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 3007cfa link false /test okd-scos-e2e-aws-ovn

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.

@maxcao13
Copy link
Member Author

Tests are unrelated to the change. Am I supposed to rebase on main because we merged 1.34 bump yesterday or will these flakes eventually resolve?

@maxcao13
Copy link
Member Author

/retest-required

@maxcao13
Copy link
Member Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 25, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 2492df5 and 2 for PR HEAD 3007cfa in total

@openshift-merge-bot openshift-merge-bot bot merged commit 20578e7 into openshift:main Oct 25, 2025
20 of 21 checks passed
@openshift-ci-robot
Copy link

@maxcao13: Jira Issue OCPBUGS-61376: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-61376 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

In response to this:

We need to isolate HPA parallel tests because of resource contention with other parallelized tests.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants