Skip to content

Add openbolt plugin support#1249

Merged
bastelfreak merged 2 commits intotheforeman:masterfrom
bastelfreak:openbolt
Dec 12, 2025
Merged

Add openbolt plugin support#1249
bastelfreak merged 2 commits intotheforeman:masterfrom
bastelfreak:openbolt

Conversation

@bastelfreak
Copy link
Member

No description provided.

@bastelfreak bastelfreak force-pushed the openbolt branch 3 times, most recently from 70c6407 to 6c90db4 Compare November 29, 2025 17:44
@bastelfreak
Copy link
Member Author

Setting up foreman (3.16.2-1+ubuntu2204) ...
[DEPRECATED] The `--no-prune` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local no_prune 'true'`, and stop using this flag
[DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local path './vendor/'`, and stop using this flag
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
Bundler could not find compatible versions for gem "foreman-tasks":
  In Gemfile:
    foreman_openbolt (= 0.1.1) was resolved to 0.1.1, which depends on
      foreman-tasks (~> 11.0)

Could not find gem 'foreman-tasks (~> 11.0)', which is required by gem
'foreman_openbolt (= 0.1.1)', in any of the sources or in gems cached in
vendor/cache.
dpkg: error processing package foreman (--configure):
 installed foreman package post-installation script subprocess returned error exit status 6
dpkg: dependency problems prevent configuration of ruby-foreman-openbolt:
 ruby-foreman-openbolt depends on foreman (>= 3.4.0~rc1); however:
  Package foreman is not configured yet.

@bastelfreak
Copy link
Member Author

I'm checking if the dependency is intentional

@bastelfreak
Copy link
Member Author

@bastelfreak
Copy link
Member Author

@ekohl the openbolt integration is working now. The acceptance tests fail because some other plugins are broken since a few days/weeks (mostly dynflow). Can we still merge this or do those plugins need to be fixed first? (if not too late, I would love to get this merged soonish so we can maybe get it into foreman 3.17).

Copy link
Member

@evgeni evgeni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK once CI is green

@bastelfreak bastelfreak force-pushed the openbolt branch 2 times, most recently from 98f96bf to eb50528 Compare December 11, 2025 16:26
@bastelfreak
Copy link
Member Author

