Skip to content

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Mar 20, 2025

OLMv1 uses containers/images/v5 which looks in the /etc/docker/certs.d directory for certificates used in image fetching. It is necessary for local registries as well as additional CAs specified in images.config.

- What I did
Added /etc/docker/certs.d to template

- How to verify it
Ensure /etc/docker/certs.d exists after cluster startup

- Description for the changelog
Add /etc/docker/certs.d to template

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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 Mar 20, 2025
@openshift-ci-robot
Copy link
Contributor

@tmshort: This pull request references Jira Issue OCPBUGS-52282, which is invalid:

  • expected the bug to target the "4.19.0" version, but no target version was set

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:

OLMv1 uses containers/images/v5 which looks in the /etc/docker/certs.d directory for certificates used in image fetching. It is necessary for local registries as well as additional CAs specified in images.config.

- What I did
Added /etc/docker/certs.d to template

- How to verify it
Ensure /etc/docker/certs.d exists after cluster startup

- Description for the changelog
Add /etc/docker/certs.d to template

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.

@tmshort
Copy link
Contributor Author

tmshort commented Mar 20, 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 Mar 20, 2025
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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.

@rphillips
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2025
@jianzhangbjz
Copy link

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 21, 2025
@tmshort
Copy link
Contributor Author

tmshort commented Mar 24, 2025

Still get https://issues.redhat.com/browse/OCPBUGS-48795, details: https://issues.redhat.com/browse/OCPBUGS-52282

This is expected due to the runlevel difference between OLM and MCO.

@tmshort
Copy link
Contributor Author

tmshort commented Mar 24, 2025

/retest-required

@tmshort tmshort changed the title OCPBUGS-52282: Add /etc/docker/certs.d to template OCPBUGS-54175: Add /etc/docker/certs.d to template Mar 24, 2025
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

In response to this:

OLMv1 uses containers/images/v5 which looks in the /etc/docker/certs.d directory for certificates used in image fetching. It is necessary for local registries as well as additional CAs specified in images.config.

- What I did
Added /etc/docker/certs.d to template

- How to verify it
Ensure /etc/docker/certs.d exists after cluster startup

- Description for the changelog
Add /etc/docker/certs.d to template

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.

@tmshort
Copy link
Contributor Author

tmshort commented Mar 24, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@tmshort: This pull request references Jira Issue OCPBUGS-54175, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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.

@tmshort
Copy link
Contributor Author

tmshort commented Mar 24, 2025

This can't be tested as part of OCPBUGS-52282, when it is backported to 4.18, it can then be tested with that bug.

@jianzhangbjz
Copy link

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-54175
/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 25, 2025
@tmshort
Copy link
Contributor Author

tmshort commented Mar 25, 2025

/retest-required

OLMv1 uses containers/images/v5 which looks in the /etc/docker/certs.d
directory for certificates used in image fetching. It is necessary for
local registries as well as additional CAs specified in images.config.

Signed-off-by: Todd Short <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2025
@tmshort
Copy link
Contributor Author

tmshort commented Mar 28, 2025

@rphillips can I get another LGTM? I rebased.

Copy link
Contributor

openshift-ci bot commented Mar 28, 2025

@tmshort: 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/e2e-azure-ovn-upgrade-out-of-change 2ed66e8 link false /test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-gcp-op-ocl 2ed66e8 link false /test e2e-gcp-op-ocl
ci/prow/okd-scos-e2e-aws-ovn 2ed66e8 link false /test okd-scos-e2e-aws-ovn

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.

@tmshort
Copy link
Contributor Author

tmshort commented Apr 7, 2025

ping @rphillips @dkhater-redhat @LorbusChris ?

@djoshy
Copy link
Contributor

djoshy commented Apr 8, 2025

/lgtm

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

openshift-ci bot commented Apr 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, rphillips, tmshort

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 Apr 8, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit ddc18e8 into openshift:main Apr 8, 2025
14 of 17 checks passed
@openshift-ci-robot
Copy link
Contributor

@tmshort: Jira Issue OCPBUGS-54175: All pull requests linked via external trackers have merged:

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

In response to this:

OLMv1 uses containers/images/v5 which looks in the /etc/docker/certs.d directory for certificates used in image fetching. It is necessary for local registries as well as additional CAs specified in images.config.

- What I did
Added /etc/docker/certs.d to template

- How to verify it
Ensure /etc/docker/certs.d exists after cluster startup

- Description for the changelog
Add /etc/docker/certs.d to template

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
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.19.0-202504090015.p0.gddc18e8.assembly.stream.el9.
All builds following this will include this PR.

@tmshort
Copy link
Contributor Author

tmshort commented Sep 30, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot

@tmshort: new pull request created: #5320

In response to this:

/cherry-pick release-4.18

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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.

7 participants