Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-28-170019_amd64-2024-07-28_arm64-2024-07-28#3686

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-28-170019_amd64-2024-07-28_arm64-2024-07-28
Jul 29, 2024
Merged

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-28-170019_amd64-2024-07-28_arm64-2024-07-28#3686
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-28-170019_amd64-2024-07-28_arm64-2024-07-28

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-07-28-170019
arm64: 4.15.0-0.nightly-arm64-2024-07-28-221643
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1817772377849729024

  • cluster-kube-apiserver-operator embedded-component 62a9eff944bfbdc1b4e79332fe4d8ae2df053c8c to aabc7863cdbd76f8909a10fbc1be53b032e4ec31

    • 9f52a49 2024-07-25T13:12:48+00:00 p/o/podsecurityreadinesscontroller: add disabled syncer
    • 2178bbd 2024-07-25T13:12:48+00:00 p/o/psreadinesscontroller: make ctrl owner aware
    • 11d242e 2024-07-25T13:12:48+00:00 p/o/psreadinesscontroller: minor refactoring
  • operator-framework-olm embedded-component f3f8de5d0caa7387630272260e9e4e0db1b8ef85 to 80dee4eb4c5ec643131052292313191e600e5d0c

    • d209907e 2024-07-25T12:01:36+01:00 set required-scc for openshift workloads

/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 Jul 29, 2024
@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.15.0-0.nightly-2024-07-28-170019
arm64: 4.15.0-0.nightly-arm64-2024-07-28-221643
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1817772377849729024

  • cluster-kube-apiserver-operator embedded-component 62a9eff944bfbdc1b4e79332fe4d8ae2df053c8c to aabc7863cdbd76f8909a10fbc1be53b032e4ec31

  • 9f52a49 2024-07-25T13:12:48+00:00 p/o/podsecurityreadinesscontroller: add disabled syncer

  • 2178bbd 2024-07-25T13:12:48+00:00 p/o/psreadinesscontroller: make ctrl owner aware

  • 11d242e 2024-07-25T13:12:48+00:00 p/o/psreadinesscontroller: minor refactoring

  • operator-framework-olm embedded-component f3f8de5d0caa7387630272260e9e4e0db1b8ef85 to 80dee4eb4c5ec643131052292313191e600e5d0c

  • d209907e 2024-07-25T12:01:36+01:00 set required-scc for openshift workloads

/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 Jul 29, 2024
@openshift-ci openshift-ci bot requested review from jogeo and pacevedom July 29, 2024 04:19
@pmtk
Copy link
Member

pmtk commented Jul 29, 2024

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 2024

@pmtk: The following commands are available to trigger required jobs:

  • /test images
  • /test metal-periodic-test
  • /test metal-periodic-test-arm
  • /test microshift-metal-cache
  • /test microshift-metal-cache-arm
  • /test microshift-metal-tests
  • /test microshift-metal-tests-arm
  • /test ocp-conformance-rhel-eus
  • /test ocp-conformance-rhel-eus-arm
  • /test test-rpm
  • /test test-unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test test-rebase

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-microshift-release-4.15-images
  • pull-ci-openshift-microshift-release-4.15-microshift-metal-tests
  • pull-ci-openshift-microshift-release-4.15-microshift-metal-tests-arm
  • pull-ci-openshift-microshift-release-4.15-ocp-conformance-rhel-eus
  • pull-ci-openshift-microshift-release-4.15-ocp-conformance-rhel-eus-arm
  • pull-ci-openshift-microshift-release-4.15-test-rebase
  • pull-ci-openshift-microshift-release-4.15-test-unit
  • pull-ci-openshift-microshift-release-4.15-verify
Details

In response to this:

/test ?

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.

@pmtk
Copy link
Member

pmtk commented Jul 29, 2024

/test metal-periodic-test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 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.

@pmtk
Copy link
Member

pmtk commented Jul 29, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: microshift-rebase-script[bot], 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d4ae096 into release-4.15 Jul 29, 2024
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-07-28-170019_amd64-2024-07-28_arm64-2024-07-28 branch July 29, 2024 11:18
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