William Bradford Clark

@ekohl I updated this to truly skip RPM installation and install foreman-installer and all puppet modules from source using librarian-puppet. Any idea how I could properly handle the SCL ruby...

I also need to figure out what is different w.r.t. answers files vs. RPM installation and ensure the right executable gets called.

With my latest work on this, I have it working to build the installer from source (haven't fully implemented using a PR number yet) and running the installer which fails...

Now getting through all hooks up to puppet apply, where it fails due to: ``` [ERROR 2020-09-17T17:01:29 verbose] Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'augeas'...

Installing puppet-agent fixed the issue: `Unknown resource type: 'augeas'`

Pushed another update. I'm sticking with SCLs but had to apply a few workarounds. I'm setting up the puppetserver ca before running the installer (because it doesn't work when the...

This works for me when I test with the following box definition: ``` centos8-nodejs14-katello-devel: primary: true box: centos8-stream ansible: playbook: - 'playbooks/katello_devel.yml' group: 'devel' variables: ssh_forward_agent: true foreman_devel_github_push_ssh: true katello_devel_github_username:...

A related problem is: https://github.com/theforeman/foreman-ansible-modules/issues/946 For now, as you already found, you will need to specify the full operating system title in order to associate multiple operating systems (there is...

A lot of the discussion on this topic is at https://github.com/theforeman/foreman-ansible-modules/issues/373

I believe this is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1962386 paging @phess , let me know if you have some interest/bandwidth to look into it together :)