yahoo-eng-team team mailing list archive

[Eric Xie <1934412@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
When 'host_topology' can not be satified with 'requested_topology',
nova-compute returns the msg to nova-conductor but there is no logs
in nova-compute.log. Thouth there are some debug logs, but `debug`
configuration is not be set to true in production environment. So
 the warning log should be added.

Steps to reproduce
==================
* Set flavor with hugepage and total ram that exceeds the limit configured on the node
openstack flavor create --vcpus 2 --ram 3000 --disk 10 --property hw:mem_page_size=2MB flv-2MB-huge
On the node:
vm.nr_hugepages = 20480
* Create one vm with the flavor
openstack server create --image 1512209c-83ca-4a64-aab5-973120e61718 --flavor flv-2MB-huge --network 44dc3e3e-5146-458b-b9b9-6b65e5282efc --availability-zone ::compute01 test-vm

Expected result
===============
Find failed logs in nova-compute.log

Actual result
=============
Find no logs, and the failed logs can be found in nova-conductor.log

Environment
===========
Libvirt + KVM

nova:
$ git log
commit 90455cdae3fae5289b07ae284db0f96e0544d9d2 (HEAD -> stable/wallaby, origin/stable/wallaby)
Merge: 97c3517e7e 5d65680095
Author: Zuul <zuul@xxxxxxxxxxxxxxxxxx>
Date:   Sun Jun 27 07:27:03 2021 +0000

    Merge "libvirt: Set driver_iommu when attaching virtio devices to
SEV instance" into stable/wallaby

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1934412

Title:
  Find none logs when not fitting numa topology in nova-compute log

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  When 'host_topology' can not be satified with 'requested_topology',
  nova-compute returns the msg to nova-conductor but there is no logs
  in nova-compute.log. Thouth there are some debug logs, but `debug`
  configuration is not be set to true in production environment. So
   the warning log should be added.

  Steps to reproduce
  ==================
  * Set flavor with hugepage and total ram that exceeds the limit configured on the node
  openstack flavor create --vcpus 2 --ram 3000 --disk 10 --property hw:mem_page_size=2MB flv-2MB-huge
  On the node:
  vm.nr_hugepages = 20480
  * Create one vm with the flavor
  openstack server create --image 1512209c-83ca-4a64-aab5-973120e61718 --flavor flv-2MB-huge --network 44dc3e3e-5146-458b-b9b9-6b65e5282efc --availability-zone ::compute01 test-vm

  Expected result
  ===============
  Find failed logs in nova-compute.log

  Actual result
  =============
  Find no logs, and the failed logs can be found in nova-conductor.log

  Environment
  ===========
  Libvirt + KVM

  nova:
  $ git log
  commit 90455cdae3fae5289b07ae284db0f96e0544d9d2 (HEAD -> stable/wallaby, origin/stable/wallaby)
  Merge: 97c3517e7e 5d65680095
  Author: Zuul <zuul@xxxxxxxxxxxxxxxxxx>
  Date:   Sun Jun 27 07:27:03 2021 +0000

      Merge "libvirt: Set driver_iommu when attaching virtio devices to
  SEV instance" into stable/wallaby

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1934412/+subscriptions