"bosh create release" fails because there is no recent tag in ruby-buildpack about ruby-buildpack

[squeedee]

That was a bad move on our behalf.
Thanks for pointing this out. We will fix this very shortly and let you know when it's done.

[squeedee]

I found no tags related to that SHA (2fc4ad8). It seems to me that bosh is tripping over the lack of any tags.

There is now 1 tag referencing our 1.0.0 release. I hope that the presence of this tag solves your issue.

We have no trouble locally releasing from the 172 tag.

[mkocher]

Thanks @squeedee for responding so quickly.

I looked into this a little since I was concerned that we were pulling stuff down in the pre_packaing script. We're not, the pre_packaging script is just trying to put the current tag into a plain text file in the buildpack. Since we switched to versioned binaries for buildpacks this was only an issue for old releases.

[nota-ja]

I'm sorry I didn't write how to reproduce this issue.

cd /tmp
git clone https://github.com/cloudfoundry/cf-release.git
cd cf-release/
git checkout v172
git submodule sync; git submodule update --init --recursive
bosh create release --force

It doesn't occur when we use a release already created (because it occurs while building packages).
So please try to reproduce it with just adding --force option when creating release.
You would see the isssue still remains.

[drich10]

@nota-ja Per @mkocher, this is a known problem. The solution is to just upload the existing v172 release:

$ bosh upload release releases/cf-172.yml

Thanks
@krishicks && @drich10
CF Community Pair