Skip to content

OCPBUGS-73661: Rename HPA test label filter#2572

Open
maxcao13 wants to merge 1 commit intoopenshift:masterfrom
maxcao13:fix-broken-hpa
Open

OCPBUGS-73661: Rename HPA test label filter#2572
maxcao13 wants to merge 1 commit intoopenshift:masterfrom
maxcao13:fix-broken-hpa

Conversation

@maxcao13
Copy link
Member

Fixes: https://issues.redhat.com/browse/OCPBUGS-73661

Renames the labels for HPA tests to Feature:HPA so this captures all HPA tests, including ones tagged with [Feature:HPAConfigurableTolerance]. Previously the filter was [Feature:HPA]' so these tests were not captured.

Signed-off-by: Max Cao <macao@redhat.com>
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 Jan 22, 2026
@openshift-ci-robot
Copy link

@maxcao13: This pull request references Jira Issue OCPBUGS-73661, 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.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, 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.

Details

In response to this:

Fixes: https://issues.redhat.com/browse/OCPBUGS-73661

Renames the labels for HPA tests to Feature:HPA so this captures all HPA tests, including ones tagged with [Feature:HPAConfigurableTolerance]. Previously the filter was [Feature:HPA]' so these tests were not captured.

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

@maxcao13: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: maxcao13
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@jacobsee
Copy link
Member

Thanks! I will pull your commit directly into the rebase and try it against 1.35 soon.
/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 Jan 22, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

@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/e2e-aws-ovn-serial-1of2 fde1745 link true /test e2e-aws-ovn-serial-1of2

Full PR test history. Your PR dashboard.

Details

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.

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

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants