From 4f44011d1641798feaa3e072a023bf2894dce164 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Wed, 6 Apr 2016 12:54:33 -0400 Subject: [PATCH] Fix typo in compute node mega join comments The actual key name is inv_local_gb and that's what the ComputeNode object code is going to be checking during the online data migration. Change-Id: I3daa18b08373e3f0917093f3f043bf69b68b60dc --- nova/db/sqlalchemy/api.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nova/db/sqlalchemy/api.py b/nova/db/sqlalchemy/api.py index 9c086aba0e1f..d70fc6e44dec 100644 --- a/nova/db/sqlalchemy/api.py +++ b/nova/db/sqlalchemy/api.py @@ -636,12 +636,12 @@ def _compute_node_select(context, filters=None): # - inv_vcpus, inv_vcpus_used, inv_cpu_allocation_ratio # - inv_local_gb, inv_local_gb_used, inv_disk_allocation_ratio # These resource capacity/usage fields store the total and used values - # for those three resource classes that are currently store in similar + # for those three resource classes that are currently stored in similar # fields in the compute_nodes table (e.g. memory_mb and memory_mb_used) # The code that runs the online data migrations will be able to tell if # the compute node has had its inventory information moved to the # inventories table by checking for a non-None field value for the - # inv_memory_mb, inv_vcpus, and inv_disk_gb fields. + # inv_memory_mb, inv_vcpus, and inv_local_gb fields. # # The below SQLAlchemy code below produces the following SQL statement # exactly: