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

CheCluster devfileRegistryURL no longer applied #19627

Closed
5 of 23 tasks
sunix opened this issue Apr 20, 2021 · 2 comments
Closed
5 of 23 tasks

CheCluster devfileRegistryURL no longer applied #19627

sunix opened this issue Apr 20, 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.
Milestone

Comments

@sunix
Copy link
Contributor

sunix commented Apr 20, 2021

Describe the bug

I tested recently devfileRegistryURL to add my custom external devfile registry. It was working fine but after few modification of the CheCluster CR, it is no longer applied.

Che version

  • latest 7.29.0
  • nightly
  • other: please specify

Steps to reproduce

Not sure it is reproducible in other instance, I can help providing logs, etc.

In my case:

  1. edit the CheCluster CR kubectl edit CheCluster/eclipse-che -n che
  2. in the server section:
      server:
        devfileRegistryURL: https://sunix-sunix-che-devfile-registry.surge.sh
        externalDevfileRegistry: true
  3. save and quit
  4. look at the new resource status section.
    status:
      cheClusterRunning: Available
      cheURL: https://che-che.chegcp.mychecluster.org
      cheVersion: 7.29.0
      dbProvisioned: true
      devfileRegistryURL: ""

devfileRegistryURL is empty

Expected behavior

Should be

    status:
      cheClusterRunning: Available
      cheURL: https://che-che.chegcp.mychecluster.org
      cheVersion: 7.29.0
      dbProvisioned: true
      devfileRegistryURL: "https://sunix-sunix-che-devfile-registry.surge.sh"

Runtime

  • kubernetes (include output of kubectl version) GKE
  • 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

Selection_335

Installation method

  • chectl 7.29.0
    • 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

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

@sunix sunix added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 20, 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 20, 2021
@tolusha
Copy link
Contributor

tolusha commented Apr 20, 2021

Could you provide operator logs ?

@tolusha
Copy link
Contributor

tolusha commented Apr 20, 2021

It should be devfileRegistryUrl not devfileRegistryURL

@tolusha tolusha added the area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator label Apr 20, 2021
@tolusha tolusha closed this as completed Apr 20, 2021
@tolusha tolusha added this to the 7.30 milestone Apr 20, 2021
@sleshchenko sleshchenko removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 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.
Projects
None yet
Development

No branches or pull requests

4 participants