Foreman Discovery 4.1 is ready

Hello,

Foreman Discovery image 4.1 is ready in our 1.10 and nightly
repositories together with new Discovery Image 3.0.

GPG signature files to be uploaded this week.

Version combinations:

Foreman Discovery 4.1.1
Discovery Image 3.0.2
Smart Proxy Discovery plugin 1.0.5
Hammer CLI Discovery Plugin 0.0.2

Plugin changes:

New features:

  • PXE-less discovery via kexec mechanism

This version only works with Discovery Image 3.0+ but it is possible to
reboot legacy discovered nodes into new version. Remember to sign-off
from Foreman after the plugin is installed to invalidate top-menu cache.

#11915 - MO files no longer missing for prod translations
#12003 - new API for refresh_facts action
#12053 - improved RHEL6 kexec template
#11942 - host conversion fixed on PostgreSQL
#11978 - fixed kexec auto provisioning
#10300 - adding new image power API support
#11708 - removed auto_provisioning RABL, improved unit tests
#11313 - Add the app/views path to RABL view path of foreman

The plugin is also compatible with Foreman 1.9, we will push it into the
repositories if there is demand from our users. Let us know on the
lists.

Image changes:

The new image now does not initialize all network cards with DHCP by
default (use fdi.initnet=all to force this behavior). We have cleaned up
network initialization little bit further, which solved two race
conditions with systemd. Also, initial five fact uploads are not cached
to solve some hardware with late initialization. This can be overriden
with kernel command line options. Also, systemctl is following system
journal on the second console and smart proxy now logs into journald
instead of separate file. Servers with IPMI on port #2 (Dell PowerEdge)
is now reported correctly.

The biggest new feature is text-based interface with enhanced status
information, ability to turn on/off ssh and better reporting/debugging.
The ISO image can now be burned onto CDROM/USB stick and nodes can be
discovered semi-automatically without PXE or DHCP. Possible scenarios:

  • fully-automated discovery (traditional approach)
  • networks with DHCP but without PXE
  • networks without PXE/DHCP

Kernel command line options are accepted to do semi-automatic
provisioning where some of forms can be pre-populated with values. Or
things can be fully automated even on networks without PXE/DHCP by
modifying SYSLINUX configuration on the discovery ISO. This essentially
replaces Foreman Bootdisk plugin in scenarios where generic images
(iPXE) do not work well (hardware compatibility).

Upgrading existing nodes: Deploy the new image onto the TFTP server(s),
upgrade Foreman/Discovery plugin and reboot the existing nodes into the
new image.

  • #10299 - PXE-less workflow with TUI interface
  • #11678 - Initial 5 fact uploads are not cached
  • #9810 - IPMI facter extensions multichannel support
  • #11340 - Improved build scripts
  • #11241 - Use NetworkManager dispatcher script instead of dhclient
  • #11134 - New fdi.initnet option to init all interfaces
  • #10831 - New fdi.zipserver to override TFTP server for extensions
  • Interactive TUI on the initial (status) screen
  • Only Provisioning (PXE) NIC is initialized with DHCP by default
  • System logs accessible via journald on tty2
  • Removed BMC API with new Power API with kexec support
  • Smart-proxy logs into systemd instead a separate file
  • Dracut patch for old Fedoras removed

Documentation link:

http://theforeman.org/plugins/foreman_discovery/4.1/index.html

(Since we are still in RC phase for Foreman Core, I am announcing this
with documentation undergoing review.)

https://github.com/theforeman/theforeman.org/pull/421/files

Contributors (in alphabetical order): Elmer Rivera, Greg Sutcliffe, Jan
Ivar Beddari, Lukas Zapletal, Shlomi Zadok, Stephen Benjamin

Thank you all!

··· -- Later, Lukas #lzap Zapletal

awesome stuff, i would love to be able to roll this with foreman 1.9… but
i do plan on moving to foreman 1.10 pretty quickly since there are pieces
in there i'm looking forward to.

-byron

··· On Tuesday, October 20, 2015 at 10:26:33 AM UTC-5, Lukas Zapletal wrote: > > Hello, > > Foreman Discovery image 4.1 is ready in our 1.10 and nightly > repositories together with new Discovery Image 3.0. > > http://downloads.theforeman.org/discovery/releases/3.0/ > > GPG signature files to be uploaded this week. > > Version combinations: > > Foreman Discovery 4.1.1 > Discovery Image 3.0.2 > Smart Proxy Discovery plugin 1.0.5 > Hammer CLI Discovery Plugin 0.0.2 > > Plugin changes: > > New features: > > * PXE-less discovery via kexec mechanism > > This version only works with Discovery Image 3.0+ but it is possible to > reboot legacy discovered nodes into new version. Remember to sign-off > from Foreman after the plugin is installed to invalidate top-menu cache. > > #11915 - MO files no longer missing for prod translations > #12003 - new API for refresh_facts action > #12053 - improved RHEL6 kexec template > #11942 - host conversion fixed on PostgreSQL > #11978 - fixed kexec auto provisioning > #10300 - adding new image power API support > #11708 - removed auto_provisioning RABL, improved unit tests > #11313 - Add the app/views path to RABL view path of foreman > > The plugin is also compatible with Foreman 1.9, we will push it into the > repositories if there is demand from our users. Let us know on the > lists. > > Image changes: > > The new image now does not initialize all network cards with DHCP by > default (use fdi.initnet=all to force this behavior). We have cleaned up > network initialization little bit further, which solved two race > conditions with systemd. Also, initial five fact uploads are not cached > to solve some hardware with late initialization. This can be overriden > with kernel command line options. Also, systemctl is following system > journal on the second console and smart proxy now logs into journald > instead of separate file. Servers with IPMI on port #2 (Dell PowerEdge) > is now reported correctly. > > The biggest new feature is text-based interface with enhanced status > information, ability to turn on/off ssh and better reporting/debugging. > The ISO image can now be burned onto CDROM/USB stick and nodes can be > discovered semi-automatically without PXE or DHCP. Possible scenarios: > > - fully-automated discovery (traditional approach) > - networks with DHCP but without PXE > - networks without PXE/DHCP > > Kernel command line options are accepted to do semi-automatic > provisioning where some of forms can be pre-populated with values. Or > things can be fully automated even on networks without PXE/DHCP by > modifying SYSLINUX configuration on the discovery ISO. This essentially > replaces Foreman Bootdisk plugin in scenarios where generic images > (iPXE) do not work well (hardware compatibility). > > Upgrading existing nodes: Deploy the new image onto the TFTP server(s), > upgrade Foreman/Discovery plugin and reboot the existing nodes into the > new image. > > * #10299 - PXE-less workflow with TUI interface > * #11678 - Initial 5 fact uploads are not cached > * #9810 - IPMI facter extensions multichannel support > * #11340 - Improved build scripts > * #11241 - Use NetworkManager dispatcher script instead of dhclient > * #11134 - New fdi.initnet option to init all interfaces > * #10831 - New fdi.zipserver to override TFTP server for extensions > * Interactive TUI on the initial (status) screen > * Only Provisioning (PXE) NIC is initialized with DHCP by default > * System logs accessible via journald on tty2 > * Removed BMC API with new Power API with kexec support > * Smart-proxy logs into systemd instead a separate file > * Dracut patch for old Fedoras removed > > Documentation link: > > http://theforeman.org/plugins/foreman_discovery/4.1/index.html > > (Since we are still in RC phase for Foreman Core, I am announcing this > with documentation undergoing review.) > > https://github.com/theforeman/theforeman.org/pull/421/files > > Contributors (in alphabetical order): Elmer Rivera, Greg Sutcliffe, Jan > Ivar Beddari, Lukas Zapletal, Shlomi Zadok, Stephen Benjamin > > Thank you all! > > -- > Later, > Lukas #lzap Zapletal >

