Skip to content

Conversation

@martinszuc
Copy link
Contributor

@martinszuc martinszuc commented Oct 14, 2025

OCPBUGS-44235: Fix Helm chart installation with CA/TLS certificates

Fixes: https://issues.redhat.com/browse/OCPBUGS-44235

Problem

Helm chart installation fails when CA certificates or client TLS certificates are configured:

error locating chart: open /.cache/helm/repository/<hash>-index.yaml: no such file or directory

Browsing works. Installing fails.

Root Cause

Console uses Kubernetes CRDs for repository management, not Helm's repository cache. The code set chartPathOptions.RepoURL during authentication, forcing Helm to look for a cache at $HOME/.cache/helm/repository/. This cache doesn't exist in the console pod's read-only filesystem.

Solution

Remove chartPathOptions.RepoURL assignments. Helm downloads directly from URLs using CaFile, CertFile, and KeyFile without requiring repository cache.

Reproduction

See: https://github.com/openshift-helm/test-scenarios/tree/main/ca-certificate-test

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

@martinszuc: This pull request references Jira Issue OCPBUGS-44235, which is invalid:

  • expected the bug to target the "4.21.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.

Details

In response to this:

OCPBUGS-44235: Fix Helm chart installation with CA/TLS certificates

Fixes: https://issues.redhat.com/browse/OCPBUGS-44235

Problem

Helm chart installation fails when CA certificates or client TLS certificates are configured:

error locating chart: open /.cache/helm/repository/<hash>-index.yaml: no such file or directory

Browsing works. Installing fails.

Root Cause

Console uses Kubernetes CRDs for repository management, not Helm's repository cache. The code set chartPathOptions.RepoURL during authentication, forcing Helm to look for a cache at $HOME/.cache/helm/repository/. This cache doesn't exist in the console pod's read-only filesystem.

Solution

Remove chartPathOptions.RepoURL assignments. Helm downloads directly from URLs using CaFile, CertFile, and KeyFile without requiring repository cache.

Reproduction

See: https://github.com/openshift-helm/OCPBUGS-44235

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 14, 2025
@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. component/backend Related to backend needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 14, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

Hi @martinszuc. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@baijum
Copy link
Contributor

baijum commented Oct 15, 2025

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 15, 2025
@vikram-raj
Copy link
Member

/retest

Console uses Kubernetes CRDs to manage Helm repositories, not Helm's
repository cache. Setting chartPathOptions.RepoURL forced Helm to look
for a cache that doesn't exist in the console pod's read-only filesystem.

Remove RepoURL assignments and use direct URL downloads with CaFile,
CertFile, and KeyFile for authentication.

Fixes https://issues.redhat.com/browse/OCPBUGS-44235

Signed-off-by: Martin Szuc <mszuc@redhat.com>
Test that authentication setup does not set RepoURL and verify
chart downloads work with CA/TLS certificates.

Signed-off-by: Martin Szuc <mszuc@redhat.com>
@martinszuc martinszuc marked this pull request as ready for review October 16, 2025 13:01
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 16, 2025
@openshift-ci openshift-ci bot requested review from Leo6Leo and baijum October 16, 2025 13:02
@vikram-raj
Copy link
Member

/jira refresh

/cc @jhadvig

@openshift-ci openshift-ci bot requested a review from jhadvig October 16, 2025 13:11
@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 Oct 16, 2025
@openshift-ci-robot
Copy link
Contributor

@vikram-raj: This pull request references Jira Issue OCPBUGS-44235, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

/cc @jhadvig

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.

@baijum
Copy link
Contributor

baijum commented Oct 17, 2025

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 17, 2025
@baijum
Copy link
Contributor

baijum commented Oct 17, 2025

/hold

@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 Oct 17, 2025
@openshift-ci-robot
Copy link
Contributor

@martinszuc: This pull request references Jira Issue OCPBUGS-44235, which is valid.

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

In response to this:

OCPBUGS-44235: Fix Helm chart installation with CA/TLS certificates

Fixes: https://issues.redhat.com/browse/OCPBUGS-44235

Problem

Helm chart installation fails when CA certificates or client TLS certificates are configured:

error locating chart: open /.cache/helm/repository/<hash>-index.yaml: no such file or directory

Browsing works. Installing fails.

Root Cause

Console uses Kubernetes CRDs for repository management, not Helm's repository cache. The code set chartPathOptions.RepoURL during authentication, forcing Helm to look for a cache at $HOME/.cache/helm/repository/. This cache doesn't exist in the console pod's read-only filesystem.

Solution

Remove chartPathOptions.RepoURL assignments. Helm downloads directly from URLs using CaFile, CertFile, and KeyFile without requiring repository cache.

Reproduction

See: https://github.com/openshift-helm/test-scenarios/tree/test/ca-cert-server/ca-certificate-test

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.

@baijum
Copy link
Contributor

baijum commented Oct 28, 2025

/retest

Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

Thank you @martinszuc 👍 Change looks good ✌️
/hold cancel

@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 Nov 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: baijum, jhadvig, martinszuc

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

@baijum
Copy link
Contributor

baijum commented Nov 4, 2025

/verified by @baijum

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 4, 2025
@openshift-ci-robot
Copy link
Contributor

@baijum: This PR has been marked as verified by @baijum.

Details

In response to this:

/verified by @baijum

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.

webbnh

This comment was marked as outdated.

@openshift-merge-bot openshift-merge-bot bot merged commit 0b7b101 into openshift:main Nov 5, 2025
7 of 8 checks passed
@openshift-ci-robot
Copy link
Contributor

@martinszuc: Jira Issue Verification Checks: Jira Issue OCPBUGS-44235
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-44235 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

OCPBUGS-44235: Fix Helm chart installation with CA/TLS certificates

Fixes: https://issues.redhat.com/browse/OCPBUGS-44235

Problem

Helm chart installation fails when CA certificates or client TLS certificates are configured:

error locating chart: open /.cache/helm/repository/<hash>-index.yaml: no such file or directory

Browsing works. Installing fails.

Root Cause

Console uses Kubernetes CRDs for repository management, not Helm's repository cache. The code set chartPathOptions.RepoURL during authentication, forcing Helm to look for a cache at $HOME/.cache/helm/repository/. This cache doesn't exist in the console pod's read-only filesystem.

Solution

Remove chartPathOptions.RepoURL assignments. Helm downloads directly from URLs using CaFile, CertFile, and KeyFile without requiring repository cache.

Reproduction

See: https://github.com/openshift-helm/test-scenarios/tree/main/ca-certificate-test

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-11-05-234508

@martinszuc
Copy link
Contributor Author

/cherrypick release-4.18

@openshift-cherrypick-robot

@martinszuc: new pull request created: #15860

Details

In response to this:

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

@martinszuc
Copy link
Contributor Author

/cherrypick release-4.19

@openshift-cherrypick-robot

@martinszuc: new pull request created: #15861

Details

In response to this:

/cherrypick release-4.19

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.

@martinszuc
Copy link
Contributor Author

/cherrypick release-4.20

@openshift-cherrypick-robot

@martinszuc: new pull request created: #15862

Details

In response to this:

/cherrypick release-4.20

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. component/backend Related to backend 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants