Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2024-08-19-165854_amd64-2024-08-19_arm64-2024-08-24#3813

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2024-08-19-165854_amd64-2024-08-19_arm64-2024-08-24
Aug 26, 2024
Merged

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2024-08-19-165854_amd64-2024-08-19_arm64-2024-08-24#3813
openshift-merge-bot[bot] merged 5 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2024-08-19-165854_amd64-2024-08-19_arm64-2024-08-24

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.17.0-0.nightly-2024-08-19-165854
arm64: 4.17.0-0.nightly-arm64-2024-08-24-040530
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1827919106083393536

  • oc image-arm64 51ca91a2e3bc21e8d3c6b1850fd1088a1d002ecf to 30c77fb30bef0cf2c4b7ab37862ae060f6faf47d
    • 95e0aa72 2024-08-20T13:28:44+00:00 Adding examples for add-cluster-role-to-* and remove-cluster-role-from-* so they show in the CLI docs

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 26, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.17.0-0.nightly-2024-08-19-165854
arm64: 4.17.0-0.nightly-arm64-2024-08-24-040530
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/1827919106083393536

  • oc image-arm64 51ca91a2e3bc21e8d3c6b1850fd1088a1d002ecf to 30c77fb30bef0cf2c4b7ab37862ae060f6faf47d
  • 95e0aa72 2024-08-20T13:28:44+00:00 Adding examples for add-cluster-role-to-* and remove-cluster-role-from-* so they show in the CLI docs

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

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 added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 26, 2024
@openshift-ci openshift-ci Bot requested review from copejon and pacevedom August 26, 2024 04:18
@copejon
Copy link
Copy Markdown
Contributor

copejon commented Aug 26, 2024

Failed due to malformed secret. This seems to have been resolved just recently, so 1 retest before closing.

/retest

@copejon copejon self-assigned this Aug 26, 2024
@copejon
Copy link
Copy Markdown
Contributor

copejon commented Aug 26, 2024

/cc copejon

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 26, 2024

@microshift-rebase-script[bot]: 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.

@copejon
Copy link
Copy Markdown
Contributor

copejon commented Aug 26, 2024

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, microshift-rebase-script[bot]

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 Aug 26, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit 7a823cb into release-4.17 Aug 26, 2024
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.17-4.17.0-0.nightly-2024-08-19-165854_amd64-2024-08-19_arm64-2024-08-24 branch August 26, 2024 20:31
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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants