Implement foreman test environment

[bastelfreak]

I added an INSTALL.md with some instructions. This doesn't pass yet. So far this works:

puppet agent -t accounts,prometheus,chrony,yumrepo,auditd,tftp,convenience,debugutils,rsyslog,discovery,puppetserver,host,irqbalance,ssh,lldpd,sysstat

Somehow something breaks the dynflow database if I apply the whole catalog and then foreman doesn't start anymore. I will investigate next week.

[bastelfreak]

@jhoblitt this works for me now:

[root@lsst ~]# puppet agent -t
Info: Using environment 'bastelfreak'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Warning: Facter: invalid or malformed lldp data: MalformedDataError: no lldp interface data found
Warning: The current total number of facts: 2490 exceeds the number of facts limit: 2048
Notice: Requesting catalog from $host:8140 ($ip)
Notice: Catalog compiled by $host
Info: Caching catalog for $host
Info: Applying configuration version '1707679430'
Notice: System Reboot Required Because:
  audit => modified
Notice: Applied catalog in 24.96 seconds
[root@lsst ~]#

There were a few minor hiera changes and I had to update the theforeman/foreman module. I only tested the latest version 24.1.0. The majority of the changes are related to the apache in front of foreman, not foreman itself.

I also think that the foreman module has some ordering issues and cannot apply the foreman_config_entry during the first puppet run and a bunch of foreman related packages are installed afterwards. I didn't dig too deep into this. They were all applied without issues during the second run and the third one is idempotent and has no changes.

To make the testing a bit easier, I made a few of your profiles optional/opt-out and provided those changes as dedicated PRs:

• profile::core::foreman: Make smee installation opt-out #1048
• Make networkmanager optional #1046
• profile::core::common: remove redundant ipa include #1049

[bastelfreak]

the plugin doesn't exist anymore because the code moved into foreman core. The Hiera data is currently unused. I didn't investigate yet how to configure the columns on modern foreman.

[bastelfreak]

For what it's worth, an upgrade to 3.9.1 works as well:

$ git diff bastelfreak -- hieradata/site/test.yaml
diff --git a/hieradata/site/test.yaml b/hieradata/site/test.yaml
index 9c8d5879..fe389676 100644
--- a/hieradata/site/test.yaml
+++ b/hieradata/site/test.yaml
@@ -28,8 +28,8 @@ profile::core::yum::versionlock:
     release: "1.el8"
     before: "Package[puppetdb-termini]"

-foreman::repo::repo: "3.8"
-foreman::version: "3.8.0"
+foreman::repo::repo: "3.9"
+foreman::version: "3.9.1"
 puppetdb::globals::version: '7.16.0'

 profile::core::common::manage_sssd: false