Skip to content
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.

Command failed with status (1): [bosh -n micro deploy --update-if-exists /h...] (RuntimeError) #325

Closed
tintoverano opened this issue Dec 3, 2015 · 1 comment

Comments

@tintoverano
Copy link

hi,

I got almost to the end withfirstbosh creation, but then I got this error message:

  Started deploy micro bosh
  Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)
  Started deploy micro bosh > Uploading stemcell. Done (00:00:01)
  Started deploy micro bosh > Creating VM from ami-c8fbb9a2 light. Done (00:00:36)
  Started deploy micro bosh > Waiting for the agent. Done (00:01:51)
  Started deploy micro bosh > Updating persistent disk
  Started deploy micro bosh > Create disk. Done (00:00:08)
  Started deploy micro bosh > Mount disk. Done (00:00:17)
     Done deploy micro bosh > Updating persistent disk
  Started deploy micro bosh > Stopping agent services. Done (00:00:03)
  Started deploy micro bosh > Applying micro BOSH spec. Done (00:00:58)
  Started deploy micro bosh > Starting agent services. Done (00:00:07)
  Started deploy micro bosh > Waiting for the director. Done (00:00:15)log writing failed. can't be called from trap context

Please choose deployment first
~/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/rake/file_utils.rb:66:in `block in create_shell_runner': Command failed with status (1): [bosh -n micro deploy --update-if-exists /h...] (RuntimeError)

any ideas?

I can see the instance running at ec2

thanks,

zoltán

@tintoverano
Copy link
Author

after researching a bit (cloudfoundry/bosh#306) it turns out there's no problem

I could login to firstbosh after targeting the created instance

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant