Bug #4366
Do not execute vgdisplay on hyps if FS LVM DS is not set
| Status: | Closed | Start date: | 03/07/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | Drivers - Storage | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.14 |
Description
Hi
I think that this issue is also related with http://dev.opennebula.org/issues/2912
We are getting a lot of log errors from our hyps with this message:
2016-01-26T09:39:02.796813+01:00 hyp101 sudo: oneadmin : command not allowed ; TTY=unknown ; PWD=/var/tmp/one/im/kvm-probes.d ; USER=root ; COMMAND=/sbin/vgdisplay --separator : --units m -o vg_size,vg_free --nosuffix --noheadings -C vg-one-0
but we are not using any LVM FS DS in our system.
Right now monitor_ds.sh is trying to use any probe command even if the DS or service is not set or configured in ONE. This behaviour generates a lot of noisy logs from kvm/xen hyps.
For LVM case (or any other monitoring probe) ONE should execute the sudo vgdisplay command only if any LVM DS is configured in OpenNebula db. Probably the monitor_ds script should be changed a bit..
Cheers
Alvaro
Associated revisions
bug #4366: preserve line breaks in monitor_and_log
bug #4366: add fs_lvm/monitor
bug #4366: enable fs_lvm for system ds monitoring
bug #4366: do not monitor lvm in tm/shared
bug #4366: get disk info in tm/shared monitor
bug #4366: bug getting datastores in tm/shared/monitor
History
#1
Updated by Ruben S. Montero over 5 years ago
- Target version set to Release 5.0
Review this as part of https://github.com/OpenNebula/one/pull/86 and https://github.com/OpenNebula/one/pull/72
#2
Updated by Javi Fontan about 5 years ago
- Status changed from Pending to Closed
- Assignee set to Javi Fontan
- Resolution set to fixed