Skip to content

[release-4.18] OCPBUGS-55787: Fix containerd host.toml generation to work with mirrors using an org_name #2879

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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2799

/assign sebsoto

sebsoto added 4 commits May 6, 2025 18:22
Refactors the code to make the test code readable.
Allows handling of image registries given via https:// , docker:// ,
or any other scheme. Before this change the parsing of images given in
these formats would fail unexpectedly and quietly.
Fixes the logic when adding mirrors with an optional org_path.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-47696 has been cloned as Jira Issue OCPBUGS-55787. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-55787: Fix containerd host.toml generation to work with mirrors using an org_name

In response to this:

This is an automated cherry-pick of #2799

/assign sebsoto

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 changed the title [release-4.18] OCPBUGS-47696: Fix containerd host.toml generation to work with mirrors using an org_name [release-4.18] OCPBUGS-55787: Fix containerd host.toml generation to work with mirrors using an org_name May 6, 2025
@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 May 6, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-55787, 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". For more information you can reference the OpenShift Bug Process.

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.

In response to this:

This is an automated cherry-pick of #2799

/assign sebsoto

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 mansikulkarni96 and sebsoto May 6, 2025 18:22
@sebsoto
Copy link
Contributor

sebsoto commented May 6, 2025

/approve

@sebsoto
Copy link
Contributor

sebsoto commented May 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2025
Copy link
Contributor

openshift-ci bot commented May 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sebsoto

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:

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 May 6, 2025
@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/retest-required

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

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

In response to this:

/cherry-pick release-4.17

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/retest-required

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/override ci/prow/vsphere-proxy-e2e-operator

INFO[2025-05-07T13:45:26Z] Running step vsphere-proxy-e2e-operator-windows-e2e-operator-test.
INFO[2025-05-07T15:27:07Z] Step vsphere-proxy-e2e-operator-windows-e2e-operator-test succeeded after 1h41m40s.

Copy link
Contributor

openshift-ci bot commented May 7, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/vsphere-proxy-e2e-operator

In response to this:

/override ci/prow/vsphere-proxy-e2e-operator

INFO[2025-05-07T13:45:26Z] Running step vsphere-proxy-e2e-operator-windows-e2e-operator-test.
INFO[2025-05-07T15:27:07Z] Step vsphere-proxy-e2e-operator-windows-e2e-operator-test succeeded after 1h41m40s.

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/override ci/prow/nutanix-e2e-operator ci/prow/vsphere-disconnected-e2e-operator

Vsphere disconnected failed in the deletion test due to a known issue.

Copy link
Contributor

openshift-ci bot commented May 7, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/nutanix-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator

In response to this:

/override ci/prow/nutanix-e2e-operator ci/prow/vsphere-disconnected-e2e-operator

Vsphere disconnected failed in the deletion test due to a known issue.

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/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 May 7, 2025
@openshift-ci-robot
Copy link

@sebsoto: This pull request references Jira Issue OCPBUGS-55787, 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.18.z) matches configured target version for branch (4.18.z)
  • 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-47696 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-47696 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

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 openshift-ci bot requested a review from rrasouli May 7, 2025 23:02
@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/override ci/prow/vsphere-disconnected-e2e-operator

Copy link
Contributor

openshift-ci bot commented May 7, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/vsphere-disconnected-e2e-operator

In response to this:

/override ci/prow/vsphere-disconnected-e2e-operator

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 7, 2025

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

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

In response to this:

/cherry-pick release-4.17

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 8, 2025

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator ci/prow/platform-none-vsphere-e2e-operator ci/prow/vsphere-proxy-e2e-operator ci/prow/vsphere-e2e-operator ci/prow/wicd-unit-vsphere ci/prow/vsphere-disconnected-e2e-operator

Copy link
Contributor

openshift-ci bot commented May 8, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/aws-e2e-operator, ci/prow/azure-e2e-operator, ci/prow/azure-e2e-upgrade, ci/prow/gcp-e2e-operator, ci/prow/nutanix-e2e-operator, ci/prow/platform-none-vsphere-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator, ci/prow/vsphere-e2e-operator, ci/prow/vsphere-proxy-e2e-operator, ci/prow/wicd-unit-vsphere

In response to this:

/override ci/prow/aws-e2e-operator ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade ci/prow/gcp-e2e-operator ci/prow/nutanix-e2e-operator ci/prow/platform-none-vsphere-e2e-operator ci/prow/vsphere-proxy-e2e-operator ci/prow/vsphere-e2e-operator ci/prow/wicd-unit-vsphere ci/prow/vsphere-disconnected-e2e-operator

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-merge-bot openshift-merge-bot bot merged commit b1799dc into openshift:release-4.18 May 8, 2025
19 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-55787: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #2799

/assign sebsoto

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.

Copy link
Contributor

openshift-ci bot commented May 8, 2025

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/vsphere-disconnected-e2e-operator ca0fd0f link true /test vsphere-disconnected-e2e-operator
ci/prow/nutanix-e2e-operator ca0fd0f link true /test nutanix-e2e-operator

Full PR test history. Your PR dashboard.

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-cherrypick-robot
Copy link
Author

@sebsoto: new pull request created: #2891

In response to this:

/cherry-pick release-4.17

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.

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

3 participants