Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

bosh_cli 1.5.0.pre2 reports uninitialized constant Retryable::Methods (NameError) #67

Closed
resouer opened this Issue · 3 comments

2 participants

@resouer

bosh_cli 1.5.0.pre2 reports uninitialized constant Retryable::Methods (NameError)

GEM LIST:

archive-tar-minitar (0.5.2)
aws-sdk (1.8.3.1)
blobstore_client (1.5.0.pre2)
bosh_cli (1.5.0.pre2)
bosh_common (1.5.0.pre2)
builder (3.2.0)
bundler (1.3.1)
excon (0.19.5)
fog (1.9.0)
formatador (0.2.4)
highline (1.6.15)
httpclient (2.2.4)
json (1.7.7)
json_pure (1.7.7)
log4r (1.1.10)
mime-types (1.21)
multi_json (1.6.1)
net-scp (1.0.4)
net-ssh (2.6.6)
net-ssh-gateway (1.1.0)
netaddr (1.5.0)
nokogiri (1.5.6)
progressbar (0.9.2)
rake (10.0.3)
retryable (1.3.2)
ruby-atmos-pure (1.0.5)
ruby-hmac (0.4.0)
rubygems-bundler (1.1.1)
rvm (1.11.3.6)
terminal-table (1.4.5)
uuidtools (2.1.3)

RubyGems Environment:

  • RUBYGEMS VERSION: 1.8.25
  • RUBY VERSION: 1.9.3 (2013-02-22 patchlevel 392) [x86_64-linux]
  • INSTALLATION DIRECTORY: /home/boshcli/.rvm/gems/ruby-1.9.3-p392
  • RUBY EXECUTABLE: /home/boshcli/.rvm/rubies/ruby-1.9.3-p392/bin/ruby
  • EXECUTABLE DIRECTORY: /home/boshcli/.rvm/gems/ruby-1.9.3-p392/bin
  • RUBYGEMS PLATFORMS:
    • ruby
    • x86_64-linux
  • GEM PATHS:
    • /home/boshcli/.rvm/gems/ruby-1.9.3-p392
    • /home/boshcli/.rvm/gems/ruby-1.9.3-p392@global
  • GEM CONFIGURATION:
    • :update_sources => true
    • :verbose => true
    • :benchmark => false
    • :backtrace => false
    • :bulk_threshold => 1000
    • "install" => "--no-rdoc --no-ri"
    • "update" => "--no-rdoc --no-ri"
  • REMOTE SOURCES:
@pmenglund

Can you include the stacktrace?

@resouer

Sorry, I have destroyed that VM and use a stable bosh_cli gem. But I remember the error occurs at:
https://github.com/cloudfoundry/bosh/blob/master/bosh_common/lib/common/common.rb#L8
and it's a normal uninitialized constant error even though I required the needed gems. I'm not sure whether it is because my ENV is corrupted.

@pmenglund

This should have been fixed by a change I made, but if it shows up again, just reopen the issue...

@pmenglund pmenglund closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.