yahoo-eng-team team mailing list archive

[Stephen Finucane <1882821@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Per title, the '[libvirt] file_backed_memory' and '[DEFAULT]
reserved_host_memory_mb' config options are incompatible. Not only does
'[DEFAULT] reserved_host_memory_mb' not really make sense for file
backed memory (if you want to reserve "memory", configure a lower
'[libvirt] file_backed_memory' value) but configuring a value for
'[libvirt] file_backed_memory' that is lower than the value for
'[DEFAULT] reserved_host_memory_mb', which currently defaults to 512MB,
will break nova's resource reporting to placement:

  nova.exception.ResourceProviderUpdateFailed: Failed to update resource
provider via URL
/resource_providers/f39bde61-6f73-4ccb-9488-6efb9689730f/inventories:
{"errors": [{"status": 400, "title": "Bad Request", "detail": "The
server could not comply with the request since it is either malformed or
otherwise incorrect.\n\n Unable to update inventory for resource
provider f39bde61-6f73-4ccb-9488-6efb9689730f: Invalid inventory for
'MEMORY_MB' on resource provider 'f39bde61-6f73-4ccb-9488-6efb9689730f'.
The reserved value is greater than total.  ", "code":
"placement.undefined_code", "request_id": "req-977e43e7-1a7c-4309-96ec-
49a75bdea58a"}]}

Ideally we should error out if both values are configured, however,
doing so would be a breaking change. Instead, we can warn if these are
incompatible and then error our in a future release.

** Affects: nova
     Importance: Medium
     Assignee: Stephen Finucane (stephenfinucane)
         Status: Confirmed

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova
     Assignee: (unassigned) => Stephen Finucane (stephenfinucane)

** Changed in: nova
       Status: New => Confirmed

-- 
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/1882821

Title:
  '[libvirt] file_backed_memory' and '[DEFAULT] reserved_host_memory_mb'
  are incompatible

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Per title, the '[libvirt] file_backed_memory' and '[DEFAULT]
  reserved_host_memory_mb' config options are incompatible. Not only
  does '[DEFAULT] reserved_host_memory_mb' not really make sense for
  file backed memory (if you want to reserve "memory", configure a lower
  '[libvirt] file_backed_memory' value) but configuring a value for
  '[libvirt] file_backed_memory' that is lower than the value for
  '[DEFAULT] reserved_host_memory_mb', which currently defaults to
  512MB, will break nova's resource reporting to placement:

    nova.exception.ResourceProviderUpdateFailed: Failed to update
  resource provider via URL
  /resource_providers/f39bde61-6f73-4ccb-9488-6efb9689730f/inventories:
  {"errors": [{"status": 400, "title": "Bad Request", "detail": "The
  server could not comply with the request since it is either malformed
  or otherwise incorrect.\n\n Unable to update inventory for resource
  provider f39bde61-6f73-4ccb-9488-6efb9689730f: Invalid inventory for
  'MEMORY_MB' on resource provider
  'f39bde61-6f73-4ccb-9488-6efb9689730f'. The reserved value is greater
  than total.  ", "code": "placement.undefined_code", "request_id":
  "req-977e43e7-1a7c-4309-96ec-49a75bdea58a"}]}

  Ideally we should error out if both values are configured, however,
  doing so would be a breaking change. Instead, we can warn if these are
  incompatible and then error our in a future release.

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