Project

General

Profile

Actions

Bug #24992

closed

Uninitialized constant Excon (NameError)

Added by Ohad Levy over 5 years ago. Updated about 5 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

/home/foreman/git/foreman/lib/foreman/http_proxy/excon_connection_extension.rb:20:in `<top (required)>': uninitialized constant Excon (NameError)
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/dependencies/interlock.rb:14:in `block in loading'
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/concurrency/share_lock.rb:151:in `exclusive'
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/dependencies/interlock.rb:13:in `loading'
    from /home/foreman/git/foreman/lib/foreman/http_proxy.rb:64:in `<top (required)>'
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/dependencies/interlock.rb:14:in `block in loading'
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/concurrency/share_lock.rb:151:in `exclusive'
    from /home/foreman/gems/gems/activesupport-5.2.1/lib/active_support/dependencies/interlock.rb:13:in `loading'
    from /home/foreman/git/foreman/config/application.rb:62:in `<top (required)>'
    from /opt/rh/rh-ruby24/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/rh/rh-ruby24/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
    from ./script/dynflowd:69:in `block in <main>'
    from ./script/dynflowd:67:in `chdir'
    from ./script/dynflowd:67:in `<main>'

seeing this error on latest nightly

Actions #1

Updated by Lukas Zapletal over 5 years ago

  • Tracker changed from Bug to Support
  • Subject changed from uninitialized constant Excon (NameError) to Uninitialized constant Excon (NameError)
  • Status changed from New to Feedback

Cannot reproduce during start, is there anything I need to do in order to see this, e.g. VMWare action?

Actions #2

Updated by Ohad Levy over 5 years ago

  • Status changed from Feedback to New

are you actually starting dynflow ? its pretty easy to reproduce on production env?

Actions #3

Updated by Marek Hulán over 5 years ago

  • Tracker changed from Support to Bug
  • Status changed from New to Need more information

Just finished installing nightly from rpms. Where should I observe the error? Could you provide some reproducing steps? All seems operational. I can share the box if that helps.

Actions #4

Updated by Marek Hulán over 5 years ago

Given the nature of the bug, listing deps version you have might help, IIRC this feature relies on fog and rest client to monkey patch some code. It may be that I can't reproduce since I use gems we package, your setup seems to be from git. I don't see the error on my develop checkout in production evn with dynflow either though.

Actions #5

Updated by Anonymous over 5 years ago

I'm unsure if it's related, but I'm getting this with the current staging DEBs:

Sep 27 19:50:30 sledge dynflowd[829]: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- active_support/dependencies (LoadError)
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/share/foreman/config/boot.rb:7:in `<top (required)>'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/share/foreman/config/application.rb:4:in `<top (required)>'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/bin/dynflowd:69:in `block in <main>'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/bin/dynflowd:67:in `chdir'
Sep 27 19:50:30 sledge dynflowd[829]:         from /usr/bin/dynflowd:67:in `<main>'

Actions #6

Updated by Lukas Zapletal over 5 years ago

Ohad, good quality tickets please :-)

Michael, I think it's not related but this looks similar to the issue when we introduced Bootsnap and I was trying to boot it without bundler.

Actions #7

Updated by Marek Hulán about 5 years ago

  • Status changed from Need more information to Feedback
Actions

Also available in: Atom PDF