bosh create - package spec github path issues.

[saluru]

I'm trying to deploy Diego release in my local, as part of that i'm running bosh create , but some of the package spec file github path has been migrated and create release is failing.

bosh create release --force && quit
Syncing blobs...

Building DEV release

Release artifact cache: /Users/sumanaluru/.bosh/cache

Building license

Building license...
Using final version '861d82c0d9745784acfcd026ccf44e942579824a'

Building packages

Building acceptance-tests...
Using final version '2f54ad04d4f720d8e42ad802ca431677635902c8'
Downloading from blobstore (id=e2d9e686-0234-4c24-b0e9-ddf0278ab164)...

Building auctioneer...
Package 'auctioneer' has a glob that resolves to an empty file list: github.com/cloudfoundry-incubator/auctioneer/cmd/auctioneer/*.go

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/100708486.

[emalm]

Hi, @saluru,

Thanks for the report. Are you trying to deploy from the tip of the develop branch right now? Looks like the team might have forgotten to push some of the submodules on this commit. Creating a release works for me on the current master commit, though (version 0.1407.0).

Thanks again,
Eric, CF Runtime Diego PM

[Amit-PivotalLabs]

I have a different hypothesis @saluru, what happens if you run git submodule update --init src/github.com/cloudfoundry-incubator/auctioneer from the root of the diego-release repo? If you then try to create the release, do you get a bit further (you might see a different glob complaining about resolving to an empty list).

[saluru]

Hi @eric,

I will try with master , but i see you have same dead links in spec file (version 0.1407.0) which are giving 404 .

---

name: auctioneer

dependencies:

• golang_1.4

files:

• github.com/cloudfoundry-incubator/auctioneer/cmd/auctioneer/*.go # gosub

[saluru]

Hi @Amit-PivotalLabs

unknown90840df169fe:diego-release sumanaluru$ git submodule update --init src/github.com/cloudfoundry-incubator/auctioneer

fatal: reference is not a tree: 145bc488a656a5e15d233b7c0340551dc014b4af

Unable to checkout '145bc488a656a5e15d233b7c0340551dc014b4af' in submodule path 'src/github.com/cloudfoundry-incubator/auctioneer'

Amit i see what you are trying to tell, i dont see my local src is getting cloned, let do a fresh one and retry see if the issue resolve.

[saluru]

Hi @eric,

I tried using master, still got the same error . I'm following the instructions provided in diego-release.
If you observe its not just one package for all.

When i access GIT url in the browser its giving 404, but when i click from diego-release repo its going to Good One.

Problem URL in spec file: https://github.com/cloudfoundry-incubator/diego-acceptance-tests/assets/
Good One: https://github.com/cloudfoundry-incubator/diego-acceptance-tests/tree/master/assets/

Building packages

Building acceptance-tests...
Package 'acceptance-tests' has a glob that resolves to an empty file list: github.com/cloudfoundry-incubator/diego-acceptance-tests/assets/*/

[Amit-PivotalLabs]

@saluru, the Unable to checkout '145bc488a656a5e15d233b7c0340551dc014b4af' in submodule path 'src/github.com/cloudfoundry-incubator/auctioneer' error message jives with what @ematpl suggested, that some of the submodules had not been pushed up, by accident. If you don't have any work in progress in the diego-release repo, you can do the following:

git fetch origin
git checkout master
git reset --hard origin/master
./scripts/update

and then create release. The ./scripts/update will hydrate all your submodules which will be empty until you clone the diego-release repo and update/init the submodules. The ./scripts/update does that for you, and takes care of doing it recursively because some submodules might have their own submodules.

This should work on master because master has had a release built from it, from scratch. It is currently failing on develop because a submodule was accidentally not pushed when diego-release was bumped to change a submodule pointer.

[saluru]

Thank You @Amit-PivotalLabs & @ematpl that fixed the issue.