Currently if the quota_port, quota_network, quota_subnet values
in the neutron.conf are set to a negative value not equal to -1,
neutron reports the values as is to consumers like Nova.
Nova treats -1 as the infinite quota indicator and doesn't expect
neutron to return any other non-negative value.
The fix allows the flexibility of having any negative number for the
quota parameters in the neutron.conf file and allows the nova boot
to succeed subsequently. The fix would report any negative value
as -1 for port, subnet and network.
Reviewed: https:/ /review. openstack. org/170061 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=2041ead12d1 bf4c2b03fd980fd 2a6ce5f653dcfb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2041ead12d1bf4c 2b03fd980fd2a6c e5f653dcfb
Author: Sudipta Biswas <email address hidden>
Date: Thu Apr 2 15:06:35 2015 +0530
Treat all negative quota values as -1
Currently if the quota_port, quota_network, quota_subnet values
in the neutron.conf are set to a negative value not equal to -1,
neutron reports the values as is to consumers like Nova.
Nova treats -1 as the infinite quota indicator and doesn't expect
neutron to return any other non-negative value.
The fix allows the flexibility of having any negative number for the
quota parameters in the neutron.conf file and allows the nova boot
to succeed subsequently. The fix would report any negative value
as -1 for port, subnet and network.
Change-Id: Ib9a7136b0bfd01 bdf04a5d0937854 590029b1010
Closes-Bug: 1438738
Co-Authored-By: Salvatore Orlando <email address hidden>