Skip to content

[release-4.14] OCPBUGS-37016: Bump github.com/containers/image/v5#824

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
m1kola:release-4.14-bump-containers-image
Jul 26, 2024
Merged

[release-4.14] OCPBUGS-37016: Bump github.com/containers/image/v5#824
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
m1kola:release-4.14-bump-containers-image

Conversation

@m1kola
Copy link
Copy Markdown
Contributor

@m1kola m1kola commented Jul 17, 2024

No description provided.

[CARRY] Bump github.com/containers/image/v5
f2fbd8f 
Signed-off-by: Mikalai Radchuk <mradchuk@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 Jul 17, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 17, 2024

@m1kola: This pull request references Jira Issue OCPBUGS-37016, which is invalid:

  • expected dependent Jira Issue OCPBUGS-37017 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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:

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 dinhxuanvu and grokspawn July 17, 2024 12:41
@m1kola
Copy link
Copy Markdown
Contributor Author

m1kola commented Jul 17, 2024

/retest

bandrade
bandrade approved these changes Jul 17, 2024
View reviewed changes
Copy link
Copy Markdown
Contributor

@bandrade bandrade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/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 Jul 17, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2024
@kevinrizza
Copy link
Copy Markdown
Member

kevinrizza commented Jul 18, 2024

/approve
/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 Jul 18, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bandrade, kevinrizza, m1kola

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 18, 2024
@bandrade
Copy link
Copy Markdown
Contributor

bandrade commented Jul 25, 2024

/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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 25, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 25, 2024

@bandrade: This pull request references Jira Issue OCPBUGS-37016, 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.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, 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-37017 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-37017 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

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.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 26, 2024

/retest-required

Remaining retests: 0 against base HEAD b699086 and 2 for PR HEAD f2fbd8f in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 26, 2024

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 8d9b39e into openshift:release-4.14 Jul 26, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 26, 2024

@m1kola: Jira Issue OCPBUGS-37016: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-37016 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-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jul 26, 2024

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.14.0-202407260439.p0.g8d9b39e.assembly.stream.el8.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Jul 26, 2024

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.14.0-202407260439.p0.g8d9b39e.assembly.stream.el8.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

openshift-merge-robot commented Jul 26, 2024

Fix included in accepted release 4.14.0-0.nightly-2024-07-26-074621

@m1kola m1kola deleted the release-4.14-bump-containers-image branch July 29, 2024 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@grokspawn grokspawn Awaiting requested review from grokspawn

1 more reviewer

@bandrade bandrade bandrade approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@bandrade bandrade

@jianzhangbjz jianzhangbjz

@emmajiafan emmajiafan

@kuiwang02 kuiwang02

@Xia-Zhao-rh Xia-Zhao-rh

@KeenonLee KeenonLee

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.