[BUG] OCP 4.11 installation times out

[concaf]

CRC times out while starting a 4.11 cluster. I guess that it's particularly the auth operator that's slower to come up and times out.

Even though it times out, the installation completes eventually - which is nice, just not ideal :)

General information

• OS: Linux
• Hypervisor: KVM
• Did you run crc setup before starting it? Yes
• Running CRC on: Laptop

CRC version

$ crc version
CRC version: 2.7.1+a8e9854
OpenShift version: 4.11.0
Podman version: 4.1.1

CRC status

$ crc status --log-level debug
DEBU CRC version: 2.7.1+a8e9854                   
DEBU OpenShift version: 4.11.0                    
DEBU Podman version: 4.1.1                        
DEBU Running 'crc status'                         
DEBU Checking file: /home/concaf/.crc/machines/crc/.crc-exist 
DEBU Checking file: /home/concaf/.crc/machines/crc/.crc-exist 
DEBU Found binary path at /home/concaf/.crc/bin/crc-driver-libvirt 
DEBU Launching plugin server for driver libvirt   
DEBU Plugin server listening at address 127.0.0.1:46257 
DEBU () Calling .GetVersion                       
DEBU Using API Version 1                          
DEBU () Calling .SetConfigRaw                     
DEBU () Calling .GetMachineName                   
DEBU (crc) Calling .GetBundleName                 
DEBU (crc) Calling .GetState                      
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="Getting current state..." 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="Fetching VM..." 
DEBU (crc) Calling .GetIP                         
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="GetIP called for crc" 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="Getting current state..." 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="IP address: 192.168.130.11" 
DEBU (crc) Calling .GetIP                         
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="GetIP called for crc" 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="Getting current state..." 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="IP address: 192.168.130.11" 
DEBU Running SSH command: df -B1 --output=size,used,target /sysroot | tail -1 
DEBU Using ssh private keys: [/home/concaf/.crc/machines/crc/id_ecdsa /home/concaf/.crc/cache/crc_libvirt_4.11.0_amd64/id_ecdsa_crc] 
DEBU SSH command results: err: <nil>, output: 32737570816 14558605312 /sysroot 
DEBU Making call to close driver server           
DEBU (crc) Calling .Close                         
DEBU Successfully made call to close driver server 
DEBU Making call to close connection to plugin binary 
DEBU (crc) DBG | time="2022-08-19T13:18:11+05:30" level=debug msg="Closing plugin on server side" 
CRC VM:          Running
OpenShift:       Running (v4.11.0)
Podman:          
Disk Usage:      14.56GB of 32.74GB (Inside the CRC VM)
Cache Usage:     17.09GB
Cache Directory: /home/concaf/.crc/cache

CRC config

$ crc config view
- consent-telemetry                     : no

Host Operating System

NAME="Fedora Linux"
VERSION="36 (Workstation Edition)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:36"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f36/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=36
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=36
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

1. crc start :)

Expected

CRC does not time out and OCP comes up before the timeout.

Actual

I use the command crc start -m 30000 -c 8:

INFO All operators are available. Ensuring stability...                        
INFO Operator authentication is progressing                                                                                                                   
INFO Operator authentication is progressing                       
INFO Operator authentication is progressing                                    
INFO Operator authentication is progressing         
INFO Operator authentication is progressing                                    
INFO Operator authentication is progressing                                                                                                                   
ERRO Cluster is not ready: cluster operators are still not stable after 10m0.314541215s                                                                       
INFO Adding crc-admin and crc-developer contexts to kubeconfig...                                                                                             
Started the OpenShift cluster.                                                                                                                                
                                                                                                                                                              
The server is accessible via web console at:                                                                                                                  
  https://console-openshift-console.apps-crc.testing                           

Logs

https://paste.centos.org/view/090f8ae5

[concaf]

oc get co authentication -o json --> https://paste.centos.org/view/c856d8d3 oc get co -o json --> https://paste.centos.org/view/ef1e8c79

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[praveenkumar]

/close

[openshift-ci[bot]]

@praveenkumar: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.