yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #96624
[Bug 2126032] Re: [CI] Random failure network create with Error while executing command: HttpException: 503, Unable to create the network. No tenant network is available for allocation.
Reviewed: https://review.opendev.org/c/openstack/neutron/+/963704
Committed: https://opendev.org/openstack/neutron/commit/78c14b72256d5f8272a5666fcc841fccb52e5b8b
Submitter: "Zuul (22348)"
Branch: master
commit 78c14b72256d5f8272a5666fcc841fccb52e5b8b
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Fri Oct 10 13:20:57 2025 +0000
Restore the value of FIRST_WORKER_ID that should be 1
This constant was modified in [1]. This is preventing, for example, the
initialization of the network segment ranges in the database.
[1]https://review.opendev.org/c/openstack/neutron/+/947898
Closes-Bug: #2126032
Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Change-Id: I12243a86cd0e95fbd231c99d671454f85834c149
** 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/2126032
Title:
[CI] Random failure network create with Error while executing command:
HttpException: 503, Unable to create the network. No tenant network is
available for allocation.
Status in neutron:
Fix Released
Bug description:
Job failed during devstack setup while network create with:-
2025-09-25 10:31:49.695736 | controller | ++ lib/neutron_plugins/services/l3:create_neutron_initial_network:202 : oscwrap --os-cloud devstack --os-region RegionOne network create private -f value -c id
2025-09-25 10:32:10.579557 | controller | Error while executing command: HttpException: 503, Unable to create the network. No tenant network is available for allocation.
2025-09-25 10:32:10.580958 | controller |
2025-09-25 10:32:10.602842 | controller | ++ functions-common:oscwrap:2468 : return 1
Network type is geneve
Example failures:-
- https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_d2d/openstack/d2d864e0808642f485a82f714758c959/job-output.txt
- https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_808/openstack/808a83ed5e9e488683b04db133bcf1a6/job-output.txt
- https://6b63d007c735178e577a-a21c5a2f7ec31a719791313ddc031133.ssl.cf1.rackcdn.com/openstack/a1e71fa61dd841d3a2feb277e1130737/job-output.txt
opensearch:-
'https://opensearch.logs.openstack.org/_dashboards/app/data-
explorer/discover?security_tenant=global#?_a=(discover:(columns:!(_source),isDirty:!f,sort:!()),metadata:(indexPattern:'94869730-aea8-11ec-9e6a-83741af3fdcd',view:discover))&_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30d,to:now))&_q=(filters:!(),query:(language:kuery,query:'message:%22No%20tenant%20network%20is%20available%20for%20allocation%22'))'
Till now seen in below jobs in check queue:-
osc-functional-devstack
neutron-tempest-plugin-designate-scenario
neutron-tempest-plugin-designate-scenario-2025.1
neutron-tempest-plugin-tap-as-a-service-ovn-2025.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2126032/+subscriptions
References