You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we deployed a new microbosh using bosh-init. The installation works really well, thank you for building this great tool.
After we finished the installation we tried to upload a new stemcell and got the following error:
Started update stemcell > Verifying stemcell manifest. Done (00:00:00)
Started update stemcell > Checking if this stemcell already exists. Done (00:00:00)
Started update stemcell > Uploading stemcell bosh-aws-xen-ubuntu-trusty-go_agent/3012 to the cloud. Failed: Unable to copy stemcell root image: command 'sudo -n /var/vcap/packages/bosh_aws_cpi/gem_home/ruby/1.9.1/gems/bosh_aws_cpi-1.2981.0/scripts/stemcell-copy.sh /var/vcap/data/tmp/director/stemcell20150709-25924-fq60fb/image /dev/xvdg 2>&1' failed with exit code 1 (00:00:40)
Error 100: Unable to copy stemcell root image: command 'sudo -n /var/vcap/packages/bosh_aws_cpi/gem_home/ruby/1.9.1/gems/bosh_aws_cpi-1.2981.0/scripts/stemcell-copy.sh /var/vcap/data/tmp/director/stemcell20150709-25924-fq60fb/image /dev/xvdg 2>&1' failed with exit code 1
Task 6 error
The problem was, the sudo is requiring a password.
$ sudo -l
Matching Defaults entries for vcap on 84bc124e-0c15-45f8-7b08-ed8e72b83a3f:
!lecture, tty_tickets, !fqdn
User vcap may run the following commands on 84bc124e-0c15-45f8-7b08-ed8e72b83a3f:
(ALL) ALL
(root) NOPASSWD: /var/vcap/jobs/director/bin/stemcell-copy
Is there already a solution for this issue (except of ssh in to the microbosh and fix sudo)?
From my perspective it is quiet hard to fix the sudoers file, since the path to the script is generated including version numbers. Any ideas?
Cheers
Johannes
The text was updated successfully, but these errors were encountered:
Solved this for bosh-init by using the latest AWS CPI release, which includes the fix. Change bosh.yml lines 9 and 10 to use v=28 instead of v=27. Change sha1 to c7ce03393ebedd87a860dc609758ddb9654360fa.
Hi,
we deployed a new microbosh using bosh-init. The installation works really well, thank you for building this great tool.
After we finished the installation we tried to upload a new stemcell and got the following error:
The problem was, the sudo is requiring a password.
Is there already a solution for this issue (except of ssh in to the microbosh and fix sudo)?
From my perspective it is quiet hard to fix the sudoers file, since the path to the script is generated including version numbers. Any ideas?
Cheers
Johannes
The text was updated successfully, but these errors were encountered: