minishift: Nodejs-ex gets stuck on rollout during integration test

General information

As part of #1838 I tried to add a check to the http endpoint of nodejs-ex, but it gets stuck on rollout step. We need to do more investigation of where this issue is coming from. For now the http check was removed.

Steps to reproduce

  1. Add rollout step to the nodejs-ex scenario in cmd-openshift.feature
  2. Add http check steps to the nodejs-ex scenario in cmd-openshift.feature

Expected

The application rollouts successfully and its http endpoint is accessible.

Actual

The tests get stuck on the rollout step and whole test run is then killed by a 3600s timeout.

Logs

12:13:11   Scenario: User creates route to the service                                                                                                                                                             # features/cmd-openshift.feature:81
12:13:11     Given executing "oc set probe dc/nodejs-ex --readiness --get-url=http://:8080" succeeds                                                                                                               # integration_test.go:706 -> executingOcCommandSucceedsOrFails
13:30:32 Killed by signal 15.
13:30:32 + rtn_code=124
13:30:32 + '[' 124 -eq 0 ']'

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 16 (8 by maintainers)

Commits related to this issue

Most upvoted comments

I think we can now add the test with the delay and remove it once we switch to 3.9.0. WDYT?

Sounds good to me.