README.md for microsoft/azure-industrial-iot chart Not Found (404)

[karok2m]

GET for https://hub.helm.sh/api/chartsvc/v1/assets/microsoft/azure-industrial-iot/versions/0.2.0/README.md returns 404 and the microsoft/azure-industrial-iot chart page in Helm Hub keeps showing as loading.

I have seen #225, where the suggestion was that this might be caused by the relative urls in index.yaml file. But this is true for all charts in microsoft repository and the other charts are loading correctly, see bellow for examples. So I am not sure that that suggestion is relevant here as well.

• microsoft/cognitive-services-speech-onpremise
• microsoft/spark

Here is excerpt from https://microsoft.github.io/charts/repo/index.yaml:

apiVersion: v1
entries:
  azure-industrial-iot:
  - apiVersion: v2
    appVersion: 2.6.104
    ...
    urls:
    - azure-industrial-iot/azure-industrial-iot-0.2.0.tgz
    version: 0.2.0
  - apiVersion: v2
    appVersion: 2.5.2
    ...
    urls:
    - azure-industrial-iot/azure-industrial-iot-0.1.0.tgz
    version: 0.1.0
  cognitive-services-speech-onpremise:
  - apiVersion: v1
    appVersion: 0.1.1
    ...
    urls:
    - cognitive-services-speech/cognitive-services-speech-onpremise-0.1.1.tgz
    version: 0.1.1
  spark:
  - apiVersion: v1
    appVersion: 2.4.0
    ...
    urls:
    - spark/spark-1.0.0.tgz
    version: 1.0.0

And GETs on https://microsoft.github.io/charts/repo/azure-industrial-iot/azure-industrial-iot-0.2.0.tgz and https://microsoft.github.io/charts/repo/azure-industrial-iot/azure-industrial-iot-0.1.0.tgz do return 200.

I am the maintainer of azure-industrial-iot chart, so if the problem is caused by the chart itself then I can fix it on that side.

[mattfarina]

@karok2m I think I know what happened here.

The quick fix, please update to Helm 3.1.2 and repackage. In the changelog you'll see the fix as "Fixing issue where archives created on windows have broken paths".

This looks like the chart was packaged with Helm 3 on Windows. This was causing path issues. For example, on POSIX systems instead of extracting a directory structure when decompressing it's extracting file names with \\ as part of the name.

Please let us know if this works.

[karok2m]

@mattfarina, thanks a lot for the tip. It fixed the error with README.md. Closing the issue as it is resolved.