This repository was archived by the owner on Jan 5, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
When using compiled releases, an incorrect stemcell sha leads to a panic #70
Labels
Comments
@cppforlife any updates on this? |
@voelzmo that's weird. we do that ourselves in our tests. can you show me stemcell.MF and release.MF? |
Just to clarify, here is what I do:
I would expect Anyways, here is my
The |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When updating stemcells for a bosh-init deployment, I often just update the stemcell version in the manifest and have bosh-init tell me what the sha1 should be, so I don't have to download the same file twice. This doesn't work when using compiled releases with bosh-init.
I use bosh-init
version 0.0.81-775439c-2015-12-09T00:36:04Z
Steps to reproduce
Expected
An error message like this one
Actual
bosh-init output is pretty silent
And the debug log shows a panic happening
The text was updated successfully, but these errors were encountered: