yahoo-eng-team team mailing list archive

[Vasyl Saienko <2078669@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

openstack server create with --availability-zone=nova can place instance
onto the compute which belongs to non default AZ since caracal release.
The issue is introduced by removal of nova availabilityZone filter
https://review.opendev.org/c/openstack/nova/+/886779.

When using placement to filter AZs we add member_of=XXX, where XXX is
the aggregate UUID which corresponds to AZ. In case of default AZ (nova)
there is not any aggregate. As result we request computes without any
aggregate/az filtering.

** 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/2078669

Title:
  Specify --availability-zone=nova does not work since caracal

Status in OpenStack Compute (nova):
  New

Bug description:
  openstack server create with --availability-zone=nova can place
  instance onto the compute which belongs to non default AZ since
  caracal release. The issue is introduced by removal of nova
  availabilityZone filter
  https://review.opendev.org/c/openstack/nova/+/886779.

  When using placement to filter AZs we add member_of=XXX, where XXX is
  the aggregate UUID which corresponds to AZ. In case of default AZ
  (nova) there is not any aggregate. As result we request computes
  without any aggregate/az filtering.

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