Foreman 1.23 test week

Foreman 1.23 RC has been announced! It’s the time to put our effort into making sure that all most important features work. It’s easy to get your hands dirty and help us with testing:

  1. Install Foreman RC version (the most up to date one)
  2. Pick a scenario from this post or add your own scenario
  3. If you find an issue, file it in the RedMine and make a comment in this thread linking the issue
  4. Mark the scenario as checked in this OP (this is an editable wiki post), here is syntax of checked and unchecked lines (you can click on checkboxes directly with mouse):
    • Unchecked
    • Checked
    • Checked (alternative syntax with no special semantics - both are equal)

You can start right away, the ideal timing is from Tuesday August 6th until Wednesday August 14th but feel free to put your effort anytime before the final release comes out.


  • Install Foreman using existing script/forklift/beaker
    • RHEL / CentOS latest stable version
    • Debian stable
    • Ubuntu stable LTS
  • Install Foreman manually by following our installation guide
    • RHEL / CentOS latest stable version
    • Debian stable
    • Ubuntu stable LTS
  • Upgrade existing Foreman deployment (advertise in RedMine it was an upgraded instance if you encounter bug)
    • RHEL / CentOS latest stable version
    • Debian stable
    • Ubuntu stable LTS
  • Sanity checks
    • Installation on Red Hat distro with SELinux turned on
    • Packages passenger and tfm-rubygem-passenger are from the same repo (foreman) and in the same version
    • Logging in with a user that has limited permissions works properly


  • Bare-metal or virtualized PXE provisioning (host exits build mode and reboots)
    • BIOS host with CentOS
    • UEFI host with CentOS
    • BIOS host with Debian or Ubuntu
    • UEFI host with Debian or Ubuntu
    • BIOS host with Atomic OS
  • Compute Resources (VM is successfully created, finish or cloud-init is executed)
    • Create VMware host (Image Based/Network Based)
    • Create OpenStack host (Image Based)
    • Create Ovirt host (Image Based/Network Based)
    • Create Libvirt host (Image Based/Network Based)
    • Creare AWS host (Image Based)
    • Create GCE host
  • Puppet manifest import (classes are imported, parameters recognized)
  • Puppet configuration (class is assigned to a host, agent performs changes, reports and facts appears correctly)
  • Log in using user from LDAP (user account is created from LDAP)
  • Log in using user from FreeIPA (user account is created from FreeIPA)

Foreman Discovery

  • Bare-metal or virtualized provisioning via Provision - Customize Host (host exits build mode and reboots)
    • BIOS with discovery from PXE
    • UEFI with discovery from PXE
    • BIOS with discovery PXE-less
    • UEFI with discovery PXE-less
  • Provision a host via discovery rule
  • Provision a host via Customize UI button
  • Provision a host without hostgroup via Customize UI button
  • Provision a host via hammer via hostgroup
  • Provision a host via hammer via auto provisioning rule

Foreman Bootdisk

  • Bootdisk basic provisioning (host exits build mode and reboots)
    • Full host image
    • Host image
    • Generic image
    • Subnet image

Foreman Ansible

  • Import Roles
    • With/From Smart-Proxy
  • Assign Roles
    • Hostgroup
    • Hosts
  • Play Roles
    • Hostgroup
    • Hosts
  • Run shipped Ansible playbook (job), e.g. to install ansible role from galaxy

Foreman Remote Execution

  • Run some job, e.g. ‘ls /etc’ on a system that was provisioned from Foreman, it should work out of the box
  • Run some job against the Foreman host itself, only key configuration should be needed

Foreman Puppet run

  • Trigger Puppet run on host through SSH

Foreman Openscap

  • Create new content file, define a policy, assign it to a host and deploy the foreman_scap_client using puppet
  • Verify ARF report gets uploaded upon foreman_scap_client run and full version of it can be rendered
  • Create tailoring file, assign it to the policy and rerun client with the tailoring file

Foreman Virt Who Configure

  • Create a configuration definition and run it e.g. through REX on some provisioned host. It should succeed as long as it has access to sat tools repo on RHEL, epel (I think) on centos.
    note: plugin works, the configuration requires new virt-who that is currently in fedora 30, not in epel

Foreman Templates

  • hammer import-templates --lock true # sync newest templates from community-templates repo, see audits
  • mkdir /repo; chown foreman /repo; hammer export-templates --repo /repo # may need setenforce 0

This page is a wiki, feel free to update it and add new scenarios as you test them.

Hello all, I just pushed out Discovery 15.1 compatible with 1.23, package PRs are pending, I will perform additional e2e testing next week. FDI to be released soon with help from @evgeni.

I was thinking doing joint release announcement this time for my plugins, I could prepare the text in advance for discovery and bootdisk and it could appear in the official announcement. What do you think @tbrisker? I think the only plugin that deservers a separate annoucement is Katello which has a different pace but most/all the others could be included.

Blocker bug for Red Hat provisioning: Bug #27578: Syntax error in kickstart_ifcfg_generic_interface template - Foreman

1 Like

Blocker Bug for DEB Plugins (thus also the last discovery release): Bug #27564: webpack compile for plugins also generates files for vendor package - Foreman - If it can’t get resolevd for RC2 I’d just delete those files in the packgaing process as a workaround.

1 Like

@sharvit - any idea regarding this? I’m not sure why before it was fine with the core files under public/webpack, but perhaps we should only include public/webpack/$plugin files in the package?

Actually, so far only Katello has been releasing versions in coordination with Foreman core. I think it would be fine to mentions in the release announcement additional plugin versions that have been released to match the core release, but I’m not sure we should include the actual announcement - as that might become too big quickly with a few plugins.

When there is a rendering issue, small overlook in our code causes:

2019-08-20T11:41:56 [W|app|8cd14d86] Action failed
ArgumentError: wrong number of arguments (given 1, expected 3)
/usr/share/foreman/app/controllers/unattended_controller.rb:83:in `render_error'
/usr/share/foreman/app/controllers/concerns/foreman/controller/template_rendering.rb:19:in `rescue in safe_render'
/usr/share/foreman/app/controllers/concerns/foreman/controller/template_rendering.rb:15:in `safe_render'
/usr/share/foreman/app/controllers/concerns/foreman/controller/template_rendering.rb:9:in `render_template'
/usr/share/foreman/app/controllers/unattended_controller.rb:130:in `render_provisioning_template'

This fixes it, so proposing for 1.23: Bug #26758: Unify render_error in unattended and template rendering - Foreman

1 Like

Foreman Discovery Image 3.5.6, Foreman Discovery 15.1 and Bootdisk 15.1 all tested with RC1 successfully. PXE workflows work both with BIOS and UEFI.

1 Like