Uninitialized constant SmartProxyDynflowCore::SETTINGS (NameError)

[betonmoewe]

Problem:
Upgrade to katello nightly from 3.4.2021 (v 4.1) not possible
Expected outcome:
foreman-installer run without any problems
Foreman and Proxy versions:
katello nightly from 3.4.2021
Foreman and Proxy plugin versions:
katello nightly from 3.4.2021
Distribution and version:
CentOS 7
Other relevant data:

[root@sfravm-fi-katello settings.d]# foreman-installer
2021-04-04 00:28:28 [NOTICE] [root] Loading installer configuration. This will take some time.
2021-04-04 00:28:36 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2021-04-04 00:28:36 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2021-04-04 00:29:59 [NOTICE] [configure] Starting system configuration.
2021-04-04 00:30:23 [NOTICE] [configure] 250 configuration steps out of 2056 steps complete.
2021-04-04 00:30:34 [NOTICE] [configure] 500 configuration steps out of 2056 steps complete.
2021-04-04 00:30:35 [NOTICE] [configure] 750 configuration steps out of 2058 steps complete.
2021-04-04 00:30:39 [NOTICE] [configure] 1000 configuration steps out of 2062 steps complete.
2021-04-04 00:30:42 [NOTICE] [configure] 1250 configuration steps out of 2067 steps complete.
2021-04-04 00:31:09 [ERROR ] [configure] ‘/usr/sbin/foreman-rake db:migrate’ returned 1 instead of one of [0]
2021-04-04 00:31:09 [ERROR ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: change from ‘notrun’ to [‘0’] failed: ‘/usr/sbin/foreman-rake db:migrate’ returned 1 instead of one of [0]
2021-04-04 00:31:23 [NOTICE] [configure] 1500 configuration steps out of 2068 steps complete.
2021-04-04 00:31:24 [NOTICE] [configure] 1750 configuration steps out of 2068 steps complete.
2021-04-04 00:32:06 [NOTICE] [configure] 2000 configuration steps out of 2068 steps complete.
2021-04-04 00:32:18 [NOTICE] [configure] System configuration has finished.

if I run foreman-rake db:migrate direct, I got the Error:
rake aborted!
NameError: uninitialized constant SmartProxyDynflowCore::SETTINGS

the foreman service could not start with the same error (uninitialized constant SmartProxyDynflowCore::SETTINGS)

[sajha]

@tasks…Hey Team, does this look familiar?

[ehelms]

Note that while we try to keep nightly as stable as can, it is a moving target and subject to these potential issues. That being said, what you are seeing appears to be a result of the working going on related to this RFC:

Phasing out smart_proxy_dynflow_core

Intro In the early days of remote execution, we wanted to get dynflow to the smart proxy to be able to reuse some code we had on Foreman’s side and to have the same engine on both sides. Sadly at the time, smart proxy wasn’t SCL’d and Dynflow required newer ruby than what was available outside of SCL. To address this situation, we created smart_proxy_dynflow and smart_proxy_dynflow_core gems. smart_proxy_dynflow_core is a sidecar service to the smart proxy, essentially just Dynflow runtime with…

@aruzicka may have more insight

[aruzicka]

Yeah, I’m aware of it. There’s even a fix ready for it [1] for some time already. Until that gets merged and released, you can either rollback to remote execution core 1.4.0 if you still have it cached somewhere or apply the patch locally.

[1] - Fixes #32219 - Check if SPDC settings are available by adamruzicka · Pull Request #575 · theforeman/foreman_remote_execution · GitHub

[betonmoewe]

Thanks for your help and answers (and yes, I know that nightly builds are only for testing ). I just “downgraded” to 4.0RC3.1 … as soon as the patch is integrated, I will test the nightly one more time …

[tbrisker]

Thank you very much for testing on nightly! reporting issues on nightly helps us catch them before they reach stable releases.

[ekohl]

Connecting back: it’s been merged now and packaging has been updated. You should note that currently nightly is being rebuilt on Ruby 2.7. Right now some plugins or Katello pacakges haven’t been rebuilt yet. You may run into that.