bosh.io stemcell hashes are shown in md5 while bosh-init requires sha1
Closed this issue · 28 comments
When you include a new stemcell in your manifest, e.g. from http://bosh.io/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent you have to put the sha1 into your bosh-init manifest. However, the page only lists an md5 hash whereas for bosh releases sha1 hashes are listed.
I didn't find a way to specify manifest hashes as md5, so either this option should be added to bosh-init or the shown hashes on bosh.io should be in sha1.
We are planning to make our CI send sha1s to the bosh.io. Stay tuned.
Sent from my iPhone
On Aug 8, 2015, at 1:02 AM, Marco Voelz notifications@github.com wrote:
When you include a new stemcell in your manifest, e.g. from http://bosh.io/stemcells/bosh-openstack-kvm-ubuntu-trusty-go_agent you have to put the sha1 into your bosh-init manifest. However, the page only lists an md5 hash whereas for bosh releases sha1 hashes are listed.
I didn't find a way to specify manifest hashes as md5, so either this option should be added to bosh-init or the shown hashes on bosh.io should be in sha1.
—
Reply to this email directly or view it on GitHub.
+1
+1
+1
+15
Any ETA on when we can expect this?
Dmitriy, which repo is generating the wrong sha? Perhaps one of the +15 people can then PR a fix.
On Mon, Nov 2, 2015 at 10:52 PM, Geoff Franks notifications@github.com
wrote:
+15
Reply to this email directly or view it on GitHub:
#41 (comment)
+16
I need that, too.
It's not a repo per se but our jenkins pipelines dont produce and send sha1s to bosh.io. I'll bump this in priority.
I hate to pile on, but this would nice ;)
+1
+1
Just lost about 30 minutes to this.
+30
+1
+1
Pretty please can we have this in 2016?
@cppforlife can there be a tracker URL for this please so we can see if/where its in the backlog?
Yup. Here it is: https://www.pivotaltracker.com/story/show/112466887 as
part of the epic to move over to using concourse for stemcell generation.
On Tue, Jan 26, 2016 at 2:13 PM, Dr Nic Williams notifications@github.com
wrote:
@cppforlife https://github.com/cppforlife can there be a tracker URL
for this please so we can see if/where its in the backlog?—
Reply to this email directly or view it on GitHub
#41 (comment)
.
+1
Still not available?
7 months and still no fix?
+1. Please fix this issue. :)
+1: I'd like this to simplify the bosh-init instructions in https://github.com/cloudfoundry-incubator/diego-release/tree/develop/examples/aws#stubsbosh-initstemcellyml. I'd prefer for bosh.io to display the SHA checksums, so cloudfoundry/bosh-io-web#7 is also relevant.
+1. Come on, dawgs.
+1 please?
+1 Cough Cough ... Still Only See md5 on bosh.io
Dmitriy et al are working on this, but it's going to be a gradual migration of stem cells. To help ease the transition, http://stemcell-sha1s.starkandwayne.com/<stem cell name>/<version> will spit back the sha1 of the stemcell.
It only goes back to about 3215, but it is auto-updated as new stemcells come out.
For example:
curl -k http://stemcell-sha1s.starkandwayne.com//bosh-aws-xen-centos-7-go_agent/3232
No sha for stemcells makes me sad...
bosh.io will now show sha1s for 3262.2+ stemcells.