Project

General

Profile

Actions

Bug #28941

closed

Failed running Dynflow daemon <TypeError> superclass mismatch for class Command

Added by Tom Ritserveldt about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Debian/Ubuntu
Target version:

Description

we keep seeing the following dynflowd error in our foreman production.log at least every minute.
https://gist.github.com/zipkid/a67ab97d276306d427bf694e24da03a3

It seems that these are both being called, and that causes the error:

    /usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
...
    /usr/share/foreman/vendor/ruby/2.3.0/gems/thor-1.0.1/lib/thor/command.rb:1:in `<top (required)>'

when editing `/usr/share/foreman/script/dynflowd`
and changing the shebang from:

#!/usr/bin/env ruby
to
#!/usr/bin/foreman-ruby

it seems to work properly after restarting dynflowd.

this is with foreman 1.24.2 on debian stretch.
Possibly a packaging issue?

Actions #1

Updated by Ewoud Kohl van Wijngaarden about 4 years ago

  • Project changed from Foreman to Packaging
  • Category set to Debian/Ubuntu
  • Target version set to 1.24.3
Actions #2

Updated by Lars Wagner about 4 years ago

Tom Ritserveldt wrote:

we keep seeing the following dynflowd error in our foreman production.log at least every minute.
https://gist.github.com/zipkid/a67ab97d276306d427bf694e24da03a3

It seems that these are both being called, and that causes the error:
[...]

when editing `/usr/share/foreman/script/dynflowd`
and changing the shebang from:
[...]to
[...]
it seems to work properly after restarting dynflowd.

this is with foreman 1.24.2 on debian stretch.
Possibly a packaging issue?

Got the same problem here on ubuntu 18.

Actions #3

Updated by The Foreman Bot about 4 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ewoud Kohl van Wijngaarden
  • Pull request https://github.com/theforeman/foreman-packaging/pull/4837 added
Actions #4

Updated by Ewoud Kohl van Wijngaarden about 4 years ago

  • Status changed from Ready For Testing to Closed

Since it's a stable branch-only, Redmine isn't importing the Closed commit so closing manually.

Actions #5

Updated by The Foreman Bot about 4 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/4841 added
Actions #6

Updated by Ewoud Kohl van Wijngaarden about 4 years ago

  • Fixed in Releases 1.23.2, 1.24.3 added
Actions

Also available in: Atom PDF