The Overcloud deployment used a default port quota of 50 for Neutron networking, which caused failures in larger deployments. This fix disables the port quota. Larger Overcloud deployments no longer fail from lack of Neutron ports.
Description of problem: The neutron port quota on the undercloud is set to 50 by default, which fails even moderately sized deployments when using network isolation.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Deploy an overcloud with 3 controllers and 10 computes
Actual results: Deployment fails due to over quota errors on Neutron ports
Expected results: Successful deployment
Ben, any clarification to the workaround we want to put in the release doc?
This is the default in puppet-neutron: https://github.com/openstack/puppet-neutron/blob/master/manifests/quota.pp#L93
Because this is the default in Neutron:
If we need such a change, I would suggest to patch tripleo-heat-template to use the puppet class and change the parameter. Can be done quickly, please let me know.
*** Bug 1251571 has been marked as a duplicate of this bug. ***
The workaround is to run "neutron quota-update --port -1" on the undercloud.
*** Bug 1261206 has been marked as a duplicate of this bug. ***
Chris, can you please set the severity field to "urgent" for this bug. We are using severity field to track the blocker issues.
Setting the severity to urgent won't change anything as far as when it's delivered. This bug is currently ON_QA, which means the bug is has been patched by a developer, and our quality engineering group is testing the fix. This bug also has a 'blocker' flag on it, which means it's critical and it must be part of the 7.1 release.
[stack@instack ~]$ rpm -qa | grep instack-undercloud
[stack@instack ~]$ neutron quota-show defaults
| Field | Value |
| network | 10 |
| port | -1 |
| security_group | 10 |
| security_group_rule | 100 |
| subnet | 10 |
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.