I would like to see and test it also on Foreman 1.9, because I think
Katello 2.4 will not be released soon…

> I would like to see and test it also on Foreman 1.9, because I think
> Katello 2.4 will not be released soon…

Ok, let's just do some extra testing with 1.10 and then we can prepare
it for 1.9. Expect 1.10 Foreman core release timeframe.

Thanks for the feedback.

··· -- Later, Lukas #lzap Zapletal

Wow, thanks!

+1 for 1.9 backport.

··· 2015-10-20 18:26 GMT+03:00 Lukas Zapletal :

Hello,

Foreman Discovery image 4.1 is ready in our 1.10 and nightly
repositories together with new Discovery Image 3.0.

http://downloads.theforeman.org/discovery/releases/3.0/

GPG signature files to be uploaded this week.

Version combinations:

Foreman Discovery 4.1.1
Discovery Image 3.0.2
Smart Proxy Discovery plugin 1.0.5
Hammer CLI Discovery Plugin 0.0.2

Plugin changes:

New features:

  • PXE-less discovery via kexec mechanism

This version only works with Discovery Image 3.0+ but it is possible to
reboot legacy discovered nodes into new version. Remember to sign-off
from Foreman after the plugin is installed to invalidate top-menu cache.

#11915 - MO files no longer missing for prod translations
#12003 - new API for refresh_facts action
#12053 - improved RHEL6 kexec template
#11942 - host conversion fixed on PostgreSQL
#11978 - fixed kexec auto provisioning
#10300 - adding new image power API support
#11708 - removed auto_provisioning RABL, improved unit tests
#11313 - Add the app/views path to RABL view path of foreman

The plugin is also compatible with Foreman 1.9, we will push it into the
repositories if there is demand from our users. Let us know on the
lists.

Image changes:

The new image now does not initialize all network cards with DHCP by
default (use fdi.initnet=all to force this behavior). We have cleaned up
network initialization little bit further, which solved two race
conditions with systemd. Also, initial five fact uploads are not cached
to solve some hardware with late initialization. This can be overriden
with kernel command line options. Also, systemctl is following system
journal on the second console and smart proxy now logs into journald
instead of separate file. Servers with IPMI on port #2 (Dell PowerEdge)
is now reported correctly.

The biggest new feature is text-based interface with enhanced status
information, ability to turn on/off ssh and better reporting/debugging.
The ISO image can now be burned onto CDROM/USB stick and nodes can be
discovered semi-automatically without PXE or DHCP. Possible scenarios:

  • fully-automated discovery (traditional approach)
  • networks with DHCP but without PXE
  • networks without PXE/DHCP

Kernel command line options are accepted to do semi-automatic
provisioning where some of forms can be pre-populated with values. Or
things can be fully automated even on networks without PXE/DHCP by
modifying SYSLINUX configuration on the discovery ISO. This essentially
replaces Foreman Bootdisk plugin in scenarios where generic images
(iPXE) do not work well (hardware compatibility).

Upgrading existing nodes: Deploy the new image onto the TFTP server(s),
upgrade Foreman/Discovery plugin and reboot the existing nodes into the
new image.

  • #10299 - PXE-less workflow with TUI interface
  • #11678 - Initial 5 fact uploads are not cached
  • #9810 - IPMI facter extensions multichannel support
  • #11340 - Improved build scripts
  • #11241 - Use NetworkManager dispatcher script instead of dhclient
  • #11134 - New fdi.initnet option to init all interfaces
  • #10831 - New fdi.zipserver to override TFTP server for extensions
  • Interactive TUI on the initial (status) screen
  • Only Provisioning (PXE) NIC is initialized with DHCP by default
  • System logs accessible via journald on tty2
  • Removed BMC API with new Power API with kexec support
  • Smart-proxy logs into systemd instead a separate file
  • Dracut patch for old Fedoras removed

Documentation link:

Foreman :: Plugin Manuals

(Since we are still in RC phase for Foreman Core, I am announcing this
with documentation undergoing review.)

https://github.com/theforeman/theforeman.org/pull/421/files

Contributors (in alphabetical order): Elmer Rivera, Greg Sutcliffe, Jan
Ivar Beddari, Lukas Zapletal, Shlomi Zadok, Stephen Benjamin

Thank you all!


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google Groups
"foreman-announce" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-announce+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Kind regards,
Vladimir.

I'd like to see this in 1.9 too.

Another thing - it appears that TFM (not sure what this one is) ruby SCL is
new requirement and replaces ruby193? For example:

[root@foreman ~]# yum update ruby193-rubygem-foreman_hooks
Setting up Update Process
Resolving Dependencies
–> Running transaction check
—> Package ruby193-rubygem-foreman_hooks.noarch 0:0.3.8-1.el6 will be
obsoleted
–> Processing Dependency: ruby193-rubygem-foreman_hooks = 0.3.8-1.el6 for
package: ruby193-rubygem-foreman_hooks-doc-0.3.8-1.el6.noarch
—> Package tfm-rubygem-foreman_hooks.noarch 0:0.3.9-1.el6 will be
obsoleting
–> Running transaction check
—> Package ruby193-rubygem-foreman_hooks-doc.noarch 0:0.3.8-1.el6 will be
obsoleted
—> Package tfm-rubygem-foreman_hooks-doc.noarch 0:0.3.9-1.el6 will be
obsoleting
–> Processing Dependency: tfm-rubygem(jgrep) for package:
tfm-rubygem-foreman_hooks-doc-0.3.9-1.el6.noarch
–> Running transaction check
—> Package ruby193-rubygem-jgrep.noarch 0:1.3.3-5.el6 will be obsoleted
—> Package tfm-rubygem-jgrep.noarch 0:1.3.3-6.el6 will be obsoleting
–> Finished Dependency Resolution

