Bug 1658284 - [RFE] Allow virt-who-configure plugin to have additional interval options
Summary: [RFE] Allow virt-who-configure plugin to have additional interval options
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.6.0
Assignee: Marek Hulan
QA Contact: Eko
Depends On:
Blocks: 1602034
TreeView+ depends on / blocked
Reported: 2018-12-11 16:53 UTC by Rich Jerrido
Modified: 2020-06-22 18:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Three new intervals for the virt-who configuration have been added: 24 hours, 2 days, and 3 days. You can now configure Satellite to run the virt-who at the following intervals: every hour, every 2 hours, every 4 hours, every 8 hours, every 12 hours, every 24 hours, every 2 days, or every 3 days.
Clone Of:
Last Closed: 2019-10-22 12:47:06 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25747 0 Normal Closed Allow virt-who-configure plugin to have additional interval options 2020-09-23 20:52:12 UTC
Red Hat Product Errata RHSA-2019:3172 0 None None None 2019-10-22 12:47:21 UTC

Description Rich Jerrido 2018-12-11 16:53:20 UTC
Description of problem:

The least frequent a user can configure the virt-who-configure plugin is to run every 24 hours. In large environments, you may way to run virt-who as infrequent as 2 to 3 days. 

This RFE requests these in the drop down menus as options

Comment 4 Marek Hulan 2018-12-20 20:20:29 UTC
Created redmine issue https://projects.theforeman.org/issues/25747 from this bug

Comment 5 pm-sat@redhat.com 2018-12-21 11:06:18 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25747 has been resolved.

Comment 6 patalber 2019-02-11 21:11:51 UTC
The case recently attached if for a customer who is interested in shorter intervals than one hour. They would like as short as 1 minute. They have done with manually, but believe that other customers with smaller deployments would benefit.

"Yes, unfortunately there's no events to trigger virt-who to update the guest's UUID immediately after adding a guest with ESX mode.
>>> You can set shorter checking interval as a workaround (--interval option or VIRTWHO_INTERVAL in /etc/sysconfig/virt-who).

We need a 2 minutes interval or so for us to be able to provision new virtual machines that can get registered with the sattelite/pulp.
Hammer cli and the web inteface only let you set higher intervals like : 

[root@satellite-02 ~]# hammer virt-who-config update --name afis-devops --interval 1
Could not create the Virt Who configuration:
  Error: Option '--interval': Value must be one of '60', '120', '240', '480', '720'..

(which are minutes, as observed, not seconds as documented)

Workaround :

I edited the DB directly :

psql: update foreman_virt_who_configure_configs set interval=1 where id = 1;

^ this will result in a 60 secs VIRTWHO_INTERVAL. 

Thus now, unless you modify the conf via web interface you can run 
#hammer virt-who-config deploy --id 1
without overwriting the 60 secs interval. 

And you can now seem to be able use hammer to update the other params without touching the interval.

How can we set lower intervals ? 

I think at least 1, 5 and 30 minutes would be soem useful settings for small deployments."

Comment 8 Rich Jerrido 2019-02-11 22:30:03 UTC
Satellite includes temporary subscriptions which help with provisioning guests which are EXPLICITLY designed to prevent customers from running virt-who too frequently. 

6.2.11 and earlier had a 1 day temporary sub
6.2.12 and newer had a 7 day temporary sub

If the user feels the need to run virt-who very frequently, it is indicative of their activation keys being busted. See https://access.redhat.com/blogs/1169563/posts/2867891 for guidance on configuring activation keys.

Comment 12 errata-xmlrpc 2019-10-22 12:47:06 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.