yahoo-eng-team team mailing list archive

[Sylvain Bauza <2012843@xxxxxxxxxxxxxxxxxx>]

This is an expected behaviour, as you can read in
https://docs.openstack.org/nova/latest/admin/availability-
zones.html#resource-affinity

If an instance is not pinned for a AZ [1] and if cross_az_attach is equal to True, then the instance can float between *all* Availability Zones.
We only pin the instance to a specific AZ if cross_az_attach=False. See the new functional test that verifies this : https://review.opendev.org/c/openstack/nova/+/878948/1/nova/tests/functional/test_cross_az_attach.py


[1] By 'pinned', I mean that either the AZ parameter for the instance is set, or the 'default_schedule_az' config option is not 'None'.


** Changed in: nova
       Status: New => Invalid

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

Title:
  Instances are free to move others zone when AZ was not specified

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===========

  Instances are free move to others zone by migrating or Masakari(host
  down) when instances dont specify you when launch and
  cross_az_attach=true.

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

  Launch instance without AZ choice(Any Availability Zone on Horizon or
  CLI).

  
  Expected result
  ===============

  Instances should move to its current AZ only when migrating or
  Masakari HA.

  Actual result
  =============

  Instances were moved to other AZs when migrating or Masakari HA.

  Environment
  ===========
  Xena
  KVM
  Openswitch
  SAN
  Provider network

  Logs & Configs
  ==============
  cross_az_attach=true.

  Any Availabily Zone when launch instance on Horizon

  Default AZ was not set in nova.conf

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