Error 500 importing ansible roles by UI

Support
,
1

Problem:

“Failed to import roles and variables Error: Request failed with status code 500” importing ansible roles

Expected outcome:

Foreman and Proxy versions:

foreman-proxy-3.16.0-1.el9.noarch

Foreman and Proxy plugin versions:

foreman-release-3.16.0-1.el9

foreman-proxy-3.16.0-1.el9

Distribution and version:

Rocky Linux 9.

Other relevant data:

This is a fresh install on Rocky Linux 9.6 and my first experience with foreman, maybe that have forgot to install somethighs?
This is the list of packages installed:
foreman-release-3.16.0-1.el9.noarch
foreman-installer-3.16.0-1.el9.noarch
foreman-selinux-3.16.0-1.el9.noarch
foreman-3.16.0-1.el9.noarch
foreman-postgresql-3.16.0-1.el9.noarch
foreman-service-3.16.0-1.el9.noarch
foreman-dynflow-sidekiq-3.16.0-1.el9.noarch
foreman-redis-3.16.0-1.el9.noarch
foreman-proxy-3.16.0-1.el9.noarch
rubygem-hammer_cli_foreman-3.16.0-1.el9.noarch
foreman-cli-3.16.0-1.el9.noarch
ansible-collection-theforeman-foreman-5.6.0-1.el9.noarch
rubygem-hammer_cli_foreman_tasks-0.0.24-1.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_remote_execution-0.3.4-1.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_ansible-0.8.1-1.fm3_16.el9.noarch
rubygem-hammer_cli_foreman_puppet-0.1.1-1.fm3_15.el9.noarch
rubygem-foreman_puppet-9.0.0-1.fm3_16.el9.noarch
rubygem-foreman-tasks-11.0.5-1.fm3_16.el9.noarch
rubygem-foreman_remote_execution-16.2.3-1.fm3_16.el9.noarch
rubygem-foreman_ansible-17.0.2-1.fm3_16.el9.noarch
rubygem-foreman_templates-10.0.10-1.fm3_16.el9.noarch

many thank's guys
2

What do the logs at /var/log/foreman/production.log and /var/log/foreman-proxy/proxy.log say?

3

Hi,thank’s by quickly reply.
In the meantime i’m tryed to reinstall step-by-step the system but the result seems the same. I’ve installed foreman base then went to add ansible support but the issues persists. I’ve done it by:
foreman-installer --enable-foreman-plugin-remote-execution --enable-foreman-plugin-ansible --enable-foreman-proxy-plugin-ansible

