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

Verify CRW 1.2 to 2.0 upgrade using operator works for all updated containers #14865

Closed
nickboldt opened this issue Oct 11, 2019 · 2 comments
Closed

Verify CRW 1.2 to 2.0 upgrade using operator works for all updated containers #14865

nickboldt opened this issue Oct 11, 2019 · 2 comments
Assignees
@nickboldt @dmytro-ndp
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@nickboldt
Copy link
Contributor

Followup from #14200

Is your task related to a problem? Please describe.

Goal here is to verify that an old CRW 1.2 (based on Che 6.x) install using old containers can be updated to new 2.9 (based on 7.2 or 7.3) using newer containers, via an operator-based update as discussed in #14200 (comment) (and below).

  • PVC: registry.access.redhat.com/ubi8-minimal:8.0-159 -> registry.access.redhat.com/ubi8-minimal:8.0-213
  • Postgres: registry.redhat.io/rhscl/postgresql-96-rhel7:1-46 to registry.redhat.io/rhscl/postgresql-96-rhel7:1-47
  • Che Server registry.redhat.io/codeready-workspaces/server-rhel8:1.2 to quay.io/crw/server-rhel8:2.0
  • keycloak/sso registry.redhat.io/redhat-sso-7/sso73-openshift:1.0-13 to registry.redhat.io/redhat-sso-7/sso73-openshift:1.0-13.1567588155

Describe the solution you'd like

Automated test that will:

  • install old CRW 1.2 via operator, with custom image versions noted above
  • cause update to occur to update to newer 2.0 operator, with override images set (CRW 2.0 images don't yet exist in default locations, so need to use Quay locations instead for testing).
@nickboldt nickboldt added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 11, 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 Oct 11, 2019
@nickboldt nickboldt mentioned this issue Oct 11, 2019
Closed
@ibuziuk ibuziuk added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 14, 2019
@ibuziuk
Copy link
Member

ibuziuk commented Oct 14, 2019

@nickboldt who is expected to work on this issue ?

@ibuziuk ibuziuk added the severity/P1 Has a major impact to usage or development of the system. label Oct 14, 2019
@ibuziuk ibuziuk mentioned this issue Oct 15, 2019
Closed
@nickboldt
Copy link
Contributor Author

Given QE has signed off on https://issues.jboss.org/browse/CRW-304 and https://issues.jboss.org/browse/CRW-305 as being done, I guess this is done too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nickboldt nickboldt

@dmytro-ndp dmytro-ndp

Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator kind/task Internal things, technical debt, and to-do tasks to be performed. 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
4 participants
@nickboldt @dmytro-ndp @ibuziuk @che-bot