Closed molivo123 closed 2 months ago
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)...
through many deletes and starts and stops, it is now just showing up blank:
Same issue here
Workaround for now: https://access.redhat.com/solutions/7075189
@Dave-c-Ross Thanks for that, any insight into how to resolve "No OperatorHub items found" issue?
closing as this cannot be solved on crc and is an issue with operator hub
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
Ability to install Operators
Actual
error when trying to access OperatorHub
Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.