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

Single-host testing on OpenShift #17789

Closed
skabashnyuk opened this issue Sep 4, 2020 · 6 comments
Closed

Single-host testing on OpenShift #17789

skabashnyuk opened this issue Sep 4, 2020 · 6 comments
Assignees
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Sep 4, 2020

Is your task related to a problem? Please describe.

We should figure out where we are with single-host implementation #12914 on OpenShift.

Describe the solution you'd like

Run as much as possible automated tests.

Describe alternatives you've considered

  • add some manual testing

Additional context

Known issues

@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Sep 4, 2020
@skabashnyuk skabashnyuk changed the title Single host testing on OpenShift Single-host testing on OpenShift Sep 4, 2020
@skabashnyuk
Copy link
Contributor Author

How to setup environment #16842 (comment)

@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 4, 2020
@skabashnyuk skabashnyuk added area/qe area/che-server and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. area/che-server labels Sep 4, 2020
@artaleks9 artaleks9 added team/che-qe status/in-progress This issue has been taken by an engineer and is under active development. labels Sep 7, 2020
@artaleks9
Copy link
Contributor

artaleks9 commented Sep 7, 2020

  • On this moment was checked installation CHE 'single-host' on OCP 4.5 by using specific 'che-operator' and 'patch-cr.yaml' provided 'platform-team'.
    CHE 'single-host' was installed and worksapce launched. 'Smoke' tests have found a problem with run demo application which is described in Running demo application of 'java-web-spring' doesn't work in CHE 'single-host' on k8s  #17783
  • I'm planning to update script and run E2E tests in specific job for CHE 'single-host' on OCP 4.5 /4.4

@rhopp rhopp added this to the 7.19 milestone Sep 9, 2020
@artaleks9
Copy link
Contributor

  • There were created two jobs which can launch E2E tests on CHE with 'single-host' strategy:
    -che-single-host-chectl-tls-oauth
    -che-single-host-chectl-tls-no-oauth
  • Results of E2E and manual tests don't show blockers issue on this moment.
  • There was done several runs on OCP 4.5/4.4/3:
    -Devfile E2E tests (in some runs some of test were fail by flakiness reasons, the similar results are on 'default-nightly' Che)
    -Git SSH flow E2E test (is success)
    -Dashbord Java E2E (some of them were fail, and require rework / update)
    -Happy path E2E test is not still implemented to run on OCP (working in progress)

@artaleks9
Copy link
Contributor

@rhopp rhopp modified the milestones: 7.19, 7.20 Sep 14, 2020
@artaleks9
Copy link
Contributor

  • I think, the goal of this issue was reached.
  • The issue can be closed.

@rhopp
Copy link
Contributor

rhopp commented Oct 5, 2020

Automation is being done in #17789

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

4 participants