Skip to content
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

CheHost set incorrectly with chectl server:deploy #19586

Closed
5 of 23 tasks
filipkroupa opened this issue Apr 14, 2021 · 2 comments
Closed
5 of 23 tasks

CheHost set incorrectly with chectl server:deploy #19586

filipkroupa opened this issue Apr 14, 2021 · 2 comments
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@filipkroupa
Copy link

Describe the bug

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Deploy Che with latest chectl (next channel):

$ chectl server:deploy --installer=operator --platform=k8s --domain=app.che4z.mfd.broadcom.net --multiuser --chenamespace=nightly
› Current Kubernetes context: 'gke_mfd-eng-che4z_us-central1-a_mfd-che4z-gke1'
  ✔ Verify Kubernetes API...OK
  ✔ 👀  Looking for an already existing Eclipse Che instance
    ✔ Verify if Eclipse Che is deployed into namespace "nightly"...it is not
  ✔ ✈️  Kubernetes preflight checklist
    ✔ Verify if kubectl is installed
    ✔ Verify remote kubernetes status...done.
    ✔ Check Kubernetes version: Found v1.17.17-gke.2800.
    ✔ Verify domain is set...set to app.che4z.mfd.broadcom.net.
    ↓ Check if cluster accessible [skipped]
  ✔ Following Eclipse Che logs
    ✔ Start following Operator logs...done
    ✔ Start following Eclipse Che server logs...done
    ✔ Start following Postgres logs...done
    ✔ Start following Keycloak logs...done
    ✔ Start following Plugin registry logs...done
    ✔ Start following Devfile registry logs...done
    ✔ Start following namespace events...done
  ✔ 🏃‍  Running the Eclipse Che operator
    ✔ Create Namespace (nightly)...It already exists.
    ✔ Create ServiceAccount che-operator in namespace nightly...done.
    ✔ Read Roles and Bindings...done.
    ✔ Creating Roles and Bindings...done.
    ✔ Create CRD checlusters.org.eclipse.che...It already exists.
    ✔ Waiting 5 seconds for the new Kubernetes resources to get flushed...done.
    ✔ Create deployment che-operator in namespace nightly...done.
    ✔ Operator pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Prepare Eclipse Che cluster CR...Done.
    ✔ Create the Custom Resource of type checlusters.org.eclipse.che in the namespace nightly...done.
  ✔ ✅  Post installation checklist
    ✔ PostgreSQL pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Keycloak pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Devfile registry pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Plugin registry pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Eclipse Che pod bootstrap
      ✔ Scheduling...done
      ✔ Downloading images...done
      ✔ Starting...done
    ✔ Eclipse Che status check...done
  ✔ Retrieving Keycloak admin credentials...done
  ✔ Retrieving Che self-signed CA certificate... commonly trusted certificate is used.
  ✔ Prepare post installation output...done
  ✔ Show important messages
    ✔ Eclipse Che 7.29.0-SNAPSHOT has been successfully deployed.
    ✔ Documentation             : https://www.eclipse.org/che/docs/
    ✔ -------------------------------------------------------------------------------
    ✔ Users Dashboard           : https://app.che4z.mfd.broadcom.net
    ✔ Admin user login          : "admin:admin". NOTE: must change after first login.
    ✔ -------------------------------------------------------------------------------
    ✔ Plug-in Registry          : https://plugin-registry-nightly.app.che4z.mfd.broadcom.net/v3
    ✔ Devfile Registry          : https://devfile-registry-nightly.app.che4z.mfd.broadcom.net/
    ✔ -------------------------------------------------------------------------------
    ✔ Identity Provider URL     : https://keycloak-nightly.app.che4z.mfd.broadcom.net/auth
    ✔ Identity Provider login   : "admin:lIe683Ga2B7D".
    ✔ -------------------------------------------------------------------------------
Command server:deploy has completed successfully in 03:51.

Expected behavior

You can see Che dashboard URL is set to https://app.che4z.mfd.broadcom.net, where with Kubernetes namespace 'nightly' is should have been https://che-nightly.app.che4z.mfd.broadcom.net

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

Installation method

  • chectl
    • provide a full command that was used to deploy Eclipse Che (including the output)
    • provide an output of chectl version command
  • OperatorHub
  • I don't know
$ chectl --version
chectl/0.0.20210413-next.950a1f6 linux-x64 node-v12.22.0

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • Dev Sandbox (workspaces.openshift.com)
  • other: please specify

Eclipse Che Logs

Additional context

Che host is incorrectly set also in CheCluster custom resource and in Che ingress rule

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  creationTimestamp: "2021-04-14T08:27:08Z"
  finalizers:
  - cheWorkspaces.clusterpermissions.finalizers.che.eclipse.org
  generation: 15
  name: eclipse-che
  namespace: nightly
  resourceVersion: "129582966"
  selfLink: /apis/org.eclipse.che/v1/namespaces/nightly/checlusters/eclipse-che
  uid: 821d4fcc-df7f-4749-a096-dd932777a2ac
spec:
  auth:
    externalIdentityProvider: false
    identityProviderClientId: che-public
    identityProviderContainerResources:
      limits: {}
      request: {}
    identityProviderIngress: {}
    identityProviderPostgresSecret: che-identity-postgres-secret
    identityProviderRealm: che
    identityProviderRoute: {}
    identityProviderSecret: che-identity-secret
    identityProviderURL: https://keycloak-nightly.app.che4z.mfd.broadcom.net/auth
    initialOpenShiftOAuthUser: true
    updateAdminPassword: true
  database:
    chePostgresContainerResources:
      limits: {}
      request: {}
    chePostgresDb: dbche
    chePostgresHostName: postgres
    chePostgresPort: "5432"
    chePostgresSecret: che-postgres-secret
    externalDb: false
  devWorkspace:
    enable: false
  imagePuller:
    enable: false
    spec: {}
  k8s:
    ingressDomain: app.che4z.mfd.broadcom.net
    tlsSecretName: che-tls
  metrics:
    enable: true
  server:
    allowUserDefinedWorkspaceNamespaces: false
    cheDebug: "false"
    cheFlavor: che
    cheHost: app.che4z.mfd.broadcom.net
    cheLogLevel: INFO
    cheServerIngress: {}
    cheServerRoute: {}
    devfileRegistryIngress: {}
    devfileRegistryRoute: {}
    externalDevfileRegistry: false
    externalPluginRegistry: false
    gitSelfSignedCert: false
    pluginRegistryIngress: {}
    pluginRegistryRoute: {}
    selfSignedCert: true
    serverExposureStrategy: multi-host
    tlsSupport: true
    useInternalClusterSVCNames: true
    workspaceNamespaceDefault: <username>-che
  storage:
    preCreateSubPaths: true
    pvcClaimSize: 10Gi
    pvcStrategy: common
status:
  cheClusterRunning: Available
  cheURL: https://app.che4z.mfd.broadcom.net
  cheVersion: nightly
  dbProvisioned: true
  devfileRegistryURL: https://devfile-registry-nightly.app.che4z.mfd.broadcom.net/
  gitHubOAuthProvisioned: false
  keycloakProvisioned: true
  keycloakURL: https://keycloak-nightly.app.che4z.mfd.broadcom.net/auth
  openShiftOAuthUserCredentialsSecret: ""
  openShiftoAuthProvisioned: false
  pluginRegistryURL: https://plugin-registry-nightly.app.che4z.mfd.broadcom.net/v3
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
  creationTimestamp: "2021-04-14T07:45:25Z"
  generation: 1
  labels:
    app.kubernetes.io/component: che
    app.kubernetes.io/instance: che
    app.kubernetes.io/managed-by: che-operator
    app.kubernetes.io/name: che
  name: che
  namespace: nightly
  ownerReferences:
  - apiVersion: org.eclipse.che/v1
    blockOwnerDeletion: true
    controller: true
    kind: CheCluster
    name: eclipse-che
    uid: 9ce8b077-bb5f-41f0-a39f-f1ab41de61ac
  resourceVersion: "129564964"
  selfLink: /apis/extensions/v1beta1/namespaces/nightly/ingresses/che
  uid: 02a24bbb-e76a-401a-a812-51e56d7b3272
spec:
  rules:
  - host: app.che4z.mfd.broadcom.net
    http:
      paths:
      - backend:
          serviceName: che-host
          servicePort: 8080
        path: /
  tls:
  - hosts:
    - app.che4z.mfd.broadcom.net
    secretName: che-tls
status:
  loadBalancer:
    ingress:
    - ip: 10.212.56.13
@filipkroupa filipkroupa added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 14, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 14, 2021
@tolusha
Copy link
Contributor

tolusha commented Apr 14, 2021

@filipkroupa
Thank you for reporting.
It just has been fixed. Could you retry pls?

@filipkroupa
Copy link
Author

@tolusha I retried and now it behaves as expected. Thank you for prompt fix.

@tolusha tolusha added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Apr 14, 2021
@tolusha tolusha closed this as completed Apr 14, 2021
@tolusha tolusha added this to the 7.29 milestone Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants