Skip to content

OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12#1329

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.12from
oglok:criodepbackport
Feb 8, 2023
Merged

OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12#1329
openshift-merge-robot merged 1 commit intoopenshift:release-4.12from
oglok:criodepbackport

Conversation

@oglok
Copy link
Contributor

@oglok oglok commented Feb 6, 2023

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-7139

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
@openshift-ci-robot 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 Feb 6, 2023
@openshift-ci-robot
Copy link

@oglok: This pull request references Jira Issue OCPBUGS-6858, which is invalid:

  • expected the bug to target the "4.12.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-6858 to depend on a bug targeting a version in 4.13.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-6858

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2023

@oglok: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-6858: Add minimum CRIO version as rpm requirement

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/test-infra repository.

@oglok oglok changed the title OCPBUGS-6858: Add minimum CRIO version as rpm requirement OCPBUGS-6858: Add minimum CRIO version as rpm requirement for MicroShift 4.12 Feb 6, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2023

@oglok: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-6858: Add minimum CRIO version as rpm requirement for MicroShift 4.12

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/test-infra repository.

@openshift-ci openshift-ci bot requested review from mangelajo and stlaz February 6, 2023 16:22
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2023
@oglok
Copy link
Contributor Author

oglok commented Feb 6, 2023

/retest

@oglok
Copy link
Contributor Author

oglok commented Feb 6, 2023

/jira-refresh

@oglok oglok changed the title OCPBUGS-6858: Add minimum CRIO version as rpm requirement for MicroShift 4.12 OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12 Feb 7, 2023
@openshift-ci-robot
Copy link

@oglok: This pull request references Jira Issue OCPBUGS-7139, which is invalid:

  • expected Jira Issue OCPBUGS-7139 to depend on a bug targeting a version in 4.13.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-6858

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@openshift-ci-robot
Copy link

@oglok: This pull request references Jira Issue OCPBUGS-7139, which is invalid:

  • expected Jira Issue OCPBUGS-7139 to depend on a bug targeting a version in 4.13.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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.

Details

In response to this:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-7139

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2023

@oglok: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12

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/test-infra repository.

@oglok
Copy link
Contributor Author

oglok commented Feb 7, 2023

/jira-refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2023

@oglok: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12

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/test-infra repository.

@oglok
Copy link
Contributor Author

oglok commented Feb 7, 2023

/cherrypick release-4.12

@openshift-cherrypick-robot

@oglok: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.12

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/test-infra repository.

@ggiguash
Copy link
Contributor

ggiguash commented Feb 7, 2023

/jira refresh

@openshift-ci-robot
Copy link

@ggiguash: This pull request references Jira Issue OCPBUGS-7139, which is invalid:

  • expected dependent Jira Issue OCPBUGS-6858 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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 kubernetes/test-infra repository.

@ggiguash
Copy link
Contributor

ggiguash commented Feb 7, 2023

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 7, 2023
@jogeo
Copy link
Contributor

jogeo commented Feb 7, 2023

/label cherry-pick-approved

@openshift-ci 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 Feb 7, 2023
@oglok
Copy link
Contributor Author

oglok commented Feb 7, 2023

/jira-refresh

@oglok oglok closed this Feb 7, 2023
@openshift-ci-robot
Copy link

@oglok: This pull request references Jira Issue OCPBUGS-7139. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-7139

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@oglok oglok reopened this Feb 7, 2023
@openshift-ci-robot
Copy link

@oglok: This pull request references Jira Issue OCPBUGS-7139, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Duplicate) 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.

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

Details

In response to this:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-7139

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 7, 2023

@oglok: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-7139: Add minimum CRIO version as rpm requirement for MicroShift 4.12

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/test-infra repository.

@oglok
Copy link
Contributor Author

oglok commented Feb 7, 2023

/jira-refresh

@oglok
Copy link
Contributor Author

oglok commented Feb 7, 2023

/retest

@oglok
Copy link
Contributor Author

oglok commented Feb 8, 2023

/jira-refresh

@ggiguash
Copy link
Contributor

ggiguash commented Feb 8, 2023

/lgtm

@ggiguash
Copy link
Contributor

ggiguash commented Feb 8, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla 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 Feb 8, 2023
@openshift-ci-robot
Copy link

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-6858 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-6858 targets the "4.13.0" version, which is one of the valid target versions: 4.13.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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested a review from jogeo February 8, 2023 14:23
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, oglok

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

openshift-ci bot commented Feb 8, 2023

@oglok: 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 3e3d09f into openshift:release-4.12 Feb 8, 2023
@openshift-ci-robot
Copy link

@oglok: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Signed-off-by: Ricardo Noriega rnoriega@redhat.com

Which issue(s) this PR addresses:
Closes #OCPBUGS-7139

We are using a minimum requirement for CRIO, assuming the release team will only provide the CRIO version according to the OCP requirements of that release.

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/test-infra repository.

@openshift-cherrypick-robot

@oglok: base branch (release-4.12) needs to differ from target branch (release-4.12)

Details

In response to this:

/cherrypick release-4.12

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/test-infra repository.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.