Bug 1409811
| Summary: | Virt-who does not respect the interval setting | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Snyder <csnyder> |
| Component: | virt-who | Assignee: | Chris Snyder <csnyder> |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.9 | CC: | aperotti, bbuckingham, bkearney, csnyder, cwelton, dcaplan, ehelms, hsun, katello-qa-list, ktordeur, mlele, ovasik, rbalakri, satellite6-bugs, shihliu, yuefliu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1405618 | Environment: | |
| Last Closed: | 2017-03-21 10:31:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Chris Snyder
2017-01-03 15:09:27 UTC
Hey Eko, In order to complete a build for rhel-6.9 including this fix, I'll need a rhel-6.9.0+. In order to get that flag I'll need a qa_ack+. Can you please add the qa_ack+? Thank you! Verified the bug on rhel6.9-20170202.0 (virt-who-0.18-3.el6.noarch) with satellite6.2.6, please refer to below steps. 1. configure virt-who with only ESX mode and 'VIRTWHO_INTERVAL=120', restart virt-who service, which will make a 'Hypervisors' task on sat webui. ->If no any trigger (like add/delete/shutdown/start guests), will no new tasks appear, just the one task shows. ->If make trigger option to guests during virt-who running, it will make new tasks each 120s as the interval value set, like below shows, no flooding tasks queue. ~~~ Action State Result ▼ Started at Ended at User Hypervisors stopped success 2017-02-09 09:50:03 +0800 2017-02-09 09:50:03 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 09:48:02 +0800 2017-02-09 09:48:02 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 09:46:01 +0800 2017-02-09 09:46:01 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 09:44:00 +0800 2017-02-09 09:44:00 +0800 foreman_api_admin 2. configure virt-who with ESX and Xen mode and 'VIRTWHO_INTERVAL=3600', restart virt-who service, which will make two 'Hypervisors' tasks on sat webui. ->If no any trigger (like add/delete/shutdown/start guests), will no new tasks appear, just the two tasks shows. ->If make trigger option to guests during virt-who running, it will make a new task each 3600s as the interval value set, like below shows, no flooding tasks queue. ~~~ Action State Result ▼ Started at Ended at User Hypervisors stopped success 2017-02-09 12:03:46 +0800 2017-02-09 12:03:46 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 11:03:44 +0800 2017-02-09 11:03:45 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 10:03:43 +0800 2017-02-09 10:03:44 +0800 foreman_api_admin Hypervisors stopped success 2017-02-09 10:03:42 +0800 2017-02-09 10:03:42 +0800 foreman_api_admin 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. https://rhn.redhat.com/errata/RHBA-2017-0675.html |