Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2025-02-20-001209_amd64-2025-02-20_arm64-2025-02-21 #4588

Open
wants to merge 5 commits into
base: release-4.15
Choose a base branch
from

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.15.0-0.nightly-2025-02-20-001209
arm64: 4.15.0-0.nightly-arm64-2025-02-21-134046
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1893873883539312640

  • cluster-kube-apiserver-operator embedded-component aabc7863cdbd76f8909a10fbc1be53b032e4ec31 to b5b212e5cecf729bb15248d26edbd55dbe7253a9

    • a031e5b 2025-02-13T01:58:29+00:00 increase waitForFallbackDegradedConditionTimeout
  • machine-config-operator embedded-component b608d409f85d9d2f5ec8837d33490fdc6b6883a6 to 9040a70ce67b34643aa4fd17dece6a9b65a48d95

    • 3868f711 2025-02-10T20:59:45+00:00 node controller: clarify when 'maxUnavailible' is invalid in alert
  • ovn-kubernetes image-amd64 cc1522a772fbd586a192a8ceb02980a41734f7b6 to f749d5f5981d0041356671ed0c361133c3273e6d

    • 1cd6dfd 2024-12-13T11:46:41+00:00 Add static route to the hairpin masquerade IPs to pod
  • ovn-kubernetes image-arm64 cc1522a772fbd586a192a8ceb02980a41734f7b6 to f749d5f5981d0041356671ed0c361133c3273e6d

    • 1cd6dfd 2024-12-13T11:46:41+00:00 Add static route to the hairpin masquerade IPs to pod

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

@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.15.0-0.nightly-2025-02-20-001209
arm64: 4.15.0-0.nightly-arm64-2025-02-21-134046
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1893873883539312640

  • cluster-kube-apiserver-operator embedded-component aabc7863cdbd76f8909a10fbc1be53b032e4ec31 to b5b212e5cecf729bb15248d26edbd55dbe7253a9

  • a031e5b 2025-02-13T01:58:29+00:00 increase waitForFallbackDegradedConditionTimeout

  • machine-config-operator embedded-component b608d409f85d9d2f5ec8837d33490fdc6b6883a6 to 9040a70ce67b34643aa4fd17dece6a9b65a48d95

  • 3868f711 2025-02-10T20:59:45+00:00 node controller: clarify when 'maxUnavailible' is invalid in alert

  • ovn-kubernetes image-amd64 cc1522a772fbd586a192a8ceb02980a41734f7b6 to f749d5f5981d0041356671ed0c361133c3273e6d

  • 1cd6dfd 2024-12-13T11:46:41+00:00 Add static route to the hairpin masquerade IPs to pod

  • ovn-kubernetes image-arm64 cc1522a772fbd586a192a8ceb02980a41734f7b6 to f749d5f5981d0041356671ed0c361133c3273e6d

  • 1cd6dfd 2024-12-13T11:46:41+00:00 Add static route to the hairpin masquerade IPs to pod

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

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign eslutsky for approval. For more information see the Code Review Process.

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

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

@eslutsky
Copy link
Contributor

/test microshift-metal-tests-arm

Copy link
Contributor

openshift-ci bot commented Feb 25, 2025

@microshift-rebase-script[bot]: 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/microshift-metal-tests-arm 95fbde9 link true /test microshift-metal-tests-arm

Full PR test history. Your PR dashboard.

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
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. 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