yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1765334@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

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

Title:
  Ironic resource class may not be put into inventory in Pike

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description
  ===========
  An instance may not be created with a flavor which using a resource class for a bare metal node when a resource class is set to a bare metal node in ironic with 'openstack baremetal node set' command after the node is once enrolled.

  It seems that this issue was fixed in the Queens with this patch[1].

  [1] https://review.openstack.org/#/c/518294/

  Steps to reproduce
  ==================

  1. Enroll a node in ironic without a resource class
    $ openstack baremetal node create mynode

  2. Set a resouce class to the node later
    $ openstack baremetal node set mynode --resource-class baremetal

  3. Associate a flavor with the resource class
    $ openstack flavor set baremetal --property resources:CUSTOM_BAREMETAL=1

  4. Create an instance with the flavor
    $ openstack server create myinstance --flavor baremetal

  Expected result
  ===============
  Succeeds in creating an instance in a node with the specified resource class.

  Actual result
  =============
  No valid host was found.

  A custom resource class was not registered into the resource provider.
  $ curl -sH "X-Auth-Token: $token" -X GET $url/resource_providers/$uuid/inventories | python -m json.tool
  {
      "inventories": {
          "DISK_GB": {
              "allocation_ratio": 1.0,
              "max_unit": 4080,
              "min_unit": 1,
              "reserved": 0,
              "step_size": 1,
              "total": 4080
          },
          "MEMORY_MB": {
              "allocation_ratio": 1.0,
              "max_unit": 196608,
              "min_unit": 1,
              "reserved": 0,
              "step_size": 1,
              "total": 196608
          },
          "VCPU": {
              "allocation_ratio": 1.0,
              "max_unit": 28,
              "min_unit": 1,
              "reserved": 0,
              "step_size": 1,
              "total": 28
          }
      },
      "resource_provider_generation": 1
  }

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

  Pike

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)

  Ironic

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