IFS 25R1 MT installtion error

Hi ​@AntSurajK ,

This looks like the Helm dependency update step is failing, not the actual MT deployment yet.

Please check the below points:

1. Verify the IFS Helm repository access from the same server/user running the installer:

helm repo list
helm repo update
helm search repo ifscloud

2. If you are using the JFrog API key/secret, try removing or renaming the existing jfrog-artifactory-api-key file under:

ifsroot\config\secrets

Then rerun the installer so it prompts again for the repository username/password/API key. A similar IFS Community case was resolved this way when the stored JFrog credential file was invalid/stale. (community.ifs.com)

3. Also check that the OS username/path used for installation does not contain spaces. Older MT installer failures happened because temp files were copied under a user path with spaces, which broke Helm commands. (community.ifs.com)

4. Run the failed command manually with debug, if possible:

helm dependency update <local ifs-cloud chart path> --debug

This should show the real error, for example authentication failure, unreachable repo, proxy/SSL issue, or missing dependency chart.

Most likely this is due to repository authentication/cache rather than Kubernetes itself, since the log says the repo update starts successfully but dependency update fails.

Hi ,

I tried with above suggestion but not worked. I have noticed as this is using local chart as it should use global chart for dependencies.

Any idea on this.

Hi ​@AntSurajK ,

Thanks for the update! Good catch on the local vs global chart — that's actually a useful clue.

When it says 'Using local chart', Helm still needs to pull the sub-chart dependencies from remote repositories defined in the Chart.yaml. So if any of those repo URLs aren't reachable or aren't registered in Helm, it'll fail exactly like this — silently retrying until it gives up.

The quickest way to find the real error is to run the dependency update manually with debug flag:

helm dependency update <path-to-local-ifs-cloud-chart> --debug

This will tell you exactly what's failing — whether it's an auth issue, a missing repo, SSL, proxy, or something else. The logs in the installer don't show that detail unfortunately.

Also worth checking:
- Run 'helm repo list' and compare those URLs against the 'dependencies:' section in your local Chart.yaml — if any repo URL is missing, that's your culprit
- Check if the charts/ subfolder inside the local chart directory is empty
- If you're behind a corporate proxy, try a direct curl to the dependency repo URL to see if it's even reachable

If you want to skip the local chart altogether, check your installer config for a USE_LOCAL_CHART flag and set it to false — that should make it pull everything directly from the ifscloud Helm repo instead.

Could you share the output of 'helm repo list' and the dependencies section from your Chart.yaml? That'll help narrow this down quickly.

Regards