Dependencies Resolved

··· ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Installing: tfm-rubygem-foreman_hooks noarch 0.3.9-1.el6 foreman-plugins-latest 19 k replacing ruby193-rubygem-foreman_hooks.noarch 0.3.8-1.el6 tfm-rubygem-foreman_hooks-doc noarch 0.3.9-1.el6 foreman-plugins-latest 19 k replacing ruby193-rubygem-foreman_hooks-doc.noarch 0.3.8-1.el6 tfm-rubygem-jgrep noarch 1.3.3-6.el6 foreman-plugins-latest 16 k replacing ruby193-rubygem-jgrep.noarch 1.3.3-5.el6

Transaction Summary

Install 3 Package(s)

Total download size: 54 k
Is this ok [y/N]: n
Exiting on user Command
[root@foreman ~]#

This example does not break any dependencies, but attempts to install other
packages breaks lot more stuff:

Error: Package: ruby193-rubygem-fog-softlayer-0.3.9-1.el6.noarch (@foreman-1.6) Requires: ruby193-rubygem-fog-json Removing: ruby193-rubygem-fog-json-1.0.2-1.el6.noarch (@foreman-latest) ruby193-rubygem-fog-json = 1.0.2-1.el6 Obsoleted By: tfm-rubygem-fog-json-1.0.2-2.el6.noarch (foreman-1.10) Not found Error: Package: ruby193-rubygem-fog-softlayer-0.3.9-1.el6.noarch (@foreman-1.6) Requires: ruby193-rubygem-fog-core Removing: ruby193-rubygem-fog-core-1.32.0-1.el6.noarch (@foreman-latest) ruby193-rubygem-fog-core = 1.32.0-1.el6 Obsoleted By: tfm-rubygem-fog-core-1.32.1-2.el6.noarch (foreman-1.10) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@foreman ~]#

Any advice?
Thanks!

I see. Would you anticipate backporting discovery 4.1 to 1.9 happening
sooner than 1.10 going from RC to a proper release?

Hello Folks,

Need your suggestions… Below the Scenarios.

I have configured DNS and NTP and both looks fine, while running below
command facing issues .

[root@puppet-labs-client-01 yum.repos.d]# foreman-installer -i
Welcome to the Foreman installer!

··· ---------------------------------

This wizard will gather all required information. You can change any
parameter
to your needs.

Ready to start? (y/n)
y

Main Config Menu

  1. [✓] Configure foreman
  2. [✓] Configure foreman_cli
  3. [✓] Configure foreman_proxy
  4. [✓] Configure puppet
  5. [✗] Configure foreman_plugin_ansible
  6. [✗] Configure foreman_plugin_bootdisk
  7. [✗] Configure foreman_plugin_chef
  8. [✗] Configure foreman_plugin_cockpit
  9. [✗] Configure foreman_plugin_default_hostgroup
  10. [✗] Configure foreman_plugin_dhcp_browser
  11. [✗] Configure foreman_plugin_digitalocean
  12. [✓] Configure foreman_plugin_discovery
  13. [✗] Configure foreman_plugin_docker
  14. [✗] Configure foreman_plugin_hooks
  15. [✗] Configure foreman_plugin_memcache
  16. [✗] Configure foreman_plugin_openscap
  17. [✗] Configure foreman_plugin_ovirt_provision
  18. [✗] Configure foreman_plugin_puppetdb
  19. [✗] Configure foreman_plugin_remote_execution
  20. [✗] Configure foreman_plugin_salt
  21. [✓] Configure foreman_plugin_setup
  22. [✗] Configure foreman_plugin_tasks
  23. [✗] Configure foreman_plugin_templates
  24. [✗] Configure foreman_compute_ec2
  25. [✗] Configure foreman_compute_gce
  26. [✗] Configure foreman_compute_libvirt
  27. [✗] Configure foreman_compute_openstack
  28. [✗] Configure foreman_compute_ovirt
  29. [✗] Configure foreman_compute_rackspace
  30. [✗] Configure foreman_compute_vmware
  31. [✗] Configure foreman_proxy_plugin_abrt
  32. [✗] Configure foreman_proxy_plugin_chef
  33. [✗] Configure foreman_proxy_plugin_discovery
  34. [✗] Configure foreman_proxy_plugin_dns_powerdns
  35. [✗] Configure foreman_proxy_plugin_dynflow
  36. [✗] Configure foreman_proxy_plugin_openscap
  37. [✗] Configure foreman_proxy_plugin_pulp
  38. [✗] Configure foreman_proxy_plugin_remote_execution_ssh
  39. [✗] Configure foreman_proxy_plugin_salt
  40. Display current config
  41. Save and run
  42. Cancel run without Saving
    Choose an option from the menu… 41
    Execution of '/usr/bin/yum -d 0 -e 0 -y install foreman-postgresql’
    returned 1: Error: Package: tfm-runtime-2.0-2.el6.x86_64 (foreman)
    /Stage[main]/Foreman::Install/Package[foreman-postgresql]/ensure: change
    from absent to present failed: Execution of ‘/usr/bin/yum -d 0 -e 0 -y
    install foreman-postgresql’ returned 1: Error: Package:
    tfm-runtime-2.0-2.el6.x86_64 (foreman)
    Execution of ‘/usr/bin/yum -d 0 -e 0 -y install foreman-cli’ returned 1:
    Error: Package: tfm-runtime-2.0-2.el6.x86_64 (foreman)
    /Stage[main]/Foreman::Cli/Package[foreman-cli]/ensure: change from absent
    to present failed: Execution of ‘/usr/bin/yum -d 0 -e 0 -y install
    foreman-cli’ returned 1: Error: Package: tfm-runtime-2.0-2.el6.x86_64
    (foreman)
    Could not find a suitable provider for foreman_config_entry
    Report processor failed: Could not send report to Foreman at
    https://puppet-labs-client-01.blr.yqdc.com/api/reports: Connection refused
  • connect(2)
    Installing Done
    [100%]
    […]
    Something went wrong! Check the log for ERROR-level output
    • Foreman is running at https://puppet-labs-client-01.blr.yqdc.com
      Initial credentials are admin / 87qdtidfdcLMwjGD
    • Foreman Proxy is running at
      https://puppet-labs-client-01.blr.yqdc.com:8443
    • Puppetmaster is running at port 8140
      The full log is at /var/log/foreman-installer/foreman.log
      [root@puppet-labs-client-01 yum.repos.d]#
      [root@puppet-labs-client-01 yum.repos.d]# cat
      /var/log/foreman-installer/foreman.log | grep -i error |wc -l
      16
      [root@puppet-labs-client-01 yum.repos.d]#
      [root@puppet-labs-client-01 yum.repos.d]# cat
      /var/log/foreman-installer/foreman.log | grep -i error
      [DEBUG 2016-05-28 17:51:41 main] echo
      ’$kafo_config_file="/etc/foreman-installer/scenarios.d/foreman.yaml"
      $kafo_add_progress=true $temp_dir="/tmp/d20160528-22818-u9zf8b" include
      foreman::params include foreman::cli::params include foreman_proxy::params
      include puppet::params include foreman::plugin::discovery::params include
      foreman::plugin::memcache::params include foreman::plugin::openscap::params
      include foreman::plugin::ovirt_provision::params include
      foreman::plugin::puppetdb::params include foreman::plugin::tasks::params
      include foreman_proxy::plugin::abrt::params include
      foreman_proxy::plugin::chef::params include
      foreman_proxy::plugin::discovery::params include
      foreman_proxy::plugin::dns::powerdns::params include
      foreman_proxy::plugin::dynflow::params include
      foreman_proxy::plugin::openscap::params include
      foreman_proxy::plugin::pulp::params include
      foreman_proxy::plugin::remote_execution::ssh::params include
      foreman_proxy::plugin::salt::params
      dump_values("::foreman::params::servername","::foreman::params::email_smtp_authentication","::foreman::params::ipa_authentication","::foreman::params::foreman_url","::foreman::params::email_delivery_method","::foreman::params::passenger_prestart","::foreman::params::selinux","::foreman::params::websockets_ssl_cert","::foreman::params::oauth_consumer_secret","::foreman::params::oauth_active","::foreman::params::manage_user","::foreman::params::admin_email","::foreman::params::email_smtp_domain",::foreman::params::db_pool,"::foreman::params::server_ssl_certs_dir","::foreman::params::puppetrun",::foreman::params::serveraliases,"::foreman::params::use_vhost","::foreman::params::apipie_task","::foreman::params::user","::foreman::params::websockets_encrypt","::foreman::params::ipa_manage_sssd","::foreman::params::email_smtp_user_name","::foreman::params::configure_brightbox_repo","::foreman::params::email_source","::foreman::params::server_ssl_ca",::foreman::params::loggers,"::foreman::params::passenger_ruby_package","::foreman::params::custom_repo","::foreman::params::locations_enabled","::foreman::params::db_username","::foreman::params::email_smtp_address","::foreman::params::group","::foreman::params::http_keytab",::foreman::params::user_groups,"::foreman::params::server_ssl_crl","::foreman::params::email_smtp_password","::foreman::params::server_ssl_key","::foreman::params::passenger_min_instances","::foreman::params::admin_first_name","::foreman::params::gpgcheck","::foreman::params::admin_password","::foreman::params::version",::foreman::params::email_smtp_port,"::foreman::params::authentication","::foreman::params::plugin_prefix","::foreman::params::oauth_consumer_key","::foreman::params::environment","::foreman::params::configure_epel_repo","::foreman::params::pam_service","::foreman::params::puppet_home","::foreman::params::logging_level","::foreman::params::admin_last_name","::foreman::params::db_password","::foreman::params::email_conf","::foreman::params::app_root","::foreman::params::configure_scl_repo","::foreman::params::passenger","::foreman::params::initial_location","::foreman::params::passenger_ruby","::foreman::params::admin_username","::foreman::params::passenger_interface","::foreman::params::db_type","::foreman::params::organizations_enabled","::foreman::params::websockets_ssl_key","::foreman::params::server_ssl_cert","::foreman::params::ssl","::foreman::params::passenger_start_timeout","::foreman::params::initial_organization","::foreman::params::db_manage","::foreman::params::oauth_map_users","::foreman::params::server_ssl_chain","::foreman::params::repo","::foreman::params::unattended",::foreman::cli::params::request_timeout,"::foreman::cli::params::manage_root_config","::foreman::cli::params::username","::foreman::cli::params::password","::foreman::cli::params::refresh_cache","::foreman::cli::params::foreman_url",“foreman_proxy::params::oauth_consumer_key”,foreman_proxy::params::http_port,“foreman_proxy::params::bmc”,“foreman_proxy::params::freeipa_remove_dns”,“foreman_proxy::params::puppet_user”,“foreman_proxy::params::logs_listen_on”,“foreman_proxy::params::ssl_ca”,“foreman_proxy::params::dns_listen_on”,“foreman_proxy::params::dns_ttl”,“foreman_proxy::params::virsh_network”,“foreman_proxy::params::tftp_manage_wget”,“foreman_proxy::params::salt_puppetrun_cmd”,foreman_proxy::params::tftp_dirs,“foreman_proxy::params::dhcp_nameservers”,“foreman_proxy::params::dhcp_listen_on”,“foreman_proxy::params::gpgcheck”,“foreman_proxy::params::registered_name”,foreman_proxy::params::dhcp_omapi_port,“foreman_proxy::params::register_in_foreman”,“foreman_proxy::params::dns_split_config_files”,“foreman_proxy::params::tftp_syslinux_root”,“foreman_proxy::params::dhcp_split_config_files”,“foreman_proxy::params::dhcp_interface”,“foreman_proxy::params::use_sudoersd”,“foreman_proxy::params::ssl_key”,“foreman_proxy::params::dhcp_server”,“foreman_proxy::params::bmc_default_provider”,“foreman_proxy::params::customrun_cmd”,“foreman_proxy::params::http”,“foreman_proxy::params::ssl_key”,“foreman_proxy::params::foreman_ssl_ca”,“foreman_proxy::params::dhcp_key_name”,“foreman_proxy::params::version”,foreman_proxy::params::log_buffer_errors,“foreman_proxy::params::dhcp_managed”,“foreman_proxy::params::puppet_url”,“foreman_proxy::params::tftp_listen_on”,“foreman_proxy::params::tftp”,“foreman_proxy::params::templates_listen_on”,“foreman_proxy::params::puppetrun_provider”,“foreman_proxy::params::puppetca_cmd”,“foreman_proxy::params::realm_listen_on”,“foreman_proxy::params::logs”,“foreman_proxy::params::realm_principal”,“foreman_proxy::params::dhcp_vendor”,foreman_proxy::params::dhcp_option_domain,“foreman_proxy::params::dns_zone”,“foreman_proxy::params::ssl_cert”,“foreman_proxy::params::puppet_use_environment_api”,“foreman_proxy::params::puppetssh_user”,“foreman_proxy::params::puppetrun_cmd”,“foreman_proxy::params::realm_keytab”,“foreman_proxy::params::puppetca”,foreman_proxy::params::dns_forwarders,foreman_proxy::params::tftp_syslinux_filenames,“foreman_proxy::params::ssl”,“foreman_proxy::params::puppetssh_sudo”,“foreman_proxy::params::realm”,“foreman_proxy::params::puppet_use_cache”,“foreman_proxy::params::dns_tsig_keytab”,“foreman_proxy::params::dns_managed”,“foreman_proxy::params::puppetssh_keyfile”,“foreman_proxy::params::autosign_location”,“foreman_proxy::params::dns_reverse”,“foreman_proxy::params::foreman_ssl_key”,“foreman_proxy::params::log_level”,“foreman_proxy::params::dhcp_config”,“foreman_proxy::params::foreman_ssl_cert”,“foreman_proxy::params::dns_interface”,“foreman_proxy::params::template_url”,“foreman_proxy::params::puppet_group”,“foreman_proxy::params::repo”,foreman_proxy::params::ssl_port,“foreman_proxy::params::dhcp_gateway”,“foreman_proxy::params::log”,“foreman_proxy::params::dns”,“foreman_proxy::params::puppetca_listen_on”,“foreman_proxy::params::templates”,“foreman_proxy::params::customrun_args”,“foreman_proxy::params::oauth_consumer_secret”,foreman_proxy::params::port,“foreman_proxy::params::ssl_cert”,“foreman_proxy::params::dns_tsig_principal”,“foreman_proxy::params::tftp_root”,“foreman_proxy::params::tftp_servername”,“foreman_proxy::params::puppetssh_command”,“foreman_proxy::params::plugin_version”,foreman_proxy::params::log_buffer,“foreman_proxy::params::dhcp_provider”,“foreman_proxy::params::manage_sudoersd”,foreman_proxy::params::trusted_hosts,“foreman_proxy::params::ssl_ca”,“foreman_proxy::params::puppetrun”,“foreman_proxy::params::realm_provider”,“foreman_proxy::params::dns_provider”,“foreman_proxy::params::dhcp_range”,“foreman_proxy::params::custom_repo”,“foreman_proxy::params::dhcp_key_secret”,“foreman_proxy::params::dir”,“foreman_proxy::params::bmc_listen_on”,“foreman_proxy::params::user”,“foreman_proxy::params::dns_server”,“foreman_proxy::params::dhcp_leases”,“foreman_proxy::params::puppetssh_wait”,“foreman_proxy::params::registered_proxy_url”,foreman_proxy::params::tftp_syslinux_files,“foreman_proxy::params::foreman_base_url”,“foreman_proxy::params::oauth_effective_user”,“foreman_proxy::params::puppetrun_listen_on”,“foreman_proxy::params::puppet_cache_location”,“foreman_proxy::params::dhcp”,“foreman_proxy::params::ssldir”,“foreman_proxy::params::bind_host”,“foreman_proxy::params::puppetdir”,“foreman_proxy::params::keyfile”,“puppet::params::dir”,puppet::params::server_request_timeout,“puppet::params::server_post_hook_name”,“puppet::params::agent_template”,“puppet::params::server”,“puppet::params::autosign”,“puppet::params::systemd_cmd”,puppet::params::auth_allowed,“puppet::params::server_git_repo_path”,“puppet::params::splay”,puppet::params::server_puppetdb_port,“puppet::params::group”,“puppet::params::package_source”,“puppet::params::server_certname”,“puppet::params::server_ssl_dir”,“puppet::params::vardir”,“puppet::params::server_envs_dir”,“puppet::params::server_jvm_java_bin”,“puppet::params::server_environments_mode”,“puppet::params::prerun_command”,“puppet::params::server_implementation”,“puppet::params::server_puppetdb_host”,“puppet::params::server_git_repo_mode”,“puppet::params::server_strict_variables”,“puppet::params::server_environment_timeout”,puppet::params::dns_alt_names,“puppet::params::usecacheonfailure”,“puppet::params::user”,puppet::params::unavailable_runmodes,“puppet::params::splaylimit”,“puppet::params::group”,“puppet::params::codedir”,puppet::params::server_passenger_max_pool,“puppet::params::sharedir”,“puppet::params::classfile”,“puppet::params::rundir”,“puppet::params::server_git_repo_user”,“puppet::params::server_version”,“puppet::params::use_srv_records”,“puppet::params::agent_noop”,“puppet::params::ca_server”,“puppet::params::server_reports”,“puppet::params::version”,“puppet::params::server_enc_api”,“puppet::params::server_environments_owner”,“puppet::params::server_manifest_path”,“puppet::params::server_service_fallback”,“puppet::params::server_jvm_min_heap_size”,“puppet::params::server_http”,“puppet::params::server_puppet_basedir”,“puppet::params::server_app_root”,“puppet::params::auth_template”,puppet::params::server_common_modules_path,puppet::params::additional_settings,“puppet::params::runmode”,“puppet::params::pluginfactsource”,puppet::params::server_git_branch_map,“puppet::params::server_jvm_config”,puppet::params::ca_port,“puppet::params::server_git_repo”,puppet::params::port,“puppet::params::server_foreman_ssl_cert”,“puppet::params::server_package”,“puppet::params::server_storeconfigs_backend”,“puppet::params::agent_restart_command”,“puppet::params::listen”,“puppet::params::server_passenger”,“puppet::params::module_repository”,“puppet::params::dir_group”,“puppet::params::server_ca”,“puppet::params::server_jvm_max_heap_size”,“puppet::params::server_git_repo_group”,“puppet::params::main_template”,puppet::params::server_http_allow,“puppet::params::server_jvm_extra_args”,“puppet::params::pluginsource”,“puppet::params::hiera_config”,“puppet::params::postrun_command”,“puppet::params::client_package”,“puppet::params::puppetmaster”,“puppet::params::server_default_manifest_path”,puppet::params::server_http_port,“puppet::params::logdir”,puppet::params::configtimeout,“puppet::params::pluginsync”,“puppet::params::server_facts”,“puppet::params::allow_any_crl_auth”,“puppet::params::remove_lock”,“puppet::params::server_foreman_ssl_key”,“puppet::params::server_report_api”,“puppet::params::server_default_manifest”,“puppet::params::server_foreman”,“puppet::params::server_foreman_url”,“puppet::params::nsauth_template”,“puppet::params::server_puppetdb_swf”,puppet::params::port,“puppet::params::server_external_nodes”,“puppet::params::package_provider”,puppet::params::listen_to,“puppet::params::server_post_hook_content”,“puppet::params::server_parser”,“puppet::params::service_name”,“puppet::params::server_default_manifest_content”,“puppet::params::server_ssl_dir_manage”,“puppet::params::cron_cmd”,“puppet::params::systemd_unit_name”,puppet::params::server_rack_arguments,“puppet::params::syslogfacility”,“puppet::params::server_ca_proxy”,puppet::params::server_additional_settings,“puppet::params::server_directory_environments”,“puppet::params::manage_packages”,“puppet::params::server_template”,puppet::params::agent_additional_settings,“puppet::params::server_foreman_ssl_ca”,“puppet::params::user”,“puppet::params::server_config_version”,“puppet::params::environment”,“puppet::params::dir”,“puppet::params::server_environments_group”,“puppet::params::srv_domain”,puppet::params::runinterval,“puppet::params::server_httpd_service”,“puppet::params::agent”,“puppet::params::dir_owner”,“puppet::params::show_diff”,“puppet::params::server_dynamic_environments”,“puppet::params::ssldir”,puppet::params::server_environments,"::foreman::plugin::discovery::params::install_images","::foreman::plugin::discovery::params::tftp_root","::foreman::plugin::discovery::params::image_name","::foreman::plugin::discovery::params::source_url",::foreman::plugin::memcache::params::expires_in,::foreman::plugin::memcache::params::hosts,"::foreman::plugin::memcache::params::namespace","::foreman::plugin::memcache::params::compress","::foreman::plugin::openscap::params::configure_openscap_repo",“foreman::plugin::ovirt_provision::params::package”,“foreman::plugin::puppetdb::params::package”,“foreman::plugin::puppetdb::params::dashboard_address”,“foreman::plugin::puppetdb::params::address”,“foreman::plugin::tasks::params::package”,“foreman::plugin::tasks::params::service”,“foreman-ec2”,“installed”,“installed”,“installed”,“installed”,“installed”,"::foreman_proxy::plugin::abrt::params::group","::foreman_proxy::plugin::abrt::params::abrt_send_log_file","::foreman_proxy::plugin::abrt::params::faf_server_url","::foreman_proxy::plugin::abrt::params::listen_on","::foreman_proxy::plugin::abrt::params::version","::foreman_proxy::plugin::abrt::params::spooldir","::foreman_proxy::plugin::abrt::params::aggregate_reports","::foreman_proxy::plugin::abrt::params::faf_server_ssl_cert",::foreman_proxy::plugin::abrt::params::send_period,"::foreman_proxy::plugin::abrt::params::faf_ser

Facing issue while running foreman-installer -i command …
Error as mentioned below… Looking for some suggestions …
40. Display current config
41. Save and run
42. Cancel run without Saving
Choose an option from the menu… 41
Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-postgresql' returned
1: Error: Cannot retrieve repository metadata (repomd.xml) for repository:
google_group. Please verify its path and try again
/Stage[main]/Foreman::Install/Package[foreman-postgresql]/ensure: change
from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list
foreman-postgresql' returned 1: Error: Cannot retrieve repository metadata
(repomd.xml) for repository: google_group. Please verify its path and try
again
Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-cli' returned 1:
Error: Cannot retrieve repository metadata (repomd.xml) for repository:
google_group. Please verify its path and try again
/Stage[main]/Foreman::Cli/Package[foreman-cli]/ensure: change from absent
to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list
foreman-cli' returned 1: Error: Cannot retrieve repository metadata
(repomd.xml) for repository: google_group. Please verify its path and try
again
Could not find a suitable provider for foreman_config_entry
Report processor failed: Could not send report to Foreman at
https://puppet-labs-client-01.blr.yqdc.com/api/reports: Connection refused

··· On Tuesday, October 20, 2015 at 8:56:33 PM UTC+5:30, Lukas Zapletal wrote: > > Hello, > > Foreman Discovery image 4.1 is ready in our 1.10 and nightly > repositories together with new Discovery Image 3.0. > > http://downloads.theforeman.org/discovery/releases/3.0/ > > GPG signature files to be uploaded this week. > > Version combinations: > > Foreman Discovery 4.1.1 > Discovery Image 3.0.2 > Smart Proxy Discovery plugin 1.0.5 > Hammer CLI Discovery Plugin 0.0.2 > > Plugin changes: > > New features: > > * PXE-less discovery via kexec mechanism > > This version only works with Discovery Image 3.0+ but it is possible to > reboot legacy discovered nodes into new version. Remember to sign-off > from Foreman after the plugin is installed to invalidate top-menu cache. > > #11915 - MO files no longer missing for prod translations > #12003 - new API for refresh_facts action > #12053 - improved RHEL6 kexec template > #11942 - host conversion fixed on PostgreSQL > #11978 - fixed kexec auto provisioning > #10300 - adding new image power API support > #11708 - removed auto_provisioning RABL, improved unit tests > #11313 - Add the app/views path to RABL view path of foreman > > The plugin is also compatible with Foreman 1.9, we will push it into the > repositories if there is demand from our users. Let us know on the > lists. > > Image changes: > > The new image now does not initialize all network cards with DHCP by > default (use fdi.initnet=all to force this behavior). We have cleaned up > network initialization little bit further, which solved two race > conditions with systemd. Also, initial five fact uploads are not cached > to solve some hardware with late initialization. This can be overriden > with kernel command line options. Also, systemctl is following system > journal on the second console and smart proxy now logs into journald > instead of separate file. Servers with IPMI on port #2 (Dell PowerEdge) > is now reported correctly. > > The biggest new feature is text-based interface with enhanced status > information, ability to turn on/off ssh and better reporting/debugging. > The ISO image can now be burned onto CDROM/USB stick and nodes can be > discovered semi-automatically without PXE or DHCP. Possible scenarios: > > - fully-automated discovery (traditional approach) > - networks with DHCP but without PXE > - networks without PXE/DHCP > > Kernel command line options are accepted to do semi-automatic > provisioning where some of forms can be pre-populated with values. Or > things can be fully automated even on networks without PXE/DHCP by > modifying SYSLINUX configuration on the discovery ISO. This essentially > replaces Foreman Bootdisk plugin in scenarios where generic images > (iPXE) do not work well (hardware compatibility). > > Upgrading existing nodes: Deploy the new image onto the TFTP server(s), > upgrade Foreman/Discovery plugin and reboot the existing nodes into the > new image. > > * #10299 - PXE-less workflow with TUI interface > * #11678 - Initial 5 fact uploads are not cached > * #9810 - IPMI facter extensions multichannel support > * #11340 - Improved build scripts > * #11241 - Use NetworkManager dispatcher script instead of dhclient > * #11134 - New fdi.initnet option to init all interfaces > * #10831 - New fdi.zipserver to override TFTP server for extensions > * Interactive TUI on the initial (status) screen > * Only Provisioning (PXE) NIC is initialized with DHCP by default > * System logs accessible via journald on tty2 > * Removed BMC API with new Power API with kexec support > * Smart-proxy logs into systemd instead a separate file > * Dracut patch for old Fedoras removed > > Documentation link: > > http://theforeman.org/plugins/foreman_discovery/4.1/index.html > > (Since we are still in RC phase for Foreman Core, I am announcing this > with documentation undergoing review.) > > https://github.com/theforeman/theforeman.org/pull/421/files > > Contributors (in alphabetical order): Elmer Rivera, Greg Sutcliffe, Jan > Ivar Beddari, Lukas Zapletal, Shlomi Zadok, Stephen Benjamin > > Thank you all! > > -- > Later, > Lukas #lzap Zapletal >

It does, but that is only in Foreman 1.10. Please don't try and apply
RPMs from the 1.10 or nightly plugin repositories against a Foreman 1.9
installation as they depend on the TFM feature in the Foreman 1.10 packages.

"tfm" (The ForeMan) is our own custom software collection that depends
on ruby193 (at the moment), so all of our packages have been renamed.

If you upgrade the whole Foreman installation from 1.9 to 1.10 then it
should all work together. If you try that and it doesn't work, please
do file a bug or post.

With regards to getting Discovery 4.1 on Foreman 1.9 using RPMs, for now
you'd probably have to rebuild the SRPm yourself until Lukas releases it
for 1.9 too. There is a mock config at


which should work if you change the reference to "nightly" to the
"releases/1.9" repos.

··· On 23/10/15 18:47, 'Konstantin Orekhov' via Foreman users wrote: > I'd like to see this in 1.9 too. > > Another thing - it appears that TFM (not sure what this one is) ruby SCL > is new requirement and replaces ruby193? For example:


Dominic Cleal
dominic@cleal.org

> I see. Would you anticipate backporting discovery 4.1 to 1.9 happening
> sooner than 1.10 going from RC to a proper release?

Not before 1.10 is released, we are in RC phase at the moment. Stay
tuned! :slight_smile:

··· -- Later, Lukas #lzap Zapletal

This looks like the issue, it's possible that one of your broken Yum
repo configs ("google_group") is causing other failures.

Try running the command "yum install foreman-postgresql" and ensure it
can succeed.

··· On 02/06/16 20:01, chandra prakash wrote: > Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-postgresql' > returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for > repository: google_group. Please verify its path and try again > /Stage[main]/Foreman::Install/Package[foreman-postgresql]/ensure: > change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e > 0 -y list foreman-postgresql' returned 1: Error: Cannot retrieve > repository metadata (repomd.xml) for repository: google_group. Please > verify its path and try again


Dominic Cleal
dominic@cleal.org

I took a fresh RHEL7.1 QCOW to install 1.10RC on, but foreman-installer
fails to install foreman-proxy and other packages. Manual attempt output:

<snip>
–> Finished Dependency Resolution
Error: Package: foreman-proxy-1.10.0-0.1.RC1.el7.noarch (foreman-1.10)
Requires: rubygem(rake) >= 0.8.3
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@foreman yum.repos.d]#

My repos are as follows:

[root@foreman yum.repos.d]# yum repolist
repo id repo name
status
local-packages-repo eBay RPM
packages 10
local-rhel-repo eBay RHEL 7Server - x86_64
4,371
local-updates-repo eBay RHEL 7Server - x86_64 -
updates 13
epel/x86_64 Extra Packages for Enterprise Linux 7
8,667
foreman-1.10/x86_64 foreman-1.10
281
foreman-plugins-1.10/x86_64 foreman-plugins-1.10
174
puppetlabs-deps/7Server/x86_64 Puppet Labs Dependencies El 7Server

  • 17
    

puppetlabs-products/7Server/x86_64 Puppet Labs Products El 7Server - x86_
191
rhscl-ruby193-epel-7-x86_64/x86_64 Ruby193 - epel-7-x86_64
405
rhscl-v8314-epel-7-x86_64/x86_64 V8 3.14.5.10 -
epel-7-x86_64 21
repolist: 14,150
[root@foreman yum.repos.d]#

Anyone else ran into this?

Rake GEM from ruby193 is already installed, BTW:

[root@foreman yum.repos.d]# yum search rubygem-rake
=================================================== N/S matched:
rubygem-rake ====================================================
rubygem-rake-compiler-doc.noarch : Documentation for rubygem-rake-compiler
ruby193-rubygem-rake.noarch : Ruby based make-like utility
rubygem-rake-compiler.noarch : Rake-based Ruby C Extension task generator

