-
Notifications
You must be signed in to change notification settings - Fork 30
uninitialized constant Bosh::Registry::InstanceManager::Aws::AWS (NameError) #281
Comments
I'm sorry this project isn't maintained anymore :/ I'll mark it as such soon; sorry for wasting your time. On Sat, Jan 16, 2016 at 10:38 PM, Yohan Wadia notifications@github.com
|
Hi,
Im getting the following error when I run bosh-bootstrap deploy
/usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/lib/bosh/registry/instance_manager/aws.rb:43:in
'initialize': uninitialized constant Bosh::Registry::InstanceManager::Aws::AWS (NameError) from /usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/lib/bosh/registry/config.rb:35:in
new'from /usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/lib/bosh/registry/config.rb:35:in
configure' from /usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/lib/bosh/registry/runner.rb:8:in
initialize'from /usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/bin/bosh-registry:21:in
new' from /usr/local/share/ruby/gems/2.0/gems/bosh-registry-1.3177.0/bin/bosh-registry:21:in
<top (required)>'from /usr/local/bin/bosh-registry:23:in
load' from /usr/local/bin/bosh-registry:23:in
bosh-registry -c /tmp/d20160116-25380-r0sf4x/bosh_registry_yml20160116-25380-neprch
failed, exit status=1/usr/local/share/ruby/gems/2.0/gems/rake-10.5.0/lib/rake/file_utils.rb:66:in
block in create_shell_runner': Command failed with status (1): [bosh -n micro deploy --update-if-exists /r...] (RuntimeError) from /usr/local/share/ruby/gems/2.0/gems/rake-10.5.0/lib/rake/file_utils.rb:57:in
call'from /usr/local/share/ruby/gems/2.0/gems/rake-10.5.0/lib/rake/file_utils.rb:57:in
sh' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/cli/helpers/bundle.rb:18:in
block in run'from /usr/local/share/ruby/gems/2.0/gems/bundler-1.11.2/lib/bundler.rb:219:in
block in with_clean_env' from /usr/local/share/ruby/gems/2.0/gems/bundler-1.11.2/lib/bundler.rb:199:in
with_original_env'from /usr/local/share/ruby/gems/2.0/gems/bundler-1.11.2/lib/bundler.rb:205:in
with_clean_env' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/cli/helpers/bundle.rb:16:in
run'from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/microbosh.rb:54:in
block in deploy_or_update' from /usr/share/ruby/2.0/fileutils.rb:125:in
chdir'from /usr/share/ruby/2.0/fileutils.rb:125:in
cd' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/microbosh.rb:52:in
deploy_or_update'from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/microbosh.rb:42:in
block in deploy' from /usr/share/ruby/2.0/fileutils.rb:125:in
chdir'from /usr/share/ruby/2.0/fileutils.rb:125:in
cd' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/microbosh.rb:40:in
deploy'from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/cli/commands/deploy.rb:77:in
perform_microbosh_deploy' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/cli/commands/deploy.rb:24:in
perform'from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/lib/bosh-bootstrap/thor_cli.rb:11:in
deploy' from /usr/local/share/ruby/gems/2.0/gems/thor-0.19.1/lib/thor/command.rb:27:in
run'from /usr/local/share/ruby/gems/2.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in
invoke_command' from /usr/local/share/ruby/gems/2.0/gems/thor-0.19.1/lib/thor.rb:359:in
dispatch'from /usr/local/share/ruby/gems/2.0/gems/thor-0.19.1/lib/thor/base.rb:440:in
start' from /usr/local/share/ruby/gems/2.0/gems/bosh-bootstrap-0.18.1/bin/bosh-bootstrap:13:in
<top (required)>'from /usr/local/bin/bosh-bootstrap:23:in
load' from /usr/local/bin/bosh-bootstrap:23:in
'By the looks of it there seems to be some issue with the version of "aws-sdk".
here is the output of the gem list command:
aws-sdk (2.2.11, 2.2.0, 1.60.2)
aws-sdk-core (2.2.11, 2.2.0)
aws-sdk-resources (2.2.11, 2.2.0)
aws-sdk-v1 (1.60.2)
bosh_aws_cpi (2.1.0)
fog-aws (0.6.0)
I'm running this command from an AWS Linux AMI (amzn-ami-hvm-2015.09.1.x86_64-gp2 (ami-c9b572aa) in Tokyo.
The text was updated successfully, but these errors were encountered: