Comment 45 for bug 1829403

from controller-0 sysinv.log.1
2019-07-19 20:50:01.036 103738 INFO sysinv.api.controllers.v1.host [-] Memory: Total=62908 MiB, Allocated=8000 MiB, 2M: 31454 pages None pages pending, 1G: 61 pages None pages pending
2019-07-19 20:50:01.064 103738 INFO sysinv.api.controllers.v1.host [-] Memory: Total=63239 MiB, Allocated=2000 MiB, 2M: 31619 pages None pages pending, 1G: 61 pages None pages pending
2019-07-19 20:50:01.085 103738 INFO sysinv.api.controllers.v1.host [-] host(compute-0) node(3): vm_mem_mib=53884,vm_mem_mib_possible (from agent) = 62908
2019-07-19 20:50:01.085 103738 INFO sysinv.api.controllers.v1.host [-] Updating mem values of host(compute-0) node(3): {'vm_hugepages_nr_4K': 1379840, 'vm_hugepages_nr_2M': 24247, 'vswitch_hugepages_nr': 1}
2019-07-19 20:50:01.187 103738 INFO sysinv.api.controllers.v1.host [-] host(compute-0) node(4): vm_mem_mib=60215,vm_mem_mib_possible (from agent) = 63238
2019-07-19 20:50:01.188 103738 INFO sysinv.api.controllers.v1.host [-] Updating mem values of host(compute-0) node(4): {'vm_hugepages_nr_4K': 1541888, 'vm_hugepages_nr_2M': 27096, 'vswitch_hugepages_nr': 1}

So, at least perform unlock action the db should be correct vswitch_hugepages_nr is 1.