Name and summary matches only, use "search all" for everything.
[root@foreman yum.repos.d]#

[root@foreman yum.repos.d]# rpm -qa | grep rake
ruby193-rubygem-rake-0.9.2.2-49.el7.centos.noarch
[root@foreman yum.repos.d]#

> I took a fresh RHEL7.1 QCOW to install 1.10RC on, but foreman-installer
> fails to install foreman-proxy and other packages. Manual attempt output:
>
> <snip>
> --> Finished Dependency Resolution
> Error: Package: foreman-proxy-1.10.0-0.1.RC1.el7.noarch (foreman-1.10)
> Requires: rubygem(rake) >= 0.8.3

This should come from the base OS on EL7.

> [root@foreman yum.repos.d]# yum repolist
> repo id repo
> name status
> local-packages-repo eBay RPM
> packages 10
> local-rhel-repo eBay RHEL 7Server -
> x86_64 4,371
> local-updates-repo eBay RHEL 7Server - x86_64 -
> updates 13

IIRC it's in the "optional" repository.

··· On 27/10/15 21:07, 'Konstantin Orekhov' via Foreman users wrote:


Dominic Cleal
dominic@cleal.org

Unfortunately I don't have optional repo locally so have to jump through
the hoops here. I've got rubygem-rake package though, but it is now
complaining about missing ruby(abi) dependency and this one I can't locate.
Any pointers?

[root@foreman ~]# rpm -Uvh rubygem-rake-0.8.7-2.1.el6.noarch.rpm
warning: rubygem-rake-0.8.7-2.1.el6.noarch.rpm: Header V3 RSA/SHA256
Signature, key ID fd431d51: NOKEY
error: Failed dependencies:
ruby(abi) = 1.8 is needed by rubygem-rake-0.8.7-2.1.el6.noarch
[root@foreman ~]#

Meanwhile I'll try centos7 to see if it has all the packages.

> Unfortunately I don't have optional repo locally so have to jump through
> the hoops here. I've got rubygem-rake package though, but it is now
> complaining about missing ruby(abi) dependency and this one I can't
> locate. Any pointers?
>
> [root@foreman ~]# rpm -Uvh rubygem-rake-0.8.7-2.1.el6.noarch.rpm
> warning: rubygem-rake-0.8.7-2.1.el6.noarch.rpm: Header V3 RSA/SHA256
> Signature, key ID fd431d51: NOKEY
> error: Failed dependencies:
> ruby(abi) = 1.8 is needed by rubygem-rake-0.8.7-2.1.el6.noarch
> [root@foreman ~]#

That's provided in ruby-libs, should be in the main base OS repo. Use
"yum install rubygem-rake*.rpm" and it should resolve it for you.

> Meanwhile I'll try centos7 to see if it has all the packages.

Also easier!

··· On 30/10/2015 17:50, Konstantin Orekhov wrote:


Dominic Cleal
dominic@cleal.org

That suggestion did not work either - ruby libs are in place but ruby(abi)
is apparently not.

[root@foreman ~]# rpm -qa | grep ruby-libs
ruby-libs-2.0.0.598-24.el7.x86_64
ruby193-ruby-libs-1.9.3.484-49.el7.centos.x86_64

[root@foreman ~]# yum install ruby-libs
Package ruby-libs-2.0.0.598-24.el7.x86_64 already installed and latest
version
Nothing to do
[root@foreman ~]#

[root@foreman ~]# yum install rubygem-rake-0.9.2-1.el6.noarch.rpm
Examining rubygem-rake-0.9.2-1.el6.noarch.rpm:
rubygem-rake-0.9.2-1.el6.noarch
Marking rubygem-rake-0.9.2-1.el6.noarch.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package rubygem-rake.noarch 0:0.9.2-1.el6 will be installed
–> Processing Dependency: ruby(abi) = 1.8 for package:
rubygem-rake-0.9.2-1.el6.noarch
–> Finished Dependency Resolution
Error: Package: rubygem-rake-0.9.2-1.el6.noarch
(/rubygem-rake-0.9.2-1.el6.noarch)
Requires: ruby(abi) = 1.8
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

One thing is that the only rubygem-rake package I found and tried to
install is EL6 while the system is EL7. I did not find any packages
specifically for EL7…
If nobody else is complaining about this, it has to be my local issue.

Please let me know if you have any more suggestions on this.

Sorry, I missed that you were mixing versions - you can't do that. You
need the EL7 package for EL7.

··· On 30/10/15 21:44, 'Konstantin Orekhov' via Foreman users wrote: > One thing is that the only rubygem-rake package I found and tried to > install is EL6 while the system is EL7. I did not find any packages > specifically for EL7... > If nobody else is complaining about this, it has to be my local issue.


Dominic Cleal
dominic@cleal.org

Yes, I figured so I went with CentOS 7.

Install went fine, but Foreman app wouldn't start up. After a bit of
digging, I found that DB does not get created at all (Foreman does not
manage a DB install for me):

[root@centos7 ~]# foreman-rake --trace db:migraterake aborted!
Incorrect MySQL client library version! This gem was compiled for
5.5.35-MariaDB but the client library is 5.6.26-74.0.
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:55:in
require&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:55:inrequire'
/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
block in require&#39; /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:inload_dependency'
/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
require&#39; /opt/theforeman/tfm/root/usr/share/gems/gems/mysql2-0.3.19/lib/mysql2.rb:31:in<top (required)>'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require&#39; /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock in require'
/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in
load_dependency&#39; /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inrequire'
/opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:39:in
block in system_require&#39; /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:ineach'
/opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
system_require&#39; /usr/share/foreman/config/application.rb:14:in<top (required)>'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
require&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
/usr/share/foreman/Rakefile:1:in &lt;top (required)&gt;&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/rake_module.rb:25:inload'
/opt/rh/ruby193/root/usr/share/ruby/rake/rake_module.rb:25:in
load_rakefile&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:501:inraw_load_rakefile'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:82:in block in load_rakefile&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:81:in
load_rakefile&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:65:inblock in run'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun'
/opt/rh/ruby193/root/usr/bin/rake:32:in `<main>'

[root@centos7 ~]# rpm -qa | egrep -i "mysql|percona"
Percona-XtraDB-Cluster-shared-56-5.6.26-25.12.1.el7.x86_64
Percona-XtraDB-Cluster-56-5.6.26-25.12.1.el7.x86_64
Percona-XtraDB-Cluster-client-56-5.6.26-25.12.1.el7.x86_64
perl-DBD-MySQL-4.023-5.el7.x86_64
Percona-XtraDB-Cluster-server-56-5.6.26-25.12.1.el7.x86_64
Percona-XtraDB-Cluster-devel-56-5.6.26-25.12.1.el7.x86_64
tfm-rubygem-mysql2-0.3.19-2.el7.x86_64
foreman-mysql2-1.10.0-0.1.RC2.el7.noarch
Percona-XtraDB-Cluster-galera-3-3.12.2-1.rhel7.x86_64
percona-xtrabackup-2.3.2-1.el7.x86_64
[root@centos7 ~]#

Using Percona cluster was never a problem for me in previous versions. Is
MariaDB a hard-requirement now?