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

Bonsai asset deployment failing #385

Open
jsnod opened this issue Dec 21, 2020 · 11 comments · Fixed by #386
Open

Bonsai asset deployment failing #385

jsnod opened this issue Dec 21, 2020 · 11 comments · Fixed by #386
Assignees

Comments

@jsnod
Copy link

jsnod commented Dec 21, 2020

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

@nixwiz
Copy link
Contributor

nixwiz commented Dec 29, 2020

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.

@nixwiz nixwiz mentioned this issue Dec 29, 2020
7 tasks
@nixwiz
Copy link
Contributor

nixwiz commented Dec 29, 2020

@majormoses this should be fixed if we merge #386 , cut a new release and then have Bonsai recompile releases.

@majormoses
Copy link
Member

@nixwiz thanks for the PR I will get that this evening if possible.

@majormoses
Copy link
Member

I have cut a release and am waiting for travis to publish the artifacts.

@majormoses
Copy link
Member

@majormoses
Copy link
Member

majormoses commented Jan 8, 2021

I am not sure this is fixed, I see the ruby gem published but looks like its failing to compile for bonsai asset.

image

@majormoses majormoses reopened this Jan 8, 2021
@majormoses
Copy link
Member

majormoses commented Jan 8, 2021

I see a couple errors in the travis output:

@jsnod
Copy link
Author

jsnod commented Jan 26, 2021

@nixwiz @majormoses Any update here? Is it safe to install v18.6.0 if Bonsai is complaining about compilation errors?

@jsnod
Copy link
Author

jsnod commented Jan 28, 2021

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"].

@edgan
Copy link

edgan commented Jul 12, 2021

This is still broken. Any word?

@edgan
Copy link

edgan commented Jul 14, 2021

@jsnod I got them to fix 18.5.0 two days ago. 18.6.0 is still broken as of now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants