[BUG] Oh no! Something went wrong. Description: A.reduce is not a function

[molivo123]

General information

• OS: Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)? Yes
• Running CRC on: Laptop

CRC version

CRC version: 2.37.1+36d451
OpenShift version: 4.15.14

CRC status

CRC VM:          Running
OpenShift:       Running (v4.15.14)
RAM Usage:       7.133GB of 15.61GB
Disk Usage:      24.76GB of 53.08GB (Inside the CRC VM)
Cache Usage:     29.31GB
Cache Directory: C:\Users\molivo\.crc\cache

CRC config

- consent-telemetry                     : no
- cpus                                  : 8
- disk-size                             : 50
- memory                                : 15258

Host Operating System

Host Name:                 PRECISION-1016
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          admin
Registered Organization:
Product ID:                00355-61092-94842-AAOEM
Original Install Date:     6/5/2024, 11:42:29 AM
System Boot Time:          6/12/2024, 8:51:26 AM
System Manufacturer:       Dell Inc.
System Model:              Precision 7680
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 183 Stepping 1 GenuineIntel ~2100 Mhz
BIOS Version:              Dell Inc. 1.11.0, 3/6/2024
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-08:00) Pacific Time (US & Canada)
Total Physical Memory:     65,221 MB
Available Physical Memory: 34,967 MB
Virtual Memory: Max Size:  74,949 MB
Virtual Memory: Available: 43,513 MB
Virtual Memory: In Use:    31,436 MB
Page File Location(s):     C:\pagefile.sys
Logon Server:              \\DC2

Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Steps to reproduce

1. setup/start crc
2. Go to OperatorHub
3. See following Screen:

Expected

Ability to install Operators

Actual

error when trying to access OperatorHub

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.

[molivo123]

When running `crc start --log-level debug' I get the following which looks problematic:

DEBU SSH command results: err: <nil>, output: configmap/admin-kubeconfig-client-ca patched
DEBU Creating /opt/kubeconfig with permissions 0644 in the CRC VM
DEBU Running SSH command: <hidden>
DEBU SSH command succeeded
INFO Starting openshift instance... [waiting for the cluster to stabilize]
DEBU authentication operator not available, Reason: OAuthServerDeployment_NoPod::OAuthServerRouteEndpointAccessibleController_EndpointUnavailable
DEBU console operator is degraded, Reason: RouteHealth_StatusError
DEBU console operator is still progressing, Reason: SyncLoopRefresh_InProgress
DEBU console operator not available, Reason: Deployment_InsufficientReplicas::RouteHealth_StatusError
DEBU Unexpected operator status for console: EvaluationConditionsDetected
DEBU Unexpected operator status for etcd: EvaluationConditionsDetected
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-controller-manager: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-scheduler: EvaluationConditionsDetected
DEBU Unexpected operator status for machine-config: EvaluationConditionsDetected
DEBU openshift-controller-manager operator is still progressing, Reason: _DesiredStateNotYetAchieved
INFO 2 operators are progressing: console, openshift-controller-manager
DEBU Unexpected operator status for console: EvaluationConditionsDetected
DEBU Unexpected operator status for etcd: EvaluationConditionsDetected
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-controller-manager: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-scheduler: EvaluationConditionsDetected
DEBU Unexpected operator status for machine-config: EvaluationConditionsDetected
INFO All operators are available. Ensuring stability...
DEBU Unexpected operator status for console: EvaluationConditionsDetected
DEBU Unexpected operator status for etcd: EvaluationConditionsDetected
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-controller-manager: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-scheduler: EvaluationConditionsDetected
DEBU Unexpected operator status for machine-config: EvaluationConditionsDetected
INFO Operators are stable (2/3)...
DEBU Unexpected operator status for console: EvaluationConditionsDetected
DEBU Unexpected operator status for etcd: EvaluationConditionsDetected
DEBU Unexpected operator status for ingress: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-apiserver: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-controller-manager: EvaluationConditionsDetected
DEBU Unexpected operator status for kube-scheduler: EvaluationConditionsDetected
DEBU Unexpected operator status for machine-config: EvaluationConditionsDetected
INFO Operators are stable (3/3)...

[molivo123]

through many deletes and starts and stops, it is now just showing up blank:

[Dave-c-Ross]

Same issue here

[Dave-c-Ross]

Workaround for now: https://access.redhat.com/solutions/7075189

[molivo123]

@Dave-c-Ross Thanks for that, any insight into how to resolve "No OperatorHub items found" issue?

[anjannath]

closing as this cannot be solved on crc and is an issue with operator hub