Public bug reported:
When CONF.scheduler_use_baremetal_filters is set, and IronicHostManager
is in use, the default scheduler filters should be as defined by
CONF.baremetal_scheduler_default_filters. This is done in
IronicHostManager's __init__ method.
However, __init__ calls the superclass' __init__ method before setting
the default filters, and so the change isn't picked up by the base
HostManager. Thus this setting does nothing.
** 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/1439868
Title:
Ironic: CONF.scheduler_use_baremetal_filters doesn't have any effect
Status in OpenStack Compute (Nova):
New
Bug description:
When CONF.scheduler_use_baremetal_filters is set, and
IronicHostManager is in use, the default scheduler filters should be
as defined by CONF.baremetal_scheduler_default_filters. This is done
in IronicHostManager's __init__ method.
However, __init__ calls the superclass' __init__ method before setting
the default filters, and so the change isn't picked up by the base
HostManager. Thus this setting does nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1439868/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
