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

[happy-path] Invalid url after running Pet clinic application during Happy Path scenario #13973

Closed
1 task done
musienko-maxim opened this issue Jul 23, 2019 · 2 comments
Closed
1 task done

[happy-path] Invalid url after running Pet clinic application during Happy Path scenario #13973

musienko-maxim opened this issue Jul 23, 2019 · 2 comments
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Milestone
7.x (Later, Futur...

Comments

@musienko-maxim
Copy link
Contributor

musienko-maxim commented Jul 23, 2019 •
edited
Loading

Describe the bug

Sometimes after launching Happy Path scenario on Kubernetes (minikube) and Openshift(OKD) infrastructures we got invalid url to the application URL. See screenshot

Che version

  • latest

Steps to reproduce

It is reproduced periodically during daily launching HAppy Path scenario on the job with OKD infrastructure:

Screenshots

screenshot-Check_the_running_application
@musienko-maxim musienko-maxim added the e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. label Jul 23, 2019
@musienko-maxim musienko-maxim changed the title [] Invalid url after running Pet clinic application during Happy Path scenario Invalid url after running Pet clinic application during Happy Path scenario Jul 23, 2019
@rhopp rhopp changed the title Invalid url after running Pet clinic application during Happy Path scenario [happy-path] Invalid url after running Pet clinic application during Happy Path scenario Jul 23, 2019
@rhopp
Copy link
Contributor

rhopp commented Jul 24, 2019

I would say we need more data:

  • all routes
  • Processes from the container
  • curl to the application from within the container (localhost:8080)

@nickboldt nickboldt added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Jul 24, 2019
@nickboldt nickboldt mentioned this issue Jul 24, 2019
Closed
1 task
@slemeur slemeur added this to the 7.x milestone Jul 24, 2019
@musienko-maxim
Copy link
Contributor Author

after implementation latest changes in the test this problem is not repeoduced

@vkuznyetsov vkuznyetsov mentioned this issue Aug 9, 2019
Closed
17 tasks
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. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Milestone
7.x (Later, Future, Never)
Development

No branches or pull requests
4 participants
@nickboldt @rhopp @slemeur @musienko-maxim