When running this locally, I get:

  Info: Foreman::Dynflow::Pool[worker]: Scheduling refresh of Foreman::Dynflow::Worker[worker]


  Error: Systemd start for foreman failed!
  journalctl log for foreman:
  Dec 11 16:48:32 ubuntu2204-64-1 foreman[10640]: => Booting Puma
  Dec 11 16:48:32 ubuntu2204-64-1 foreman[10640]: => Rails 7.0.10 application starting in production
  Dec 11 16:48:32 ubuntu2204-64-1 foreman[10640]: => Run `bin/rails server --help` for more startup options
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Enabling systemd notification integration
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] Puma starting in cluster mode...
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Puma version: 6.6.1 ("Return to Forever")
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Ruby version: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *  Min threads: 5
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *  Max threads: 5
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *  Environment: production
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *   Master PID: 10640
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *      Workers: 24
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] *     Restarts: (✔) hot (✖) phased (✖) refork
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Preloading application
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Activated unix:///run/foreman.sock
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] Use Ctrl-C to stop
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] Sending status to systemd every 1.0 sec
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] * Starting control server on unix:///usr/share/foreman/tmp/sockets/pumactl.sock
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]: [10950] WARNING hook before_worker_boot failed with exception (ThreadError) can't create Thread: Resource temporarily unavailable
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] - Worker 0 (PID: 10648) booted in 0.2s, phase: 0
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10640]: [10640] - Worker 1 (PID: 10650) booted in 0.2s, phase: 0
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]: /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]: /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `initialize'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]: : can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `new'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `create_with_logging_context'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `new'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `create_with_logging_context'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:436:in `new'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:436:in `new'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster/worker.rb:38:in `run'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:125:in `spawn_thread'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:71:in `block (2 levels) in initialize'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:70:in `times'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster.rb:230:in `worker'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:70:in `block in initialize'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10987]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster.rb:106:in `block in spawn_worker'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:69:in `synchronize'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/thread_pool.rb:69:in `initialize'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/server.rb:254:in `new'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/server.rb:254:in `run'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster/worker.rb:119:in `run'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster.rb:230:in `worker'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/puma-6.6.1/lib/puma/cluster.rb:106:in `block in spawn_worker'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/ffi-1.17.2/lib/ffi/ffi.rb:69:in `block in fork'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/activesupport-7.0.10/lib/active_support/fork_tracker.rb:20:in `block in fork'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/ffi-1.17.2/lib/ffi/ffi.rb:69:in `block in fork'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/ffi-1.17.2/lib/ffi/ffi.rb:67:in `fork'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/ffi-1.17.2/lib/ffi/ffi.rb:67:in `fork'
  Dec 11 16:48:34 ubuntu2204-64-1 foreman[10950]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/activesupport-7.0.10/lib/active_support/fork_tracker.rb:18:in `fork'
  Error: /Stage[main]/Foreman::Service/Service[foreman]/ensure: change from 'stopped' to 'running' failed: Systemd start for foreman failed!

@bastelfreak
Copy link
Member Author

another run:

  journalctl log for foreman:
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Booting Puma
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Rails 7.0.10 application starting in production
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Run `bin/rails server --help` for more startup options
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Enabling systemd notification integration
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Puma starting in cluster mode...
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Puma version: 6.6.1 ("Return to Forever")
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Ruby version: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Min threads: 5
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Max threads: 5
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Environment: production
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *   Master PID: 10637
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *      Workers: 24
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *     Restarts: (???) hot (???) phased (???) refork
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Preloading application
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Activated unix:///run/foreman.sock
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Use Ctrl-C to stop
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Sending status to systemd every 1.0 sec
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Starting control server on unix:///usr/share/foreman/tmp/sockets/pumactl.sock
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 0 (PID: 10646) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 1 (PID: 10648) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 2 (PID: 10651) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 3 (PID: 10657) booted in 0.21s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 4 (PID: 10665) booted in 0.2s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 5 (PID: 10670) booted in 0.2s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 6 (PID: 10676) booted in 0.19s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 7 (PID: 10683) booted in 0.19s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: E, [2025-12-11T17:28:04.324527 #10816] ERROR -- /connector-database-core: can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:24:in `start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:104:in `postgres_listen_start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:63:in `start_listening'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 8 (PID: 10693) booted in 0.18s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 9 (PID: 10703) booted in 0.17s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 10 (PID: 10718) booted in 0.16s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 11 (PID: 10729) booted in 0.15s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: E, [2025-12-11T17:28:04.326546 #10832] ERROR -- /connector-database-core: can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:24:in `start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:104:in `postgres_listen_start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:63:in `start_listening'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 12 (PID: 10749) booted in 0.14s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 13 (PID: 10766) booted in 0.13s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]: [10951] WARNING hook before_worker_boot failed with exception (ThreadError) can't create Thread: Resource temporarily unavailable
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 22 (PID: 10951) booted in 0.03s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]: /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `new'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `create_with_logging_context'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:436:in `new'
  Error: /Stage[main]/Foreman::Service/Service[foreman]/ensure: change from 'stopped' to 'running' failed: Systemd start for foreman failed!
  journalctl log for foreman:
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Booting Puma
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Rails 7.0.10 application starting in production
  Dec 11 17:28:00 ubuntu2204-64-1 foreman[10637]: => Run `bin/rails server --help` for more startup options
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Enabling systemd notification integration
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Puma starting in cluster mode...
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Puma version: 6.6.1 ("Return to Forever")
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Ruby version: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Min threads: 5
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Max threads: 5
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *  Environment: production
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *   Master PID: 10637
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *      Workers: 24
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] *     Restarts: (???) hot (???) phased (???) refork
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Preloading application
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Activated unix:///run/foreman.sock
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Use Ctrl-C to stop
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] Sending status to systemd every 1.0 sec
  Dec 11 17:28:03 ubuntu2204-64-1 foreman[10637]: [10637] * Starting control server on unix:///usr/share/foreman/tmp/sockets/pumactl.sock
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 0 (PID: 10646) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 1 (PID: 10648) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 2 (PID: 10651) booted in 0.22s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 3 (PID: 10657) booted in 0.21s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 4 (PID: 10665) booted in 0.2s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 5 (PID: 10670) booted in 0.2s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 6 (PID: 10676) booted in 0.19s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 7 (PID: 10683) booted in 0.19s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: E, [2025-12-11T17:28:04.324527 #10816] ERROR -- /connector-database-core: can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:24:in `start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:104:in `postgres_listen_start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:63:in `start_listening'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10816]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 8 (PID: 10693) booted in 0.18s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 9 (PID: 10703) booted in 0.17s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 10 (PID: 10718) booted in 0.16s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 11 (PID: 10729) booted in 0.15s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: E, [2025-12-11T17:28:04.326546 #10832] ERROR -- /connector-database-core: can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:24:in `start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:104:in `postgres_listen_start'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: /usr/share/foreman/vendor/ruby/3.0.0/gems/dynflow-1.9.3/lib/dynflow/connectors/database.rb:63:in `start_listening'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10832]: [ concurrent-ruby ]
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 12 (PID: 10749) booted in 0.14s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 13 (PID: 10766) booted in 0.13s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]: [10951] WARNING hook before_worker_boot failed with exception (ThreadError) can't create Thread: Resource temporarily unavailable
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10637]: [10637] - Worker 22 (PID: 10951) booted in 0.03s, phase: 0
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]: /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError)
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `new'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:471:in `create_with_logging_context'
  Dec 11 17:28:04 ubuntu2204-64-1 foreman[10951]:         from /usr/share/foreman/vendor/ruby/3.0.0/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:436:in `new'
  Notice: /Stage[main]/Foreman::Service/Service[foreman]: Triggered 'refresh' from 2 events

@bastelfreak
Copy link
Member Author

I can also reproduce the errors locally with beaker-vagrant

bastelfreak and others added 2 commits December 12, 2025 16:25
Co-authored-by: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>
@bastelfreak bastelfreak enabled auto-merge (rebase) December 12, 2025 15:26
@evgeni evgeni disabled auto-merge December 12, 2025 15:42
@evgeni evgeni enabled auto-merge (squash) December 12, 2025 15:42
@bastelfreak bastelfreak disabled auto-merge December 12, 2025 15:48
@bastelfreak bastelfreak enabled auto-merge (rebase) December 12, 2025 15:48
@bastelfreak bastelfreak merged commit 7891f7a into theforeman:master Dec 12, 2025
10 checks passed
@bastelfreak bastelfreak deleted the openbolt branch December 12, 2025 16:05
@ogajduse
Copy link
Member

I remember this was supposed to be included in 3.17.0. Ping me once we have all the pieces in place. I'll make sure we have this in 3.17.1.

@bastelfreak
Copy link
Member Author

Yes will do. After the module is released, I will add support for the plugin into the installer. Afterwards it can be released as 3.17.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants