diff options
| author | Vasyl Saienko <vsaienko@mirantis.com> | 2016-08-12 11:35:14 +0300 |
|---|---|---|
| committer | Vasyl Saienko <vsaienko@mirantis.com> | 2016-09-02 10:42:04 +0300 |
| commit | bfddae67056a8040b61b7137b9eb9deb6e6565fb (patch) | |
| tree | a6fe0ede35f2da45ffd94833976b02bdc775778d /releasenotes | |
| parent | 3b97d5392185b7f8d54cd5d51121ae6a18a12e05 (diff) | |
| download | ironic-bfddae67056a8040b61b7137b9eb9deb6e6565fb.tar.gz | |
Remove neutron client workarounds
We have a workarounds for cases when calling neutronclient.create_port()
or neutronclient.list_ports() may return ports with empty id, or empty
data, without raising an exception. These workarounds mask the neutron
bugs rather than fixing the root cause.
Also for example Nova doesn't have such workarounds, please see
references. This changes removes the workarounds.
Also provisioning will be interrupted with NetworkError() only when we
failed to create all Neutron ports in provisioning network, if at least
one port is created successfully we proceed with deployment.
Reference:
[0]https://github.com/openstack/nova/blob/71c007d9/nova/network/neutronv2/api.py#L1071
[1]https://github.com/openstack/nova/blob/71c007d9/nova/network/neutronv2/api.py#L315
Change-Id: I96cab32b1262efe710de06596626e01c50e457b0
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/remove-neutron-client-workarounds-996c59623684929b.yaml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/releasenotes/notes/remove-neutron-client-workarounds-996c59623684929b.yaml b/releasenotes/notes/remove-neutron-client-workarounds-996c59623684929b.yaml new file mode 100644 index 000000000..9644ca3fd --- /dev/null +++ b/releasenotes/notes/remove-neutron-client-workarounds-996c59623684929b.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - Update create provisioning ports logic to fail only + when no neutron ports were created. If we created at + least one neutron port, proceed with the deployment. + It was the default behaviour for flat scenario. |