Cannot deploy microbosh stemcell 0.8.1 using HEAD bosh_deployer about bosh

[drnic]

Weird; almost looks like its trying to run stemcell-copy as a ruby script instead of sh

[drnic]

I reverted to the bosh_deployer gem and it follows a different flow on my 10.04 inception VM, because I get the following in my log:

falling back to using dd to copy stemcell

Which means it takes the 2nd path in this method https://github.com/cloudfoundry/bosh/blob/master/bosh_aws_cpi/lib/cloud/aws/cloud.rb#L538-L539

Whereas in the bug being raised, using HEAD, it follows the first path (unsuccessfully) https://github.com/cloudfoundry/bosh/blob/master/bosh_aws_cpi/lib/cloud/aws/cloud.rb#L533-L536

[drnic]

What changed with has_stemcell_copy(path)?

[drnic]

AARGH, bosh repo has no tags for gem releases :/

[drnic]

There is no obvious recent change around these methods via git blame. Only validate_options & initial_agent_settings seem to have been changed in 2013 (in bosh_aws_cpi's cloud.rb)

[pmenglund]

When it changed to the new format stemcell-copy was bundled in the deployer gem, so it is being run through a rubygems wrapper, so I guess your root user don't have ruby in its PATH.

[drnic]

Yes the root user has ruby in its path.

vcap$ ruby -v
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]
vcap$ sudo ruby -v
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

[cf-bosh]

The root cause of the issue is that the generated bin stub for the stemcell-copy script assumed the script was ruby when in fact it was bash. We worked around this and it is now be fixed in MASTER. We still require password-less sudo on the inception box so we can write out the stemcell AMI to the AWS EBS device. Luckily the amazon ubuntu AMI has this by default.

  - Alex (ajackson) and Sean (seansweda) 

[drnic]

password-less sudo sounds like an ok requirement; I'll test HEAD soon.