yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20447
[Bug 1347778] Re: raising Maximum number of ports exceeded is wrong
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => juno-3
--
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/1347778
Title:
raising Maximum number of ports exceeded is wrong
Status in OpenStack Compute (Nova):
Fix Released
Status in Python client library for Neutron:
Fix Released
Bug description:
When neutron API in nova calls create_port(), it looks for exceptions.
Any 409 is turned into 'Maximum number of ports exceeded'. This is a
horrible assumption. Neutron can return 409s for more than just this
reason.
Another case where neutron returns a 409 is this:
2014-07-22 18:10:27.583 26577 INFO neutron.api.v2.resource [req-b7267ae5-bafa-4c34-8e25-9c0fca96ad2d None] create failed (client error):
Unable to complete operation for network 00000000-0000-0000-0000-000000000000. The mac address XX:XX:XX:XX:XX:XX is in use.
This can occur when the request to create a port includes the mac
address to use (as happens w/ baremetal/ironic in nova) and neutron
for some reason still has things assigned with that mac.
This is the offending code:
174 except neutron_client_exc.NeutronClientException as e:
175 # NOTE(mriedem): OverQuota in neutron is a 409
176 if e.status_code == 409:
177 LOG.warning(_('Neutron error: quota exceeded'))
178 raise exception.PortLimitExceeded()
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1347778/+subscriptions
References