Bug 1978213

Summary: OpenStack quota checks inexact when using Kuryr
Product: OpenShift Container Platform Reporter: Martin André <m.andre>
Component: InstallerAssignee: Martin André <m.andre>
Installer sub component: OpenShift on OpenStack QA Contact: Itay Matza <imatza>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: low CC: emacchi, imatza, itbrown, pprinett, ushkalim
Version: 4.8Keywords: Triaged
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Typo in a conditional. Consequence: quotas for kuryr deployments are checked against non-kuryr deployment requirements. Fix: Fix the conditional. Result: quota checks are more accurate for Kuryr deployments.
Story Points: ---
Clone Of:
: 1989279 (view as bug list) Environment:
Last Closed: 2021-10-18 17:37:23 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: 1989917    
Bug Blocks: 1988464, 1989279    

Description Martin André 2021-07-01 10:39:14 UTC
Due to a typo (kuryr vs Kuryr) we're not properly validating the needed network quota for Kuryr deployments. The quota check validate against the OpenShiftSDN network constraints instead of the Kuryr network constraints and as a consequence the installation may start even though the user has not nearly enough quota for a successful Kuryr deployment.

Comment 15 Itay Matza 2021-08-18 11:16:56 UTC
Verified successfully on openshift-install version:
openshift-install 4.9.0-0.nightly-2021-08-18-033031
built from commit cd2c598ae11c088eb65d8f84bc673e4c8b12f09c
release image registry.ci.openshift.org/ocp/release@sha256:29fe71a2d014c3fc34dfa040766d8c335eb4b3f385ac3f5667c3ff7a0e9a9d4e


>(shiftstack) [stack@undercloud-0 ~]$ grep type install-config.yaml
>  type: "Kuryr"
>(overcloud) [stack@undercloud-0 ~]$ openstack quota show shiftstack | grep "port\|secgroup"
>| ports                 | 1500                                                                                                                                                                                    
>| secgroup-rules        | 1000                                                                                                                                                                                    
>| secgroups             | 250                                                                                                                                                                                     
>(overcloud) [stack@undercloud-0 ~]$ openshift-install create cluster --dir ostest/                                                                                                                                
>INFO Credentials loaded from file "/home/stack/clouds.yaml"
>INFO Consuming Install Config from target directory
>INFO Obtaining RHCOS image file from 'https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.9/49.84.202107010027-0/x86_64/rhcos-49.84.202107010027-0-openstack.x86_64.qcow2.gz?sha256=00cb56c8711686255744646394e22a8ca5f27e059016f6758f14388e5a0a14cb'
>INFO The file was found in cache: /home/stack/.cache/openshift-installer/image_cache/rhcos-49.84.202107010027-0-openstack.x86_64.qcow2. Reusing...                                                                
>WARNING Following quotas SecurityGroup, RAM, Port, Subnet, Network, SecurityGroupRule are available but will be completely used pretty soon.                                                                      
>INFO Creating infrastructure resources...

Comment 18 errata-xmlrpc 2021-10-18 17:37:23 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759