Bug 1757876
Summary: | kuryr-controller stuck in CrashLoopBack and no pod creation possible after running OCP functional automation. | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> | ||||
Component: | Networking | Assignee: | Luis Tomas Bolivar <ltomasbo> | ||||
Networking sub component: | kuryr | QA Contact: | GenadiC <gcheresh> | ||||
Status: | CLOSED DUPLICATE | Docs Contact: | |||||
Severity: | urgent | ||||||
Priority: | unspecified | CC: | bbennett, juriarte, mdulko | ||||
Version: | 4.2.0 | Keywords: | TestBlocker | ||||
Target Milestone: | --- | ||||||
Target Release: | 4.3.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1757916 (view as bug list) | Environment: | |||||
Last Closed: | 2019-10-17 15:40:43 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: | |||||||
Bug Blocks: | 1757916 | ||||||
Attachments: |
|
Description
Mike Fiedler
2019-10-02 15:37:22 UTC
Created attachment 1621917 [details]
kuryr pod logs + events
Could not run oc adm must-gather, so collected kuryr pod logs.
This is definitely a quota issue - I see networks and subnets quotas at capacity on the setup. The quotas we provide at https://github.com/openshift/installer/blob/master/docs/user/openstack/kuryr.md#requirements-when-enabling-kuryr are the "bare minimum" meaning that those are minimal numbers to run a successful installation. As you can see those aren't allowing many more namespaces to be created. Please bump the OpenStack subnet and network quotas to 150 (or more if the number of namespaces your tests create is higher) and see if it helps. This is definitely a quota issue - I see networks and subnets quotas at capacity on the setup. The quotas we provide at https://github.com/openshift/installer/blob/master/docs/user/openstack/kuryr.md#requirements-when-enabling-kuryr are the "bare minimum" meaning that those are minimal numbers to run a successful installation. As you can see those aren't allowing many more namespaces to be created. Please bump the OpenStack subnet and network quotas to 150 (or more if the number of namespaces your tests create is higher) and see if it helps. Okay, I also see that those networks and subnets hang even though namespaces/projects related to them got removed. This might still be a symptom of a problem then. Anyway to unblock running the tests just bump the quotas. Maybe some sort of resource leak? The tests do constantly create/delete projects and pods among other resources. Setting this to be the master (4.3) fix. I will clone to track for 4.2. But it's likely to only be able to make 4.2.1. *** This bug has been marked as a duplicate of bug 1759095 *** |