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

Can not access to application by route because of service unavailable #14121

Closed
2 of 16 tasks
Ohrimenko1988 opened this issue Aug 5, 2019 · 1 comment
Closed
2 of 16 tasks

Can not access to application by route because of service unavailable #14121

Ohrimenko1988 opened this issue Aug 5, 2019 · 1 comment
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.1.0

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Aug 5, 2019 •
edited
Loading

Describe the bug

Time to time the automated tests fail on CI job because application which deployed in the container cant be opened by the route.

Reproduced on:
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Che7-pr-happy-path-test-OKD/642

Che version

7.0.0-rc-5.0-SNAPSHOT

Steps to reproduce

Expected behavior

After clicking "Yes" button, a new notification with the suggestion of open link will be displayed

Observed behavior

Nothing happens

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

screenshot-Launch_debug

Screenshot from 2019-08-05 12-23-58

Screenshot from 2019-08-05 12-24-23

Logs

app-statistic.zip

browserlogs-Launch_debug.txt

Installation method

  • ocp.sh

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

Additional context
@Ohrimenko1988 Ohrimenko1988 added 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. e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. labels Aug 5, 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 Aug 5, 2019
@benoitf benoitf added this to the 7.1.0 milestone Aug 5, 2019
@benoitf benoitf removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 5, 2019
This was referenced Aug 5, 2019
Closed
Closed
Ohrimenko1988 added a commit that referenced this issue Aug 5, 2019
@Ohrimenko1988
Do changes for workaround the '#14121' issue
9ec5c6f
@Ohrimenko1988 Ohrimenko1988 mentioned this issue Aug 5, 2019
Merged
Ohrimenko1988 added a commit that referenced this issue Aug 5, 2019
@Ohrimenko1988
[TS_SELENIUM] Implement workaround for bug described in the issue #14121
30fec31 
 (Can not access to application by route because of service unavailable)
@vkuznyetsov vkuznyetsov mentioned this issue Aug 9, 2019
Closed
17 tasks
@che-bot
Copy link
Contributor

che-bot commented Feb 5, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2020
@che-bot che-bot closed this as completed Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.1.0
Development

No branches or pull requests
3 participants
@benoitf @Ohrimenko1988 @che-bot