Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CNV-55082: use new 4.18 image for export bootable volumes #2378

Merged

Conversation

upalatucci
Copy link
Member

@upalatucci upalatucci commented Jan 21, 2025

📝 Description

as requested by dominik: #2318 (comment)

and here https://issues.redhat.com/browse/CNV-55082

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 21, 2025

@upalatucci: This pull request references CNV-55082 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

📝 Description

as requested by dominik: #2318 (comment)

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 the approved This issue is something we want to fix label Jan 21, 2025
@metalice
Copy link
Member

Why do we want 4.17 image on 4.18 rls?

@upalatucci upalatucci changed the title CNV-55082: use a 4.17 image for export bootable volumes CNV-55082: use new 4.18 image for export bootable volumes Jan 22, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 22, 2025

@upalatucci: This pull request references CNV-55082 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

📝 Description

as requested by dominik: #2318 (comment)

and here https://issues.redhat.com/browse/CNV-55082

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 the lgtm Passed code review, ready for merge label Jan 22, 2025
Copy link
Contributor

openshift-ci bot commented Jan 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metalice, upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [metalice,upalatucci]

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 openshift-merge-bot bot merged commit e3c0428 into kubevirt-ui:main Jan 22, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix jira/valid-reference lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants