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.

Sign up for GitHub

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

Jump to bottom

Keycloak doesn't upgrade from che-keycloak:6.19.0 to che-keycloak:7.1.0 on operator upgrade. #14575

Closed
5 of 17 tasks
metlos opened this issue Sep 17, 2019 · 4 comments
Closed
5 of 17 tasks

Keycloak doesn't upgrade from che-keycloak:6.19.0 to che-keycloak:7.1.0 on operator upgrade. #14575

metlos opened this issue Sep 17, 2019 · 4 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.

Comments

@metlos
Copy link
Contributor

metlos commented Sep 17, 2019

Describe the bug

When trying to upgrade a Che cluster created using the che operator (equivalent to crw 1.x), the operator doesn't upgrade the keycloak deployment even though the new version of the operator should use a new image version.

Che version

  • latest
  • nightly
  • che operarator from the 1.2.2.GA tag

Steps to reproduce

  1. Install che operator 1.2.2.GA
  2. install che cluster
  3. do rolling update of the operator to version 7.1.0

Expected behavior

The keycloak deployment should use the che-keycloak:7.1.0 image.

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)

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify
@metlos metlos added kind/bug Outline of a bug - must adhere to the bug report template. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Sep 17, 2019
@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 Sep 17, 2019
@metlos metlos mentioned this issue Sep 17, 2019
Closed
@l0rd l0rd added team/osio 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 Sep 17, 2019
@l0rd
Copy link
Contributor

l0rd commented Sep 17, 2019

@davidfestal are you already aware of this problem?

@davidfestal
Copy link
Contributor

Well, it's the same as #13714 but applied the scenario of an upgrade from Che 6 (CRW1.2) to Che 7.1.0, instead of the upgrade of 7.0.0 to 7.1.0, which was fixed.

More details in the initial issue: #14200 (comment)

@l0rd
Copy link
Contributor

l0rd commented Oct 22, 2019

@metlos we can close this one since we have decided to solve it as a doc issue (and doc pr has been merged)?

@ibuziuk
Copy link
Member

ibuziuk commented Oct 30, 2019

doc pr merged. Closing @metlos feel free to reopen

@ibuziuk ibuziuk closed this as completed Oct 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
5 participants
@metlos @l0rd @davidfestal @ibuziuk @che-bot