This topic is here to collect feedback. With Foreman 3.5 we had some discussion in the release announcement, but not everyone can post there. Please let us know if what your feedback is. This may be bugs, but also feedback on anything else like experience or documentation.
Hello, foreman_discovery makes installation to fail, due to the migration. It has been fixed at Fixes #36006 - Migration error 'column settings.category does not exist' · theforeman/foreman_discovery@9b52424 · GitHub but we need a release for 3.6.
Also, after running
foreman-installer \ --enable-foreman-plugin-discovery \ --enable-foreman-proxy-plugin-discovery \ --foreman-proxy-plugin-discovery-install-images=true
The installer fails with
2023-03-08 21:08:27 [NOTICE] [root] Loading installer configuration. This will take some time. 2023-03-08 21:08:39 [NOTICE] [root] Running installer with log based terminal output at level NOTICE. 2023-03-08 21:08:39 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions. 2023-03-08 21:08:57 [NOTICE] [configure] Starting system configuration. 2023-03-08 21:09:33 [NOTICE] [configure] 750 configuration steps out of 1046 steps complete. 2023-03-08 21:10:36 [NOTICE] [configure] 1000 configuration steps out of 1046 steps complete. 2023-03-08 21:10:44 [ERROR ] [configure] Proxy foreman.hu.lan has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors 2023-03-08 21:10:44 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.hu.lan]/features: change from ["Ansible", "Dynflow", "HTTPBoot", "Logs", "Puppet CA", "Script", "TFTP"] to ["Ansible", "Discovery", "Dynflow", "Logs", "Puppet CA", "Script", "TFTP"] failed: Proxy foreman.hu.lan has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors 2023-03-08 21:10:45 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.hu.lan]: Failed to call refresh: Proxy foreman.hu.lan has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors 2023-03-08 21:10:45 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman.hu.lan]: Proxy foreman.hu.lan has failed to load one or more features (Discovery), check /var/log/foreman-proxy/proxy.log for configuration errors 2023-03-08 21:10:53 [NOTICE] [configure] System configuration has finished.
however the proxy.log does not contain any issue and the proxy in foreman UI shows the discovery feature just right.
foreman_discovery packaging PR: Update rubygem-foreman_discovery to 22.0.4 by Ron-Lavi · Pull Request #9159 · theforeman/foreman-packaging · GitHub
I will also cherry-pick it into 3.6 once it’s merged
Do you have in plan to add
foreman-maintain command to Debian/Ubuntu?
You may have missed that we added foreman-maintain Debian support with Foreman 3.4:
The documentation may not reflect this yet, so it’s easy to miss.
thanks for your replay @ekohl we use Ubuntu 20.04 :
root@test-srv:~# foreman-maintain foreman-maintain: command not found root@test-srv:~# dpkg-query -l | grep foreman ii foreman 3.5.1-1+ubuntu2004 amd64 Systems management web interface ii foreman-cli 3.5.1-1+ubuntu2004 all metapackage providing hammer CLI for Foreman ii foreman-debug 3.5.1-1+ubuntu2004 all provides support utility foreman-debug. ii foreman-dynflow-sidekiq 3.5.1-1+ubuntu2004 all package providing dynflow sidekiq services for Foreman ii foreman-installer 3.5.1-1+ubuntu2004 all Automated puppet-based installer for The Foreman ii foreman-postgresql 3.5.1-1+ubuntu2004 all metapackage providing PostgreSQL dependencies for Foreman ii foreman-proxy 3.5.1-1+ubuntu2004 all RESTful proxies for DNS, DHCP, TFTP, and Puppet ii foreman-service 3.5.1-1+ubuntu2004 all package providing Foreman services running via puma ii ruby-foreman-column-view 0.4.0-2 all Foreman Column View Plugin ii ruby-foreman-deface 1.9.0-2 all Foreman Deface Plugin Dependency ii ruby-foreman-puppet 5.0.0-1 all Foreman Puppet Plugin ii ruby-hammer-cli-foreman 3.5.0-1+ubuntu2004 all Foreman commands for Hammer ii ruby-hammer-cli-foreman-puppet 0.0.6-1 all Foreman Puppet plugin for Hammer CLI
Looking at http://deb.theforeman.org/dists/focal/3.5/binary-amd64/Packages I see ruby-foreman-maintain or the other way round it is at Index of /pool/focal/3.5/r/ruby-foreman-maintain. So it should be available for you.
This lists the installed packages.
apt search foreman-maintain should list it as available though.
I install it as you suggest:
> > root@test-srv:~# apt install ruby-foreman-maintain > root@test-srv:~# foreman-maintain --help > Usage: > foreman-maintain [OPTIONS] SUBCOMMAND [ARG] ... > > Parameters: > SUBCOMMAND subcommand > [ARG] ... subcommand arguments > > Subcommands: > health Health related commands > upgrade Upgrade related commands > service Control applicable services > backup Backup server > restore Restore a backup > packages Lock/Unlock package protection, install, update > advanced Advanced tools for server maintenance > content Content related commands > plugin Manage optional plugins on your server > self-upgrade Perform major version self upgrade > maintenance-mode Control maintenance-mode for application > > Options: > -h, --help print help
is there a documentation for the foreman-maintain ?
At least some at Foreman :: Plugin Manuals
I think that’s very old. The idea is to get https://docs.theforeman.org/ ready, which uses it when needed. See Making docs.theforeman.org the primary documentation source for that plan.
this help me a lot: Foreman-maintain deep dive for all others…
In DB migration failure installing remote execution plugin, remote-execution was reported to be broken in 3.6 due to settings.category migrations which I would assume is caused by https://projects.theforeman.org/issues/29939. This seems to be fixed in Fixes #36003 - Migration error 'column settings.category does not exist' by stejskalleos · Pull Request #778 · theforeman/foreman_remote_execution · GitHub, but that PR is (from what I can tell) only in remote-execution 9.1, while 3.6 plugin repos only ship 9.0.
I would assume a release of remote-exection 9.1 to the 3.6 plugin repos should fix this, but maybe someone with better knowledge can take a look.