Description of problem: While creating new config file Infrastructure --> Virt-who Configurations --> Create Config there is option "Interval" to mention under Schedule Each time you create a new config file and if changed this Interval option then it changes the virt-who_interval in /etc/sysconfig file. Eg. created first esx config file and set Interval = 2 hours. Then created second rhevm config file and set Interval = 1 hour Running # hammer virt-who-config deploy --id 2 on satellite server will overide /etc/sysconfig/virt-who file and set virt-who interval as 3600 which was earlier 7200. ----------------------- So here should be a naming change for Schedule as "Global schedule" file or something more meaningful and a message should be displayed in information box as it will affect your global settings and this is not the local setting for that config file. Version-Release number of selected component (if applicable): satellite 6.3.0 25.0 virt-who-0.19-6.el7_4.noarch foreman-1.15.6.9-1.el7sat.noarch
This is known behavior caused by the virt-who limitation. Virt-who does not support custom interval per hyprevisor. There's no way we can configure virt-who this way to my knowledge. Users are recommended to use 2 hours as a default value. Ideally this should be documented (mind to open a doc-bug?) I opened a BZ 1517741 for virt-who itself, until that's resolved we can't do much more.
Created redmine issue http://projects.theforeman.org/issues/21775 from this bug
Hi Marek, Until we have support for configuration based "Interval" implemented in core virt-who. Can we have a Helper text for Interval to say this "Interval value specified here is a global parameter, which will affect all virt-who configurations". Attaching a screenshot, after fixing the helper text.
Created attachment 1360127 [details] Interval helper text, after modifying the text.
absolutely, since you seem to have the patch ready, would you mind sending a PR to https://github.com/theforeman/foreman_virt_who_configure/pulls ? If not, I can create it myself, but I'll need to find someone for review or wait until Tomas is back from long PTO. I'd just rephrase this a bit to e.g. "Different interval can't be set per hypervisor, therefore it will affect all other deployed configurations on the host on which this configuration will be deployed." A "global parameter" is already a term for something else in Sat 6, also it only affects configurations on the shared host. It might be worth of also creating documentation bug so it's covered.
we've agreed I'll send the patch, so cancelling the needinfo it's now available in upstream for testing, see the linked redmine issue for more details
(In reply to Marek Hulan from comment #1) > This is known behavior caused by the virt-who limitation. Virt-who does not > support custom interval per hyprevisor. There's no way we can configure > virt-who this way to my knowledge. > > Users are recommended to use 2 hours as a default value. Ideally this should > be documented (mind to open a doc-bug?) I opened a BZ 1517741 for virt-who > itself, until that's resolved we can't do much more. ------------------- Document Bug raised https://bugzilla.redhat.com/show_bug.cgi?id=1523484
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.