Skip to content

OCPNODE-4049: Revert "OCPNODE-3173: Disable OCI artifact mount by default."#5687

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bitoku:enable-artifact
Mar 12, 2026
Merged

OCPNODE-4049: Revert "OCPNODE-3173: Disable OCI artifact mount by default."#5687
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
bitoku:enable-artifact

Conversation

@bitoku
Copy link
Copy Markdown
Contributor

@bitoku bitoku commented Feb 24, 2026

This reverts commit d21d404

- What I did
Fixes https://issues.redhat.com/browse/OCPNODE-4049
- How to verify it
with downstream e2e test to verify it can mount oci artifact.
- Description for the changelog

Enabled OCI Artifact Mount

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 24, 2026 •
edited by openshift-ci bot
Loading

@bitoku: This pull request references OCPNODE-3173 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This reverts commit d21d404

- What I did
Fixes https://issues.redhat.com/browse/OCPNODE-4049
- How to verify it
with downstream e2e test to verify it can mount oci artifact.
- Description for the changelog

Enabled OCI Artifact Mount

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.

@bitoku bitoku changed the title Revert "OCPNODE-3173: Disable OCI artifact mount by default." OCPNODE-4049: Revert "OCPNODE-3173: Disable OCI artifact mount by default." Feb 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 24, 2026 •
edited by openshift-ci bot
Loading

@bitoku: This pull request references OCPNODE-4049 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This reverts commit d21d404

- What I did
Fixes https://issues.redhat.com/browse/OCPNODE-4049
- How to verify it
with downstream e2e test to verify it can mount oci artifact.
- Description for the changelog

Enabled OCI Artifact Mount

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 QiWang19 and wgahnagl February 24, 2026 11:26
@haircommander
Copy link
Copy Markdown
Member

haircommander commented Mar 11, 2026

with downstream e2e test to verify it can mount oci artifact.

does this exist yet or is it planned after?

@bitoku
Copy link
Copy Markdown
Contributor Author

bitoku commented Mar 11, 2026

@haircommander
planned after. Because to pass the e2e, CRI-O must support it first.
However I'm open to suggestions if there's any other good way

@bitoku
Copy link
Copy Markdown
Contributor Author

bitoku commented Mar 11, 2026

I'm not super worried because upstream CRI-O has artifact integration tests already.

@haircommander
Copy link
Copy Markdown
Member

haircommander commented Mar 11, 2026

/lgtm
/approve
/verified later @bitoku

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Mar 11, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Mar 11, 2026

@haircommander: This PR has been marked to be verified later by @bitoku.

Details

In response to this:

/lgtm
/approve
/verified later @bitoku

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 Indicates that a PR is ready to be merged. label Mar 11, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bitoku, haircommander

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 Mar 11, 2026
@bitoku
Copy link
Copy Markdown
Contributor Author

bitoku commented Mar 11, 2026

/retest

2 similar comments
@bitoku
Copy link
Copy Markdown
Contributor Author

bitoku commented Mar 11, 2026

/retest

@bitoku
Copy link
Copy Markdown
Contributor Author

bitoku commented Mar 11, 2026

/retest

@djoshy
Copy link
Copy Markdown
Contributor

djoshy commented Mar 12, 2026

/override ci/prow/e2e-gcp-op-part2 ci/prow/hypershift

failures are unrelated

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 12, 2026

@djoshy: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/hypershift

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • ci/prow/bootstrap-unit
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-upgrade
  • ci/prow/e2e-gcp-op-1of2
  • ci/prow/e2e-gcp-op-2of2
  • ci/prow/e2e-gcp-op-ocl
  • ci/prow/e2e-gcp-op-ocl-part1
  • ci/prow/e2e-gcp-op-ocl-part2
  • ci/prow/e2e-gcp-op-part1
  • ci/prow/e2e-gcp-op-part2
  • ci/prow/e2e-gcp-op-single-node
  • ci/prow/e2e-hypershift
  • ci/prow/images
  • ci/prow/okd-scos-images
  • ci/prow/security
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-machine-config-operator-main-bootstrap-unit
  • pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn
  • pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn-upgrade
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-ocl
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-ocl-part1
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-ocl-part2
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-part1
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-part2
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-single-node
  • pull-ci-openshift-machine-config-operator-main-e2e-hypershift
  • pull-ci-openshift-machine-config-operator-main-images
  • pull-ci-openshift-machine-config-operator-main-okd-scos-images
  • pull-ci-openshift-machine-config-operator-main-security
  • pull-ci-openshift-machine-config-operator-main-unit
  • pull-ci-openshift-machine-config-operator-main-verify
  • pull-ci-openshift-machine-config-operator-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override ci/prow/e2e-gcp-op-part2 ci/prow/hypershift

failures are unrelated

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.

@djoshy
Copy link
Copy Markdown
Contributor

djoshy commented Mar 12, 2026

/override ci/prow/e2e-gcp-op-part2 ci/prow/e2e-hypershift

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 12, 2026

@djoshy: Overrode contexts on behalf of djoshy: ci/prow/e2e-gcp-op-part2, ci/prow/e2e-hypershift

Details

In response to this:

/override ci/prow/e2e-gcp-op-part2 ci/prow/e2e-hypershift

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 12, 2026

@bitoku: 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 fd1a0c2 into openshift:main Mar 12, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@QiWang19 QiWang19 Awaiting requested review from QiWang19

@wgahnagl wgahnagl Awaiting requested review from wgahnagl

Assignees

@haircommander haircommander

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@bitoku @openshift-ci-robot @haircommander @djoshy