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 1525930 - [RFE]Virt-who configure plugin should make configuration fully automatic
Summary: [RFE]Virt-who configure plugin should make configuration fully automatic
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Katello QA List
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-14 12:48 UTC by Stefan Nemeth
Modified: 2019-06-07 11:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-08 18:54:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22122 0 Normal New Virt-who configure plugin should make configuration fully automatic 2020-12-21 08:19:32 UTC
Red Hat Bugzilla 1523387 0 unspecified CLOSED Modifying a virt-who configuration does not modify the conf file in /etc/virt-who.d 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1529260 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1523387 1529260

Description Stefan Nemeth 2017-12-14 12:48:16 UTC 
Description of problem:
When virt-who configuration is modified, manual action to alter the config files is needed.
Also when entry from satellite webui is deleted, virt-who config file from /etc/virt-who.d/ is not deleted and configuration not altered, so the config file needs to be deleted manually.


Version-Release number of selected component (if applicable):
6.3.0 

How reproducible:
100%

Steps to Reproduce:
1.create virt-who config and apply it
2.delete the profile fom satellite
3.check filesystem in /etc/virt-who.d/

Actual results:
config file of deleted profile is still present

Expected results:
config file deleted or modified to configname.config.backup to prevent accidental total deletions, with everything commented out


Additional info:
This should be possible to achieve by adding a drop-down menu or check-boxes which will allow to choose where the config will be deployed. 
If on satellite than hammer can be called, if on content host, than it would be possible to use either puppet or job to create the required configs, or if just config script is needed.
Comment 1 Stefan Nemeth 2017-12-14 12:53:02 UTC 
also virt-who, since 6.2 , is usually deployed on Satellite itself from my experience.
Comment 2 Marek Hulan 2017-12-18 12:34:03 UTC 
It would definitely use the same deploy mechanism for both Satellite host or other host. Note that Satellite can't simply run hammer, we need root permissions but Satellite web process runs under non-root user. I guess we'd use REX for all such operations. There's a parameter in installer that one could use to have Satellite ready for managing using REX. It configures internal capsule SSH key so user run jobs against Satellite host right after installation. It's disabled by default as we don't want to open this channel without user knowing.
Comment 3 Marek Hulan 2018-01-03 07:57:24 UTC 
Created redmine issue http://projects.theforeman.org/issues/22122 from this bug
Comment 4 Bryan Kearney 2018-03-08 18:54:05 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.