-
Notifications
You must be signed in to change notification settings - Fork 143
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
Bonsai asset deployment failing #385
Comments
Are we sure it silently failed? It created the 18.5.0 release. However, when asking Bonsai to recompile releases, it fails because the .bonsai.yml and the release assets actually created do not line up. I had already submitted a fix to .bonsai.yml that has not been released. |
@majormoses this should be fixed if we merge #386 , cut a new release and then have Bonsai recompile releases. |
@nixwiz thanks for the PR I will get that this evening if possible. |
I have cut a release and am waiting for travis to publish the artifacts. |
I am not sure this is fixed, I see the ruby gem published but looks like its failing to compile for bonsai asset. |
I see a couple errors in the travis output: |
@nixwiz @majormoses Any update here? Is it safe to install v18.6.0 if Bonsai is complaining about compilation errors? |
Answered my own question, 18.5.0 and 18.6.0 will not install. 18.4.0 does: > sensuctl asset add sensu-plugins/sensu-plugins-aws -r sensu-plugins-aws
no version specified, using latest: 18.6.0
fetching bonsai asset: sensu-plugins/sensu-plugins-aws:18.6.0
Error: error putting resource #0 with name "sensu-plugins-aws" and namespace "default" (/api/core/v2/namespaces/default/assets/sensu-plugins-aws): resource is invalid: SHA-512 checksum cannot be empty
> sensuctl asset add sensu-plugins/sensu-plugins-aws:18.5.0 -r sensu-plugins-aws
fetching bonsai asset: sensu-plugins/sensu-plugins-aws:18.5.0
Error: error putting resource #0 with name "sensu-plugins-aws" and namespace "default" (/api/core/v2/namespaces/default/assets/sensu-plugins-aws): resource is invalid: SHA-512 checksum cannot be empty
> sensuctl asset add sensu-plugins/sensu-plugins-aws:18.4.0 -r sensu-plugins-aws
fetching bonsai asset: sensu-plugins/sensu-plugins-aws:18.4.0
added asset: sensu-plugins/sensu-plugins-aws:18.4.0
You have successfully added the Sensu asset resource, but the asset will not get downloaded until
it's invoked by another Sensu resource (ex. check). To add this runtime asset to the appropriate
resource, populate the "runtime_assets" field with ["sensu-plugins-aws"]. |
This is still broken. Any word? |
@jsnod I got them to fix 18.5.0 two days ago. 18.6.0 is still broken as of now. |
Per discussion in #348 (comment), it appears that the Bonsai asset deploy is silently failing: https://travis-ci.org/github/sensu-plugins/sensu-plugins-aws/jobs/643238482#L5268
That means that Bonsai is stuck at v18.4.0, so users are unable to install v18.5.0 via
sensuctl asset add sensu-plugins/sensu-plugins-aws
There are some fixes in v18.5.0 that I need in a brand new Sensu Go install, so it would be great to get the latest version pushed up to Bonsai.
/cc @majormoses @jspaleta
The text was updated successfully, but these errors were encountered: