Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2026-04-29-161743_amd64-2026-04-29_arm64-2026-04-30#6611

Open
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2026-04-29-161743_amd64-2026-04-29_arm64-2026-04-30
Open

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2026-04-29-161743_amd64-2026-04-29_arm64-2026-04-30#6611
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2026-04-29-161743_amd64-2026-04-29_arm64-2026-04-30

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.19.0-0.nightly-2026-04-29-161743
arm64: 4.19.0-0.nightly-arm64-2026-04-30-034926
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/2049700597384351744

  • cluster-kube-apiserver-operator embedded-component 4bbd3be9dfda4a08dca98648209151de2a869f25 to 1b48403438c3e0eb2ccb5cae331f12fe9abe169c

    • 85bb270 2026-04-21T14:03:12+02:00 configobservation/auth: allow setting the oauthMetadata when auth type is None
  • cluster-network-operator embedded-component b5f9806ed0aee267baa390c3e0e5943d73ad60ef to ca69ef09c1bba973b3806ecf4f01302b808e2edd

    • 6394b07 2026-04-22T11:35:43-04:00 OCPBUGS-72411: use net.JoinHostPort for URL construction

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

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 30, 2026
@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.19.0-0.nightly-2026-04-29-161743
arm64: 4.19.0-0.nightly-arm64-2026-04-30-034926
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/2049700597384351744

  • cluster-kube-apiserver-operator embedded-component 4bbd3be9dfda4a08dca98648209151de2a869f25 to 1b48403438c3e0eb2ccb5cae331f12fe9abe169c

  • 85bb270 2026-04-21T14:03:12+02:00 configobservation/auth: allow setting the oauthMetadata when auth type is None

  • cluster-network-operator embedded-component b5f9806ed0aee267baa390c3e0e5943d73ad60ef to ca69ef09c1bba973b3806ecf4f01302b808e2edd

  • 6394b07 2026-04-22T11:35:43-04:00 OCPBUGS-72411: use net.JoinHostPort for URL construction

/label tide/merge-method-squash
/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. 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 Apr 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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 ggiguash and jerpeter1 April 30, 2026 04:27
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 30, 2026

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

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-merge-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 46d306b and 2 for PR HEAD de23647 in total

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-arm

Added by prow-jobs-for-pull-requests.sh 🤖

@pacevedom
Copy link
Copy Markdown
Contributor

/retest

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-arm

Added by prow-jobs-for-pull-requests.sh 🤖

@pacevedom
Copy link
Copy Markdown
Contributor

/retest

1 similar comment
@pacevedom
Copy link
Copy Markdown
Contributor

/retest

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-arm

Added by prow-jobs-for-pull-requests.sh 🤖

1 similar comment
@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-arm

Added by prow-jobs-for-pull-requests.sh 🤖

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

@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/e2e-aws-tests-arm de23647 link true /test e2e-aws-tests-arm

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.

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