Bug 1963064

Summary: openvswitch conf.db consuming all FS space rapidly
Product: Red Hat OpenStack Reporter: Ganesh Kadam <gkadam>
Component: rhosp-openvswitchAssignee: ffernand <ffernand>
Status: CLOSED DUPLICATE QA Contact: RHOS Maint <rhos-maint>
Severity: high Docs Contact:
Priority: high    
Version: 16.1 (Train)CC: mburns, twilson
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovn2.13-20.12.0-19 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 14:04:17 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:
Bug Depends On: 1903210    
Bug Blocks:    

Comment 1 ffernand 2021-05-25 14:04:17 UTC 
Looking at the attached log [1], I can see that br-int is being hit with many updates from ovn-controller to the br-int's external ids, wrt ct-zones.

This has been fixed in  ovn2.13-20.12.0-19 via bz 1903210


[1]: 
https://access.redhat.com/support/cases/#/case/02935562/discussion?attachmentId=a092K00002ZdbzEQAR

PS. Small request (for next time): please include ovn version used.

```
...
record 301288: 2021-05-14 14:47:01.345 "ovn-controller
ovn-controller: modifying OVS tunnels 'f422b688-8b03-4b7f-a002-d8303703e5d8'"
  table Bridge row "br-int" (1483151f):
    external_ids={ct-zone-01a33427-2c77-42a5-8796-92d452a7121e="1", ct-zone-0298e313-cd17-4640-8c71-cbb01e01f617="1", ct-zone-02dffc36-0c21-46ee-9997-4c8324b7be61="1", ct-zone-0641ec2c-f74c-4c56-a9c9-e9057c8071c0="1", ct-zone-078cd2a4-f536-4b36-86d1-b3d99133df3e="32", ct-zone-0d0126eb-2d04-4207-9e6a-0a0327062083="54", ct-zone-0df220b5-5bd2-48a6-ba56-831daecb0d36="1", ct-zone-0df2215d-d065-4229-804a-39aa9ce8b3e4="1", ct-zone-0f90e4a8-fc69-4c5e-867b-d63d2e4aa6bc="34", ct-zone-0fd4c621-48c5-4356-9c7b-ad3abe39668f="57", ct-zone-104ed383-df9a-47b6-96df-b99aed01998a="1", ct-zone-110209ed-2...
```

*** This bug has been marked as a duplicate of bug 1903210 ***