Reviewed: https://review.openstack.org/545494
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=d2152f309439a9d9b054a481826242ca15f5c93e
Submitter: Zuul
Branch:master
commit d2152f309439a9d9b054a481826242ca15f5c93e
Author: Eric Fried
Date: Fri Feb 16 18:18:32 2018 -0600
Only pull associated *sharing* providers
It was discussed and decided [1] that we only want to be pulling down,
caching, and passing to update_provider_tree providers associated via
aggregate with the compute node's provider tree if they are sharing
providers. Otherwise we'll get e.g. all the *other* compute nodes which
are also associated with a sharing provider.
[1]
https://review.openstack.org/#/c/540111/4/specs/rocky/approved/update-provider-tree.rst@48
Change-Id: Iab366da7623e5e31b8416e89fee7d418f7bf9b30
Closes-Bug: #1750084
** Changed in: nova
Status: In Progress => Fix Released
--
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/1750084
Title:
Report client associations include non-sharing providers
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) queens series:
In Progress
Bug description:
It was discussed and decided [1] that we only want to be pulling down,
caching, and passing to update_provider_tree providers associated via
aggregate with the compute node's provider tree if they are sharing
providers. Otherwise we'll get e.g. all the *other* compute nodes
which are also associated with a sharing provider.
[1] https://review.openstack.org/#/c/540111/4/specs/rocky/approved
/update-provider-tree.rst@48
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1750084/+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