Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1848605

Summary: VM creation instability due to neutron issues.
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: openstack-neutronAssignee: Rodolfo Alonso <ralonsoh>
Status: CLOSED ERRATA QA Contact: Alex Katz <akatz>
Severity: urgent Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: akaris, amuller, chrisw, ekuris, ralonsoh, scohen
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: openstack-neutron-12.1.1-25.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-28 18:33:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Hill 2020-06-18 15:24:43 UTC 
To workaround our scale issue as reported in the cases with case numbers: 02651054, 02646377, we adjusted the following settings in our OpenStack nodes.

1. Set ovsdb_timeout = 30 under ovs section of /var/lib/config-data/puppet-generated/neutron/etc/neutron/l3_agent.ini as well as /var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini.

2. Set of_inactivity_probe = 30 under ovs section of /var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini

3. Set ovsdb_interface = vsctl under ovs section of /var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini.

4. Then, restarted the neutron_ovs_agent neutron_metadata_agent neutron_l3_agent containers on all the controller and compute nodes.

5. Manually set inactivity_probe to 30000 on all the controller and compute nodes using the following command syntax.
ovs-vsctl set Manager $UUID inactivity_probe=30000, where $UUID is the value of the unique _uuid on every node.

Now, we are seeing a lot of ovs-vsctl command errors in logs, like the following.
```
neutron.agent.ovsdb.impl_vsctl [req-5dde0afc-addc-4934-827f-d67e778c9479 - - - - -] Unable to execute ['ovs-vsctl', '--timeout=30', '--oneline', '--format=json']. Exception: Exit code: 1; Stdin: ; Stdout: ; Stderr: ovs-vsctl: missing command name (use --help for help)
```
I am guessing that changing the ovsdb_interface from native to vsctl might be why we are seeing these error logs.
We made the aforementioned changes referring the suggestions Red Hat Support made in the cases with case numbers: 02651054, and 02646377. After making the change, we were certainly able to create more number of instances but with more wait times.
Comment 19 errata-xmlrpc 2020-10-28 18:33:16 UTC 
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 (openstack-neutron bug fix 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.

https://access.redhat.com/errata/RHBA-2020:4397