[release-4.16] OCPBUGS-35814: Fix CRI-O version to match Kubernetes version by pmtk · Pull Request #3513 · openshift/microshift

pmtk · 2024-06-19T08:31:09Z

No description provided.

openshift-ci-robot · 2024-06-19T08:31:14Z

@pmtk: This pull request references Jira Issue OCPBUGS-35814, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
expected Jira Issue OCPBUGS-35814 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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.

pmtk · 2024-06-19T08:35:49Z

/jira refresh

openshift-ci-robot · 2024-06-19T08:35:52Z

@pmtk: This pull request references Jira Issue OCPBUGS-35814, which is invalid:

expected dependent Jira Issue OCPBUGS-35507 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

pmtk · 2024-06-21T06:47:31Z

/test metal-periodic-test-arm

pmtk · 2024-06-21T07:18:36Z

/jira refresh

openshift-ci-robot · 2024-06-21T07:18:43Z

@pmtk: This pull request references Jira Issue OCPBUGS-35814, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.0) matches configured target version for branch (4.16.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-35507 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-35507 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
bug has dependents

Requesting review from QA contact:
/cc @jogeo

Details

In response to this:

/jira refresh

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.

pacevedom · 2024-06-24T12:37:13Z

/hold
until go/no go meeting today. We have until wednesday to merge it.

pmtk · 2024-06-25T07:32:43Z

/retest

jogeo · 2024-06-27T14:20:42Z

/label cherry-pick-approved

jerpeter1 · 2024-06-28T18:35:25Z

/hold cancel

jerpeter1 · 2024-06-28T18:37:32Z

/lgtm

pacevedom · 2024-06-28T21:23:25Z

/label backport-risk-assessed

openshift-ci-robot · 2024-06-28T22:27:24Z

/retest-required

Remaining retests: 0 against base HEAD 8babeb9 and 2 for PR HEAD 704bb20b5120490b000d540fc3735d28a81c6d70 in total

If newer CRI-O is installed than CRI-O present in the inspected repository then DNF will not consider it, meaning it will pretend like there is no CRI-O in the inspected repository. By adding --showduplicates DNF will show information about the CRI-O in the repository regardless if newer is installed on the system or not.

pmtk · 2024-07-01T10:45:37Z

/retest microshift-metal-tests

openshift-ci · 2024-07-01T10:45:41Z

@pmtk: The /retest command does not accept any targets.
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 ocp-full-conformance-rhel-eus
/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.16-images
pull-ci-openshift-microshift-release-4.16-metal-periodic-test
pull-ci-openshift-microshift-release-4.16-metal-periodic-test-arm
pull-ci-openshift-microshift-release-4.16-microshift-metal-tests
pull-ci-openshift-microshift-release-4.16-microshift-metal-tests-arm
pull-ci-openshift-microshift-release-4.16-test-rpm
pull-ci-openshift-microshift-release-4.16-test-unit
pull-ci-openshift-microshift-release-4.16-verify

Details

In response to this:

/retest microshift-metal-tests

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 · 2024-07-01T12:51:42Z

/test microshift-metal-tests

[MIRROR] cri-o-1.29.5-5.rhaos4.16.git7032128.el9.x86_64.rpm: Curl error (28): Timeout was reached for https://cdn.redhat.com/content/dist/layered/rhel9/x86_64/rhocp/4.16/os/Packages/c/cri-o-1.29.5-5.rhaos4.16.git7032128.el9.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(6/6): cri-o-1.29.5-5.rhaos4.16.git7032128.el9. 503 kB/s |  18 MB     00:37

but it got installed

openshift-ci · 2024-07-01T14:03:15Z

@pmtk: 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.

pacevedom

/lgtm

openshift-ci · 2024-07-01T16:01:51Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerpeter1, pacevedom, 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:

~~OWNERS~~ [jerpeter1,pacevedom,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2024-07-01T16:06:24Z

@pmtk: Jira Issue OCPBUGS-35814: All pull requests linked via external trackers have merged:

openshift/microshift#3513

Jira Issue OCPBUGS-35814 has been moved to the MODIFIED state.

Details

In response to this:

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 added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 19, 2024

openshift-ci Bot requested review from ggiguash and jerpeter1 June 19, 2024 08:34

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 19, 2024

pmtk force-pushed the rpm-spec-crio-ver/release-4.16 branch 7 times, most recently from f759028 to 7a9f0fe Compare June 20, 2024 15:57

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 21, 2024

openshift-ci Bot requested a review from jogeo June 21, 2024 07:18

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 24, 2024

openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 27, 2024

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 28, 2024

openshift-ci Bot assigned jerpeter1 Jun 28, 2024

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 28, 2024

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 28, 2024

pmtk force-pushed the rpm-spec-crio-ver/release-4.16 branch from 704bb20 to 3e9453b Compare July 1, 2024 07:18

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 1, 2024

pmtk added 3 commits July 1, 2024 11:28

Fix CRI-O version to match Kubernetes version

a524381

Don't expect that previous RHOCP will be enabled on the system

1d1a392

pmtk force-pushed the rpm-spec-crio-ver/release-4.16 branch from 3e9453b to 24613dc Compare July 1, 2024 09:29

pmtk mentioned this pull request Jul 1, 2024

NO-ISSUE: Add 4.15 rhocp repo to configure-vm.sh #3557

Closed

pacevedom approved these changes Jul 1, 2024

View reviewed changes

openshift-ci Bot assigned pacevedom Jul 1, 2024

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 1, 2024

openshift-merge-bot Bot merged commit 3efd8a4 into openshift:release-4.16 Jul 1, 2024

pmtk deleted the rpm-spec-crio-ver/release-4.16 branch July 1, 2024 16:12

Conversation

pmtk commented Jun 19, 2024

Uh oh!

openshift-ci-robot commented Jun 19, 2024

Uh oh!

pmtk commented Jun 19, 2024

Uh oh!

openshift-ci-robot commented Jun 19, 2024

Uh oh!

pmtk commented Jun 21, 2024

Uh oh!

pmtk commented Jun 21, 2024

Uh oh!

openshift-ci-robot commented Jun 21, 2024

Uh oh!

pacevedom commented Jun 24, 2024

Uh oh!

pmtk commented Jun 25, 2024

Uh oh!

jogeo commented Jun 27, 2024

Uh oh!

jerpeter1 commented Jun 28, 2024

Uh oh!

jerpeter1 commented Jun 28, 2024

Uh oh!

pacevedom commented Jun 28, 2024

Uh oh!

openshift-ci-robot commented Jun 28, 2024

Uh oh!

pmtk commented Jul 1, 2024

Uh oh!

openshift-ci Bot commented Jul 1, 2024

Uh oh!

pmtk commented Jul 1, 2024

Uh oh!

openshift-ci Bot commented Jul 1, 2024

Uh oh!

pacevedom left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Jul 1, 2024

Uh oh!

openshift-ci-robot commented Jul 1, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants