Description of problem:
When creating virt-who config from the satellite webui the virt-who config plugin adds option 'env=' to the virt-who configuration file. This is an issue because when virt-who runs with available 'env=', it still products warning - 'Ignoring unknown configuration option "env"'.
Version-Release number of selected component (if applicable):
tfm-rubygem-foreman_virt_who_configure-0.5.2-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Satellite Webui > Infrastructure > Clic on virt-who configurations > Create config > fill in the information > submit
2. Once this virt-who config is deployed you will observe the option "env=" in the etc/virt-who.d/virt-who.conf
3. In /var/log/messages you will observe something like:
[virt-who-config-2]: Ignoring unknown configuration option "env"
Actual results:
The following warning message is generated :
/usr/bin/virt-who[5298]: 2020-05-08 13:38:13,511 [virtwho.rhsm_log WARNING] MainProcess(5298):MainThread @config.py:init_config:1532 - [virt-who-config-2]: Ignoring unknown configuration option "env"
Expected results:
No warning messages
Suggested Solution:
I suggest the solution removing the 'env=Library' from file: /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_virt_who_configure-0.5.2/app/models/foreman_virt_who_configure/output_generator.rb
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:8506