Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1834897 - [RFE] Remove the configuration 'env=Library' created by the virt-who configuration plugin in the Satellite WebUI
Summary: [RFE] Remove the configuration 'env=Library' created by the virt-who configur...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.7.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: 6.12.0
Assignee: Marek Hulan
QA Contact: Kunxin Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-12 15:43 UTC by Dulce Higuera
Modified: 2023-09-07 23:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:32:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35081 0 High New Remove the configuration 'env=Library' created by the virt-who configuration plugin in the Satellite WebUI 2022-06-17 17:54:38 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:32:35 UTC

Description Dulce Higuera 2020-05-12 15:43:00 UTC 
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
Comment 6 Lucy Fu 2022-06-17 17:54:37 UTC 
Created redmine issue https://projects.theforeman.org/issues/35081 from this bug
Comment 7 Bryan Kearney 2022-06-22 00:02:02 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35081 has been resolved.
Comment 12 errata-xmlrpc 2022-11-16 13:32:23 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.