Skip to content

[release-4.14] USHIFT-4867: error in microshift RF tests randomize parameter#4565

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
agullon:USHIFT-4867_4.14
Feb 20, 2025
Merged

[release-4.14] USHIFT-4867: error in microshift RF tests randomize parameter#4565
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
agullon:USHIFT-4867_4.14

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Feb 17, 2025

This is a manual cherry-pick from: #3769

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 17, 2025

@agullon: An error was encountered searching for bug USHIFT-4867 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 401:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

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 openshift-ci bot requested review from dhellmann and jogeo February 17, 2025 11:09
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2025

@agullon: This pull request references USHIFT-4867 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 task to target the "4.14.z" version, but no target version was set.

Details

In response to this:

This is a manual cherry-pick from: #3769

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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented Feb 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, pacevedom

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 20, 2025
@ggiguash
Copy link
Contributor

ggiguash commented Feb 20, 2025

/retitle [release-4.14] USHIFT-4867: error in microshift RF tests randomize parameter

@openshift-ci openshift-ci bot changed the title USHIFT-4867: error in microshift RF tests randomize parameter [release-4.14] USHIFT-4867: error in microshift RF tests randomize parameter Feb 20, 2025
@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/label cherry-pick-approved
/label jira/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

@agullon: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit f83ff21 into openshift:release-4.14 Feb 20, 2025
5 checks passed
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

4 participants