Compilation fails about cf-riak-cs-release HOT 10 CLOSED

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/84369804.

from cf-riak-cs-release.

Recent bosh directors became stricter by fixing a long standing bug regarding package dependencies. It seems that riak-cs package does not include git as a dependency in its spec file (packages/riak-cs/spec) and it should.

I'll let the services team know about the problem tomorrow but meanwhile you can modify the spec file and use a dev release. May be even PR with the change?

-dmitriy

On Dec 11, 2014, at 1:57 AM, adun153 [email protected] wrote:

Release: cf-riak-cs 6+dev.1* 273e00a
Stemcells: bosh-aws-xen-ubuntu-trusty-go_agent 2719.3* ami-134c6141

set +x /bin/sh: 1: git: not found /bin/sh: 1: git: not found dirname: missing operand Try 'dirname --help' for more information. /usr/bin/env: escript: No such file or directory make: **\* [deps] Error 127

What is causing this error? I see the git package being uploaded when I upload the release.
—
Reply to this email directly or view it on GitHub.

from cf-riak-cs-release.

Ok, I went to packages/riak-cs/spec, and now it looks like this:

---
name: riak-cs
dependencies:
- riak
- git
files:
- riak-cs/riak-cs-1.4.4.tar.gz

I created the release, uploaded it, did a bosh deploy, now it spits out the following errors:

Started compiling packages > riak-cs/98ce76ae32266350dcb99c8d996abbf27cc18c86. Failed: Action Failed get_task: Task 4284bc86-55d8-427e-775d-3f5bc4211e00 result: Compiling package riak-cs: Running packaging script: Command exited with 2; Stdout: , Stderr: + set -u
+ set +x
fatal: Not a git repository (or any parent up to mount point /var/vcap/data)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /var/vcap/data)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
dirname: missing operand
Try 'dirname --help' for more information.
/usr/bin/env: escript: No such file or directory
make: *** [deps] Error 127
 (00:01:20)

Error 450001: Action Failed get_task: Task 4284bc86-55d8-427e-775d-3f5bc4211e00 result: Compiling package riak-cs: Running packaging script: Command exited with 2; Stdout: , Stderr: + set -u
+ set +x
fatal: Not a git repository (or any parent up to mount point /var/vcap/data)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /var/vcap/data)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
dirname: missing operand
Try 'dirname --help' for more information.
/usr/bin/env: escript: No such file or directory
make: *** [deps] Error 127

from cf-riak-cs-release.

@adun153 the git error messages are misleading. @cppforlife describes the underlying problem correctly - recent bosh directors explicitly require packages. However the package that you'll need to add is not git but erlang. This change was made a couple of months ago (see this commit).

Given that you don't have the above commit, and also that you're using riak-cs/riak-cs-1.4.4.tar.gz instead of the more recent riak-cs/riak-cs-1.5.0.tar.gz it looks like you might be out of date. Try updating from the master branch and let us know if this fixes your issue.

Thanks,
Rob Dimsdale
CF Services

from cf-riak-cs-release.

I'll give it a try. I was working from a v6 checkout.

from cf-riak-cs-release.

same issue with a v6 checkout, with bosh 124
Started compiling packages > riak-cs/e364eb7a465df8bfb0555d3a4d1c079ca55516cf. Failed: Action Failed get_task: Task bf48f2f2-370d-4479-5527-c51c77b60ca2 result: Compiling package riak-cs: Running packaging script: Command exited with 2; Stdout: , Stderr: + set -u

• set +x
  /bin/sh: 1: git: not found
  /bin/sh: 1: git: not found
  dirname: missing operand
  Try 'dirname --help' for more information.
  /usr/bin/env: escript: No such file or directory
  make: *** [deps] Error 127

from cf-riak-cs-release.

Hi @poblin-orange. As mentioned above, try again from the master branch - these issues should be fixed.

Thanks
Rob Dimsdale
CF Services

from cf-riak-cs-release.

works on master thx
Pierre

from cf-riak-cs-release.

Just to be sure: I have to create my own release here, right?‎ Because I switched to masater, I'm at HRAD, uploaded release cf-riak-cs-6.yml, still getting the "git" error.I double-checked, I do have "erlang" as a requirement, and "riak-cs-1.5.0.tar.gz" in the spec file.So, I have to create my own release, and not use the cf-riak-cs-6.yml release? Sent from my Blackberry 10 Smartphone. From: Rob DimsdaleSent: Friday, December 12, 2014 22:41To: cloudfoundry/cf-riak-cs-releaseReply To: cloudfoundry/cf-riak-cs-releaseCc: adun153Subject: Re: [cf-riak-cs-release] Compilation fails (#19)Hi @poblin-orange. As mentioned above, try again from the master branch - these issues should be fixed.

Thanks
Rob Dimsdale
CF Services

—Reply to this email directly or view it on GitHub.

from cf-riak-cs-release.

@adun153 that is correct for the time being. To obtain the latest fixes in the master branch you will need to create your own dev release. While the git issues do not cause the deploy to fail, they are misleading, and we have created a story to fix these:(https://www.pivotaltracker.com/story/show/84482222).

If you look in our Pivotal Tracker project (https://www.pivotaltracker.com/n/projects/969486) then about half-way down the backlog you can see a release marker for Riak CS can be deployed with cf-release - this release marker will correspond to the next final release and at this point the features and bug fixes will be available without needing to create a dev release.

@shalako may be able to provide further clarification.

As the master branch contains fixes to this issue, I'm going to mark this as closed.

Thanks,
Rob Dimsdale and @asimrp
CF Services

from cf-riak-cs-release.