Skip to content

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-08-21-192930_amd64-2024-08-21_arm64-2024-08-21#3815

Closed
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-08-21-192930_amd64-2024-08-21_arm64-2024-08-21
Closed

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-08-21-192930_amd64-2024-08-21_arm64-2024-08-21#3815
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-08-21-192930_amd64-2024-08-21_arm64-2024-08-21

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.16.0-0.nightly-2024-08-21-192930
arm64: 4.16.0-0.nightly-arm64-2024-08-21-175125
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1827919104405671936

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

@microshift-rebase-script
Copy link
Contributor Author

Extra messages:

@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.16.0-0.nightly-2024-08-21-192930
arm64: 4.16.0-0.nightly-arm64-2024-08-21-175125
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1827919104405671936

/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 Aug 26, 2024
@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 jerpeter1 August 26, 2024 04:20
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

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

@copejon
Copy link
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
Contributor

copejon commented Aug 26, 2024

/cc copejon

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

Tests did not encounter the secrets issue, but dnf failed to install openvswitch

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

@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 5e0d3f0 link true /test microshift-metal-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.

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

The error check is a little too fuzzy. Curl is producing an internal dnf error, but the install succeeds nonetheless.

[MIRROR] openvswitch3.3-3.3.0-30.el9fdp.aarch64.rpm: Curl error (28): Timeout was reached for https://cdn.redhat.com/content/dist/layered/rhel9/aarch64/fast-datapath/os/Packages/o/openvswitch3.3-3.3.0-30.el9fdp.aarch64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] cri-tools-1.29.0-4.el9.aarch64.rpm: Curl error (28): Timeout was reached for https://cdn.redhat.com/content/dist/layered/rhel9/aarch64/rhocp/4.16/os/Packages/c/cri-tools-1.29.0-4.el9.aarch64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] cri-o-1.29.7-3.rhaos4.16.git969f759.el9.aarch64.rpm: Curl error (28): Timeout was reached for https://cdn.redhat.com/content/dist/layered/rhel9/aarch64/rhocp/4.16/os/Packages/c/cri-o-1.29.7-3.rhaos4.16.git969f759.el9.aarch64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]

...truncated...

Installed:
  openvswitch3.3-3.3.0-30.el9fdp.aarch64                                        

Complete!' contains 'error'

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

Forgot to backport #3500. The fix is started #3817

/close

@copejon
Copy link
Contributor

copejon commented Aug 26, 2024

/close

@openshift-ci openshift-ci bot closed this Aug 26, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

@copejon: Closed this PR.

Details

In response to this:

/close

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.

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