yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

This is considered as designed, so will not be fixed.

It complicates the general case of mapping from ironic resource classes
to placement resource classes.

I still think this is going to trip up many Ironic administrators. The
docs are not clear that CUSTOM_FOO maps to CUSTOM_CUSTOM_FOO.

** No longer affects: nova/pike

** Changed in: nova
       Status: In Progress => Won't Fix

** Changed in: nova
     Assignee: John Garbutt (johngarbutt) => (unassigned)

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

Title:
  Ironic nodes report CUSTOM_CUSTOM_FOO resource class

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Currently if you set CUSTOM_FOO in ironic, the virt driver now sends
  CUSTOM_CUSTOM_FOO to placement.

  Really we shouldn't force users to drop the CUSTOM_ inside ironic.

  Expected:
  User sets CUSTOM_FOO in ironic.
  Placement shows CUSTOM_FOO resources.

  Actual:
  Placement shows CUSTOM_CUSTOM_FOO resources

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