Problem:
I’m unable to delete two virtual hosts on a remote compute resource.
If I try from the hosts page, I get this error:
If I try from the specific host page, I only get a notification stating Request failed with status code 422.
These hosts failed to configure correctly while I was setting up the new compute resource. Now it’s working but I can’t delete the hosts from Foreman. I’ve upgraded from 3.11 to 3.12 with no change. I just used Foreman to delete the VMs on the compute resource page, which worked but of course hasn’t removed the host entry in Foreman proper.
I’m not sure what request is being made to PuppetDB or what’s wrong with the certificates to give the error PuppetDB: SSL_connect returned-I errno=O state-error: certificate verify failed (hostname mismatch). PuppetDB and Foreman are on the same host, which should trust the Puppet CA.
The second error PXELinux': ERF42-7327 [Foreman::Exception]: The snippet 'kickstart_kernel_options' threw an error: undefined method '#mac' for NilClass::Jail (NilClass) looks like some problems reported here, but both hosts have an assigned MAC in Foreman, so I don’t know why the snippet would fail to render - or why it needs to be rendered at all just to delete the host.
Expected outcome:
Hosts should be deleted.
Foreman and Proxy versions:
3.12.0
Foreman and Proxy plugin versions:
rubygem-hammer_cli_foreman_puppet-0.1.0-1.fm3_11.el9.noarch
rubygem-puppetdb_foreman-6.0.2-1.fm3_10.el9.noarch
foreman-release-3.12.0-1.el9.noarch
foreman-proxy-3.12.0-1.el9.noarch
rubygem-hammer_cli_foreman-3.12.0-1.el9.noarch
foreman-selinux-3.12.0-1.el9.noarch
foreman-3.12.0-1.el9.noarch
rubygem-foreman-tasks-9.2.3-1.fm3_12.el9.noarch
rubygem-foreman_remote_execution-13.2.5-1.fm3_12.el9.noarch
foreman-dynflow-sidekiq-3.12.0-1.el9.noarch
foreman-libvirt-3.12.0-1.el9.noarch
foreman-postgresql-3.12.0-1.el9.noarch
foreman-redis-3.12.0-1.el9.noarch
foreman-service-3.12.0-1.el9.noarch
rubygem-foreman_puppet-7.0.0-2.fm3_12.el9.noarch
foreman-cli-3.12.0-1.el9.noarch
rubygem-foreman_maintain-1.7.6-1.el9.noarch
foreman-obsolete-packages-1.10-1.el9.noarch
foreman-installer-3.12.0-1.el9.noarch
foreman-debug-3.12.0-1.el9.noarch
Distribution and version:
AlmaLinux 9.4 (Seafoam Ocelot)
Other relevant data:
I can provide the backtraces but they don’t seem informative beyond the error messages. Since this was due to a configuration problem, I’m fine with just editing the DB to drop these records but it’d be nice if there’s a way to clean up properly.