Problem:
Here’s a weird one for you. Doing cloud-init install for Ubuntu 22.04 and after proper build the puppet classes do not apply. Puppet runs fine but shows “Applied catalog in 0.02 seconds” and no classes are applied. Delete the host in Foreman (without removing the host) and the host now will not re-appear after puppet run. Whats even weirder is that after building this host then fully deleting everything and building a host from scratch (not using Foreman) with the same hostname now will not show up at all in foreman after puppet run. This step doesn’t matter which OS, tried Ubuntu 20.04 22.04 and CentOS 7. It’s like the hostname is now tainted or is locked up someplace in the database. It simply won’t appear any more.
Let me know what troubleshooting steps I should take of if clarification on anything is needed. I’ve already looked in the database in the hosts table, and the test host is not present after delete.
Expected outcome:
Classes to apply, host to appear after puppet run.
Foreman and Proxy versions:
3.7.0
Foreman and Proxy plugin versions:
[foreman-tasks] 8.1.1
[foreman_google] 1.0.4
[foreman_puppet] 6.0.0
[foreman_remote_execution] 10.0.7
[foreman_templates] 9.3.3
Distribution and version:
Foreman lives on AlmaLinux 8.8
Other relevant data:
Deploying these hosts to VMWare.
Pretty much standard Foreman install using default templates only modified to point at our expanded ISO for Ubuntu 22.04. Standard puppet run command “agent -t” with zero reports uploaded even though logs show that they are being uploaded:
2023-10-06T11:28:48 [I|app|24d8fde7] Imported report for sbrocktest25 in 37.5 ms, status refreshed in 26.0 ms