Skip to content

[release-4.13] USHIFT-289: Changes to microshift-validate/ for ARM CI#1502

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.13from
pmtk:arm-kuttl-4.13
Mar 14, 2023
Merged

[release-4.13] USHIFT-289: Changes to microshift-validate/ for ARM CI#1502
openshift-merge-robot merged 1 commit intoopenshift:release-4.13from
pmtk:arm-kuttl-4.13

Conversation

@pmtk
Copy link
Member

@pmtk pmtk commented Mar 14, 2023

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 14, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 14, 2023

@pmtk: This pull request references USHIFT-289 which is a valid jira issue.

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 kubernetes/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 14, 2023

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.13] USHIFT-289: Changes to microshift-validate/ for ARM CI

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/test-infra repository.

@openshift-ci openshift-ci bot requested review from sallyom and stlaz March 14, 2023 09:04
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 14, 2023
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 14, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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

@pmtk
Copy link
Member Author

pmtk commented Mar 14, 2023

/test e2e-loadbalancer-smoke-test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 14, 2023

@pmtk: 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/test-infra repository. I understand the commands that are listed here.

@pacevedom
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 14, 2023
@pmtk
Copy link
Member Author

pmtk commented Mar 14, 2023

/label bugzilla/valid-bug
/label backport-risk-assessed

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Mar 14, 2023
@openshift-merge-robot openshift-merge-robot merged commit 32ce4c0 into openshift:release-4.13 Mar 14, 2023
@pmtk pmtk deleted the arm-kuttl-4.13 branch March 29, 2023 13:25
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.