Skip to content
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

Improve error message when helm is missing #5498

tothegills opened this issue Apr 23, 2019 · 2 comments


Copy link

commented Apr 23, 2019

The enhancement

Provide a better error message when a package is being acquired from a helm feed but helm is missing. The current error message is confusing:

The step failed: Activity failed with error 'The package redis v6.4.5 could not be downloaded to the
package cache from Helm repository at after
making 1 attempts over a total of 4s. Make sure the package is pushed to the feed and try the
deployment again. For a detailed troubleshooting guide go to
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at
System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at
System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at
Octopus.Core.Packages.Helm.HelmCommandRunner.Invoke(String args, String dir, ILog log) at
Octopus.Core.Packages.Helm.HelmCommandRunner.Fetch(String url, String packageId, IVersion version, String directory, String username, String password, ILog log) at
Octopus.Core.Packages.Helm.HelmPackageFeed.DownloadPackageToLocalCache(String packageId, IVersion version, ITaskContext taskContext, LogContext logContext) at


@tothegills tothegills self-assigned this Apr 23, 2019
@tothegills tothegills closed this Apr 23, 2019
@octoreleasebot octoreleasebot added this to the 2019.4.5 milestone Apr 23, 2019

This comment has been minimized.

Copy link

commented Apr 23, 2019

Release Note: Improved error message when attempting to acquire helm charts but helm is missing


This comment has been minimized.

Copy link

commented Jul 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.