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

Issues After Installating Halyard #3763

Click2Cloud-neutron opened this Issue Dec 19, 2018 · 4 comments


None yet
5 participants
Copy link

Click2Cloud-neutron commented Dec 19, 2018

Issue Summary:

After Installing Halyard through script, It takes time to process and After Installing All packages and Finish with last output "Unknown"

So when we Check for Hal Version " hal -v"
It shows "Unknown"

screenshot 1


Cloud Provider(s):


Feature Area:


Steps to Reproduce:

Additional Details:

Please delete the instructions below this line prior to submitting



  • Issue Summary: A brief description of what you're seeing.
  • Cloud Provider: AWS, GCP, Kubernetes, Azure, Cloud Foundry, etc. Please assign a label from the right so your issue can be properly sorted.
  • Environment: As much information about your Spinnaker environment and configuration that might be relevant to the issue. For example: "I am running Spinnaker using the Amazon images to deploy into AWS and GCP."
  • Feature Area: Notifications, Pipelines, UI, Jenkins, etc. Please assign a label from the right so your issue can be properly sorted.
  • Description: The behavior you expect to see, and the actual behavior.
  • Steps to reproduce: Ideally, an isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem). If not possible, as much information as possible to see this behavior.
  • Additional Details: Additional information such as screenshots and exception logs.

This comment has been minimized.

Copy link

ezimanyi commented Dec 21, 2018

It looks like the hal -v command was broken by spinnaker/halyard#1089 though I haven't dug into exactly why or how to fix it. This shouldn't affect any other functionality of Halyard, though it's admittedly confusing that it doesn't report the version properly. @ttomsu @lwander


This comment has been minimized.

Copy link

bytesandwich commented Jan 2, 2019

the halyard installation steps prescribe this flag to check for proper installation:

Check whether Halyard was installed properly:

hal -v

If this command fails, make sure hal is in your $PATH, and check the logs under /var/log/spinnaker/halyard/halyard.log.

Might it be a good candidate for a CI test?


This comment has been minimized.

Copy link

lwander commented Jan 3, 2019

@spinnakerbot assign-issue @ttomsu


This comment has been minimized.

Copy link

ttomsu commented Jan 15, 2019

This is a duplicate of #3720

@ttomsu ttomsu closed this Jan 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment