At some applications istio sometimes takes a long time to start routing. After all related resources are deployed to openshift, Istio takes up to several tens of minutes to start routing to the right pod. Until that, it keeps returning codes 503 or 404.

Environment:
Local installation using - https://github.com/Maistra/origin/releases. Installed by command

oc cluster up add=*,istio --public-hostname=<local IP>

Steps to reproduce:
log in to openshift with cluster-admin rights
checkout GIT repository: https://github.com/snowdrop/spring-boot-istio-distributed-tracing-booster

• oc new-project test-app
• mvn clean verify -Popenshift,openshift-it // run integration tests on app -> first run is usually OK
• // recreating namespace is just temporary workaround around some bug in resource cleaning
• oc delete projest test-app
• <wait for deletion to complete>
• oc new-project test-app
• mvn clean verify -Popenshift,openshift-it // second run usually fails
  Second build usually fails on timeout - that istio is still not routing. Error message should look like something in the attachment