-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Che operator timing out when creating CheCluster in OpenShift #20487
Comments
Possible duplicates #19243 /cc @sleshchenko |
@tolusha Thanks for the quick reply! I was following the instructions in the documentation, which mention using the default settings, so I didn't enable the DevWorkspace stuff. I'm pretty new to Che, so I apologize if this was documented somewhere else. I did try again using the DevWorkspace operator and image puller, but things still never install. Here are my CheCluster settings: apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
name: eclipse-che
namespace: eclipse-che
spec:
auth:
identityProviderURL: ''
identityProviderRealm: ''
oAuthSecret: ''
identityProviderPassword: ''
oAuthClientName: ''
initialOpenShiftOAuthUser: true
identityProviderClientId: ''
identityProviderAdminUserName: ''
externalIdentityProvider: false
openShiftoAuth: true
database:
chePostgresDb: ''
chePostgresHostName: ''
chePostgresPassword: ''
chePostgresPort: ''
chePostgresUser: ''
externalDb: false
devWorkspace:
enable: true
imagePuller:
enable: true
metrics:
enable: true
server:
proxyURL: ''
cheClusterRoles: ''
proxyPassword: ''
nonProxyHosts: ''
proxyPort: ''
tlsSupport: true
allowUserDefinedWorkspaceNamespaces: false
serverTrustStoreConfigMapName: ''
proxyUser: ''
cheWorkspaceClusterRole: ''
workspaceNamespaceDefault: <username>-che
serverExposureStrategy: ''
gitSelfSignedCert: false
cheFlavor: ''
storage:
postgresPVCStorageClassName: ''
preCreateSubPaths: true
pvcClaimSize: 10Gi
pvcStrategy: common
workspacePVCStorageClassName: '' After enabling the devworkspace thing, the che-operator instead seems to go into CrashLoopBackOff:
The logs for that pod don't show much:
|
I installed from the stable channel I believe, here's my Subscription apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: eclipse-che
namespace: eclipse-che
labels:
operators.coreos.com/eclipse-che.eclipse-che: ''
spec:
channel: stable
installPlanApproval: Automatic
name: eclipse-che
source: community-operators
sourceNamespace: openshift-marketplace
startingCSV: eclipse-che.v7.36.1
status:
installplan:
apiVersion: operators.coreos.com/v1alpha1
kind: InstallPlan
name: install-9j75x
uuid: 458b5123-90ff-4a87-8709-be12cea4d3dd
lastUpdated: '2021-09-20T12:04:19Z'
installedCSV: eclipse-che.v7.36.1
currentCSV: eclipse-che.v7.36.1
installPlanRef:
apiVersion: operators.coreos.com/v1alpha1
kind: InstallPlan
name: install-9j75x
namespace: eclipse-che
resourceVersion: '56385216'
uid: 458b5123-90ff-4a87-8709-be12cea4d3dd
state: AtLatestKnown
catalogHealth:
- catalogSourceRef:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
name: community-operators
namespace: openshift-marketplace
resourceVersion: '56378334'
uid: 52a13556-2e10-41fe-8aac-cba654585fbf
healthy: true
lastUpdated: '2021-09-20T12:04:05Z'
conditions:
- lastTransitionTime: '2021-09-20T12:04:05Z'
message: all available catalogsources are healthy
reason: AllCatalogSourcesHealthy
status: 'False'
type: CatalogSourcesUnhealthy
installPlanGeneration: 2 |
I wasn't able to reproduce the issue.
|
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Describe the bug
After creating a CheCluster, the controller seems to hang indefinitely. The che-operator container reports the following in its logs:
Che version
7.36@latest
Steps to reproduce
Expected behavior
Following the installation instructions, it seems creating a Che operator with default settings should be OK.
Runtime
OpenShift
Screenshots
No response
Installation method
OperatorHub
Environment
Linux
Eclipse Che Logs
chectl-logs.tar.gz
Additional context
No response
The text was updated successfully, but these errors were encountered: