opened
Ganeti-Issues-Migrator
username_0
Originally reported of Google Code with ID 143.

```
gnt-node list ignores completely the vm_capable flag on nodes, leading to RPC calls querying the hypervisor/storage being made. This leads to RS_NODATA insteadl of RS_UNAVAIL being returned for these nodes.
```
Originally added on 2011-02-17 13:26:39 +0000 UTC.
gnt-node list doesn't handle properly non-vm_capable nodes
issue
created
Ganeti-Issues-Migrator
username_0
```
This was fixed:

commit effab4c
Author: Iustin Pop <iustin@google.com>
Date:   Thu Feb 17 14:42:57 2011 +0100

    NodeQuery: mark live fields as UNAVAIL for non-vm_capable nodes
    
    Since we don't have the data per design, UNAVAIL is appropriate here,
    while NODATA is not.
    
    The patch also adds a comment: if we extend the live fields list to
    contain other data in the future, we need to reevaluate this solution.
    
    This should fix issue 143. The listing now shows (node2==ofline,
    node3==not vm_capable):
    
      Node     DTotal     DFree    MTotal     MNode     MFree Pinst Sinst
      node1    698.6G    630.5G     32.0G      1.0G     30.0G     8     7
      node2 (offline) (offline) (offline) (offline) (offline)     9     4
      node3 (unavail) (unavail) (unavail) (unavail) (unavail)     0     0
    
    Signed-off-by: Iustin Pop <iustin@google.com>
    Reviewed-by: Michael Hanselmann <hansmi@google.com>

commit 74f258b
Author: Iustin Pop <iustin@google.com>
Date:   Thu Feb 17 14:41:29 2011 +0100

    NodeQuery: don't query non-vm_capable nodes
    
    Because non-vm_capable nodes most likely don't have a hypervisor
    configured and/or storage, so the call will fail anyway.
    
    

```
Originally added on 2011-02-18 13:40:58 +0000 UTC.

Mentioned Issue with GoogleCode ID 143 has been migrated to GitHub with ID #199.
Changed State: Fixed
comment
created
Ganeti-Issues-Migrator
username_0
```
-- Empty comment --
```
Originally added on 2012-10-22 08:57:08 +0000 UTC.

Changed State: Released
comment
closed
Ganeti-Issues-Migrator
username_0
issue