Bug #1206
Max disk, used disk (allocated and real) always report zero
Status: | Closed | Start date: | 04/06/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Resolution: | worksforme | Pull request: | ||
Affected Versions: | OpenNebula 3.2 |
Description
When monitoring a host, for instance with onehost show, I always get:
MAX DISK : 0 USED DISK (REAL) : 0 USED DISK (ALLOCATED) : 0
Due to this erroneous report, sometimes VMs get deployed on a host that does not have enough disk space.
Cheers!
--
Dario Berzano / INFN & Università - Torino, Italy
Related issues
History
#1 Updated by Giovanni Toraldo over 9 years ago
If this is a monitoring issue, can you provide additional information about your storage configuration and oned.log errors if any?
#2 Updated by Dario Berzano about 9 years ago
I have hosts which use the LVM transfer manager and hosts which use the shared one: "DISK" parameters are zero in both cases.
No errors in logfile (debug loglevel is enabled): the only messages related to host monitoring all look like the following lines:
Tue Apr 10 16:21:13 2012 [InM][D]: Host 36 successfully monitored. Tue Apr 10 16:21:13 2012 [InM][I]: ExitCode: 0 Tue Apr 10 16:21:13 2012 [InM][D]: Host 17 successfully monitored. Tue Apr 10 16:21:13 2012 [InM][I]: ExitCode: 0
I don't know if it is a monitoring issue. Disk, CPU and memory are considered "host shares" and appear as such when running onehost show:
HOST SHARES MAX MEM : 49412684 USED MEM (REAL) : 5636156 USED MEM (ALLOCATED) : 32665600 MAX CPU : 2400 USED CPU (REAL) : 9 USED CPU (ALLOCATED) : 1200 MAX DISK : 0 USED DISK (REAL) : 0 USED DISK (ALLOCATED) : 0 RUNNING VMS : 2
At least for the "ALLOCATED" parameters, they are not updated asynchronously at each monitoring cycle; instead, AFAIK, they are immediately updated when a VM is assigned to a certain host. Maybe these parameters are not (yet) implemented?
Cheers
--
Dario Berzano / INFN & Università - Torino, Italy
Giovanni Toraldo wrote:
If this is a monitoring issue, can you provide additional information about your storage configuration and oned.log errors if any?
#3 Updated by Ruben S. Montero over 8 years ago
- Status changed from New to Closed
- Resolution set to worksforme
The host storage is not being monitored currently. Closing this one as there is a feature to address this