Network gets created even though service responds with 503
Bug #1436813 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
Medium
|
Eugene Nikanorov | ||
6.0.x |
Won't Fix
|
Medium
|
Eugene Nikanorov | ||
6.1.x |
Fix Released
|
Medium
|
Eugene Nikanorov |
Bug Description
When gre/vxlan network can't be created, neutron server responds with 503 error code, but network still gets created.
Apparently this is a regression of fix to https:/
Repro steps:
1) configure neutron server in such way that networks can't be created
2) create network (neutron net-create test-net), this should give 503 HTTP code
3) run 'neutron net-list' and make sure that 'test-net' is in the list.
description: | updated |
Changed in mos: | |
milestone: | none → 6.1 |
Changed in mos: | |
status: | New → Confirmed |
tags: | added: neutron |
tags: | added: scale |
To post a comment you must log in.
package neutron has been built for project openstack/neutron mira18. git.6747804. 77552d2
Package version == 2014.2.2, package release == fuel6.1.
Changeset: https:/ /review. fuel-infra. org/4994 ci/fuel- 6.1/2014. 2
project: openstack/neutron
branch: openstack-
author: Eugene Nikanorov
committer: Eugene Nikanorov
subject: Make proper fix for concurrent gre network creation
status: patchset-created
Files placed on repository:
NOTE: Changeset is not merged, created temporary package repository. fuel-6. 1-stable- 4994/
repository URL: /centos-