Here the log when i’m going to import the roles by UI:
2025-10-31T22:22:58 [I|app|e453397b] Started POST “/ansible/ansible_roles/confirm_import” for 172.20.1.1 at 2025-10-31 22:22:58 +0100
2025-10-31T22:22:58 [I|app|e453397b] Processing by AnsibleRolesController#confirm_import as JSON
2025-10-31T22:22:58 [I|app|e453397b] Parameters: {“changed”=>{“new”=>{“geerlingguy.nginx”=>{“id”=>nil, “name”=>“geerlingguy.nginx”, “created_at”=>nil, “updated_at”=>nil}, “rl9-install-httpd”=>{“id”=>nil, “name”=>“rl9-install-httpd”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.activation_keys”=>{“id”=>nil, “name”=>“theforeman.foreman.activation_keys”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.auth_sources_ldap”=>{“id”=>nil, “name”=>“theforeman.foreman.auth_sources_ldap”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.compute_profiles”=>{“id”=>nil, “name”=>“theforeman.foreman.compute_profiles”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.compute_resources”=>{“id”=>nil, “name”=>“theforeman.foreman.compute_resources”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.content_credentials”=>{“id”=>nil, “name”=>“theforeman.foreman.content_credentials”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.content_rhel”=>{“id”=>nil, “name”=>“theforeman.foreman.content_rhel”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.content_view_publish”=>{“id”=>nil, “name”=>“theforeman.foreman.content_view_publish”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.content_view_version_cleanup”=>{“id”=>nil, “name”=>“theforeman.foreman.content_view_version_cleanup”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.content_views”=>{“id”=>nil, “name”=>“theforeman.foreman.content_views”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.convert2rhel”=>{“id”=>nil, “name”=>“theforeman.foreman.convert2rhel”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.domains”=>{“id”=>nil, “name”=>“theforeman.foreman.domains”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.hostgroups”=>{“id”=>nil, “name”=>“theforeman.foreman.hostgroups”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.lifecycle_environments”=>{“id”=>nil, “name”=>“theforeman.foreman.lifecycle_environments”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.locations”=>{“id”=>nil, “name”=>“theforeman.foreman.locations”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.manifest”=>{“id”=>nil, “name”=>“theforeman.foreman.manifest”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.operatingsystems”=>{“id”=>nil, “name”=>“theforeman.foreman.operatingsystems”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.organizations”=>{“id”=>nil, “name”=>“theforeman.foreman.organizations”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.provisioning_templates”=>{“id”=>nil, “name”=>“theforeman.foreman.provisioning_templates”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.repositories”=>{“id”=>nil, “name”=>“theforeman.foreman.repositories”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.settings”=>{“id”=>nil, “name”=>“theforeman.foreman.settings”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.subnets”=>{“id”=>nil, “name”=>“theforeman.foreman.subnets”, “created_at”=>nil, “updated_at”=>nil}, “theforeman.foreman.sync_plans”=>{“id”=>nil, “name”=>“theforeman.foreman.sync_plans”, “created_at”=>nil, “updated_at”=>nil}}}, “proxy”=>1, “ansible_role”=>{}}
2025-10-31T22:22:58 [E|app|e453397b] Failed enqueuing SyncRolesAndVariables to Dynflow(default): RuntimeError (The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer)
2025-10-31T22:22:58 [W|app|e453397b] The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer
2025-10-31T22:22:58 [I|app|e453397b] Backtrace for ‘The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer’ error (RuntimeError): The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer
e453397b | /usr/share/gems/gems/dynflow-1.9.2/lib/dynflow/rails.rb:79:in world' e453397b | /usr/share/gems/gems/dynflow-1.9.2/lib/dynflow/active_job/queue_adapter.rb:8:in enqueue’
e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/enqueuing.rb:67:in block in enqueue' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:118:in block in run_callbacks’
e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/instrumentation.rb:25:in block in instrument' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications.rb:206:in block in instrument’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications/instrumenter.rb:24:in instrument' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications.rb:206:in instrument’
e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/instrumentation.rb:35:in instrument' e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/instrumentation.rb:9:in block (2 levels) in module:Instrumentation’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in instance_exec' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks’
e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/logging.rb:27:in tag_logger' e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/logging.rb:14:in block (2 levels) in module:Logging’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in instance_exec' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:138:in run_callbacks' e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/enqueuing.rb:63:in enqueue’
e453397b | /usr/share/gems/gems/activejob-7.0.8.7/lib/active_job/enqueuing.rb:30:in perform_later' e453397b | /usr/share/gems/gems/foreman_ansible-17.0.2/app/controllers/ansible_roles_controller.rb:35:in confirm_import’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/basic_implicit_render.rb:6:in send_action' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/abstract_controller/base.rb:215:in process_action’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/rendering.rb:165:in process_action' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/abstract_controller/callbacks.rb:234:in block in process_action’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:118:in block in run_callbacks' e453397b | /usr/share/foreman/app/controllers/concerns/foreman/controller/timezone.rb:10:in set_timezone’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks' e453397b | /usr/share/foreman/app/models/concerns/foreman/thread_session.rb:32:in clear_thread’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks' e453397b | /usr/share/foreman/app/controllers/concerns/foreman/controller/topbar_sweeper.rb:12:in set_topbar_sweeper_controller’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks' e453397b | /usr/share/gems/gems/audited-5.8.0/lib/audited/sweeper.rb:16:in around’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks' e453397b | /usr/share/gems/gems/audited-5.8.0/lib/audited/sweeper.rb:16:in around’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:127:in block in run_callbacks' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:138:in run_callbacks’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/abstract_controller/callbacks.rb:233:in process_action' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/rescue.rb:23:in process_action’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/instrumentation.rb:67:in block in process_action' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications.rb:206:in block in instrument’
e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications/instrumenter.rb:24:in instrument' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/notifications.rb:206:in instrument’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/instrumentation.rb:66:in process_action' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal/params_wrapper.rb:259:in process_action’
e453397b | /usr/share/gems/gems/activerecord-7.0.8.7/lib/active_record/railties/controller_runtime.rb:27:in process_action' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/abstract_controller/base.rb:151:in process’
e453397b | /usr/share/gems/gems/actionview-7.0.8.7/lib/action_view/rendering.rb:39:in process' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal.rb:188:in dispatch’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_controller/metal.rb:251:in dispatch' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:49:in dispatch’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:32:in serve' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/router.rb:50:in block in serve’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/router.rb:32:in each' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/journey/router.rb:32:in serve’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/routing/route_set.rb:852:in call' e453397b | /usr/share/gems/gems/apipie-dsl-2.6.2/lib/apipie_dsl/static_dispatcher.rb:67:in call’
e453397b | /usr/share/gems/gems/apipie-rails-1.4.2/lib/apipie/static_dispatcher.rb:74:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/static.rb:23:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/static.rb:23:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/static.rb:23:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/static.rb:23:in call' e453397b | /usr/share/foreman/lib/foreman/middleware/libvirt_connection_cleaner.rb:9:in call’
e453397b | /usr/share/foreman/lib/foreman/middleware/telemetry.rb:10:in call' e453397b | /usr/share/gems/gems/apipie-rails-1.4.2/lib/apipie/middleware/checksum_in_headers.rb:27:in call’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/tempfile_reaper.rb:15:in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/etag.rb:27:in call’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/conditional_get.rb:40:in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/head.rb:12:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/http/permissions_policy.rb:38:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/http/content_security_policy.rb:39:in call’
e453397b | /usr/share/foreman/lib/foreman/middleware/logging_context_session.rb:22:in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/session/abstract/id.rb:266:in context’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/session/abstract/id.rb:260:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/cookies.rb:704:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/callbacks.rb:27:in block in call' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/callbacks.rb:99:in run_callbacks’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/callbacks.rb:26:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/debug_exceptions.rb:28:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/show_exceptions.rb:29:in call' e453397b | /usr/share/gems/gems/railties-7.0.8.7/lib/rails/rack/logger.rb:40:in call_app’
e453397b | /usr/share/gems/gems/railties-7.0.8.7/lib/rails/rack/logger.rb:27:in call' e453397b | /usr/share/gems/gems/sprockets-rails-3.5.2/lib/sprockets/rails/quiet_assets.rb:17:in call’
e453397b | /usr/share/foreman/lib/foreman/middleware/logging_context_request.rb:11:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/remote_ip.rb:93:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/request_id.rb:26:in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/method_override.rb:24:in call’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/runtime.rb:22:in call' e453397b | /usr/share/gems/gems/activesupport-7.0.8.7/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/executor.rb:14:in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/sendfile.rb:110:in call’
e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/ssl.rb:77:in call' e453397b | /usr/share/gems/gems/actionpack-7.0.8.7/lib/action_dispatch/middleware/host_authorization.rb:131:in call’
e453397b | /usr/share/gems/gems/secure_headers-7.1.0/lib/secure_headers/middleware.rb:11:in call' e453397b | /usr/share/gems/gems/railties-7.0.8.7/lib/rails/engine.rb:530:in call’
e453397b | /usr/share/gems/gems/railties-7.0.8.7/lib/rails/railtie.rb:226:in public_send' e453397b | /usr/share/gems/gems/railties-7.0.8.7/lib/rails/railtie.rb:226:in method_missing’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/urlmap.rb:74:in block in call' e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/urlmap.rb:58:in each’
e453397b | /usr/share/gems/gems/rack-2.2.17/lib/rack/urlmap.rb:58:in call' e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/configuration.rb:279:in call’
e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/request.rb:99:in block in handle_request' e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/thread_pool.rb:390:in with_force_shutdown’
e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/request.rb:98:in handle_request' e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/server.rb:472:in process_client’
e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/server.rb:254:in block in run' e453397b | /usr/share/gems/gems/puma-6.6.1/lib/puma/thread_pool.rb:167:in block in spawn_thread’
e453397b | /usr/share/gems/gems/logging-2.4.0/lib/logging/diagnostic_context.rb:474:in `block in create_with_logging_context’
2025-10-31T22:22:58 [I|app|e453397b] Rendered common/500.html.erb (Duration: 4.4ms | Allocations: 856)
2025-10-31T22:22:58 [I|app|e453397b] Completed 500 Internal Server Error in 34ms (Views: 13.1ms | ActiveRecord: 3.0ms | Allocations: 6352)
2025-10-31T22:23:02 [I|app|92e5a2ba] Started GET “/notification_recipients” for 172.20.1.1 at 2025-10-31 22:23:02 +0100
2025-10-31T22:23:02 [I|app|92e5a2ba] Processing by NotificationRecipientsController#index as JSON
2025-10-31T22:23:02 [I|app|92e5a2ba] Completed 200 OK in 10ms (Views: 0.1ms | ActiveRecord: 2.1ms | Allocations: 2209)

4

That’s unusual, it looks like something went wrong during the process initialization. Have you tried restarting foreman and dynflow-sidekiq@* services?

5

tryed but hasn’t resolved

root@foreman-lab ~]# systemctl restart foreman dynflow-sidekiq@
Job for dynflow-sidekiq@worker-hosts-queue-1.service failed because the control process exited with error code.
See “systemctl status dynflow-sidekiq@worker-hosts-queue-1.service” and “journalctl -xeu dynflow-sidekiq@worker-hosts-queue-1.service” for details.

[root@foreman-lab ~]# systemctl |grep dynflow-sidekiq
dynflow-sidekiq@orchestrator.service loaded active running Foreman jobs daemon - orchestrator on sidekiq
dynflow-sidekiq@worker-1.service loaded active running Foreman jobs daemon - worker-1 on sidekiq
● dynflow-sidekiq@worker-hosts-queue-1.service loaded failed failed Foreman jobs daemon - worker-hosts-queue-1 on sidekiq
system-dynflow\x2dsidekiq.slice loaded active active Slice /system/dynflow-sidekiq

[root@foreman-lab ~]# journalctl -xeu dynflow-sidekiq@worker-hosts-queue-1.service
Nov 03 09:57:26 foreman-lab systemd[1]: dynflow-sidekiq@worker-hosts-queue-1.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ The unit dynflow-sidekiq@worker-hosts-queue-1.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 03 09:57:26 foreman-lab systemd[1]: Failed to start Foreman jobs daemon - worker-hosts-queue-1 on sidekiq.
░░ Subject: A start job for unit dynflow-sidekiq@worker-hosts-queue-1.service has failed
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ A start job for unit dynflow-sidekiq@worker-hosts-queue-1.service has finished with a failure.
░░
░░ The job identifier is 41637 and the job result is failed.
Nov 03 09:57:27 foreman-lab systemd[1]: dynflow-sidekiq@worker-hosts-queue-1.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ Automatic restarting of the unit dynflow-sidekiq@worker-hosts-queue-1.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Nov 03 09:57:27 foreman-lab systemd[1]: Stopped Foreman jobs daemon - worker-hosts-queue-1 on sidekiq.
░░ Subject: A stop job for unit dynflow-sidekiq@worker-hosts-queue-1.service has finished
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ A stop job for unit dynflow-sidekiq@worker-hosts-queue-1.service has finished.
░░
░░ The job identifier is 41727 and the job result is done.
Nov 03 09:57:27 foreman-lab systemd[1]: dynflow-sidekiq@worker-hosts-queue-1.service: Start request repeated too quickly.
Nov 03 09:57:27 foreman-lab systemd[1]: dynflow-sidekiq@worker-hosts-queue-1.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ The unit dynflow-sidekiq@worker-hosts-queue-1.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 03 09:57:27 foreman-lab systemd[1]: Failed to start Foreman jobs daemon - worker-hosts-queue-1 on sidekiq.
░░ Subject: A start job for unit dynflow-sidekiq@worker-hosts-queue-1.service has failed
░░ Defined-By: systemd
░░ Support: Getting Community Help & Support - Rocky Linux Wiki
░░
░░ A start job for unit dynflow-sidekiq@worker-hosts-queue-1.service has finished with a failure.
░░
░░ The job identifier is 41727 and the job result is failed.

6

strange?

[root@foreman-lab ~]# foreman-maintain service status -b
Running Status Services
================================================================================
Get status of applicable services:

Displaying the following service(s):
redis, postgresql, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, foreman-proxy
| displaying redis [OK]
/ displaying postgresql [OK]
/ displaying dynflow-sidekiq@orchestrator [OK]
/ displaying foreman [OK]
/ displaying httpd [OK]
/ displaying puppetserver [OK]
/ displaying dynflow-sidekiq@worker-1 [OK]
- displaying foreman-proxy [OK]
- All services are running [OK]
--------------------------------------------------------------------------------

7

seem’s that has been resolved.
With the help of chatgpt i did this:
create file /usr/share/foreman/config/initializers/dynflow_initializer.rb contains Rails.application.dynflow.require!
then /etc/systemd/system/foreman.service.d/installer.conf and changed FOREMAN_PUMA_WORKERS from -1 to 2
restarted foreman service i can import the roles.
Many than’s however for your support,
bye

8

That feels vaguely familiar. However that shouldn’t be standard, was this value explicitly set to something when the foreman instance was being deployed?

9

I’ve run foreman-installer setting organization, location and initial password and check installation was been success, the i’ve installed ansible module and plugin using foreman-installer.
I haven’t specified any other setting

10

What are the hardware specs of that machine? Now that I looked that up, the value seems to be calculated from the machine’s available cpu count and memory[1]. In some rare cases, it could probably get you to the -1 you had there.

[1] - Fixes #33277: Change Puma default workers to 1.5 * CPU, max threads to 5 · theforeman/puppet-foreman@533c1f3 · GitHub

11

is a vm with wmware workstation into my local pc, 2 cpu and 3Gb ram.
Is a personal installation for see if can use it for some tasks in owr datacenter.
I’ve understimate the resources?