yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #86901
[Bug 1938261] Re: [ovn]Router scheduler failing for config "default_availability_zones"
Reviewed: https://review.opendev.org/c/openstack/neutron/+/802665
Committed: https://opendev.org/openstack/neutron/commit/7988ab5df0eb0799811d50eb90f0b292d008f700
Submitter: "Zuul (22348)"
Branch: master
commit 7988ab5df0eb0799811d50eb90f0b292d008f700
Author: zhouhenglc <zhouhenglc@xxxxxxxxxx>
Date: Wed Jul 28 15:25:39 2021 +0800
"default_availability_zones" need to be considered when validate az
If not set availability_zone_hits when create router, should use
configuration parameter default_availability_zones.
At present, only the creation parameters are validate, and the default
availability zones not validate.
Creating a network is the same as creating a route.
Closes-bug: #1938261
Change-Id: I1c7f50b69a31d725b762e3061f09a0bd5b077a58
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1938261
Title:
[ovn]Router scheduler failing for config "default_availability_zones"
Status in neutron:
Fix Released
Bug description:
I have 3 gateway chassis and all available zones are nova, have 1 chassis.
The default_availability_zones=zone1 are configured in the neutron.conf.
I create router and not set availability_zone_hits, I can create
router success and router's availability_zones=zone1, though ovn-nbctl
command, can found router's gateway_chassis include all chassis(4
nodes).
I think should fail in this case, indicating that the available_zone
does not exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1938261/+subscriptions
References