Internal requests 404s with istio 1.1.7

Hi!

I am connecting two internal services with istio enabled and the http requests are failing to 404
From service A ( 1 pod ) to service B ( 1 pod )

This is an extract of the log of the istio-proxy from service A

{"start_time":"2019-06-07T08:32:35.662Z","method":"GET","request_id":"e5b40ac2-f40b-4c99-9ca0-f46d1605138b","upstream_host":"-","x_forwarded_for":"-","requested_server_name":"-","bytes_received":"0","istio_policy_status":"-","bytes_sent":"0","upstream_cluster":"-","downstream_remote_address":"10.48.26.54:54586","path":"xxxxxxx","authority":"xxxxxx","protocol":"HTTP/1.1","upstream_service_time":"-","upstream_local_address":"-","duration":"0","downstream_local_address":"10.229.11.44:80","response_code":"404","user_agent":"xxxxxxx","response_flags":"NR"}

Another extract of istio-proxy log in debug mode

[2019-06-06 17:05:53.588][26][debug][http] 
[external/envoy/source/common/http/conn_manager_impl.cc:243] [C217] new stream
[2019-06-06 17:05:53.588][26][debug][http] 
[external/envoy/source/common/http/conn_manager_impl.cc:580] [C217][S126554576783690079] 
request headers complete (end_stream=true):
':authority', 'xxxx'
':path', 'xxxxxx'
':method', 'GET'
'accept', 'application/json, text/plain, */*'
'authorization', 'Bearer yyyyyyy'
'connection', 'keep-alive'

[2019-06-06 17:05:53.588][26][debug][http]         
[external/envoy/source/common/http/conn_manager_impl.cc:1040] [C217][S126554576783690079] 
request end stream
[2019-06-06 17:05:53.588][26][debug][filter] [src/envoy/http/mixer/filter.cc:39] Called Mixer::Filter : Filter
[2019-06-06 17:05:53.588][26][debug][filter] [src/envoy/http/mixer/filter.cc:146] Called Mixer::Filter : setDecoderFilterCallbacks
[2019-06-06 17:05:53.588][26][debug][filter] [src/envoy/http/mixer/filter.cc:62] Called Mixer::Filter : decodeHeaders
[2019-06-06 17:05:53.588][26][debug][filter] [./src/envoy/utils/header_update.h:46] Mixer forward     attributes set:     
[2019-06-06 17:05:53.588][26][debug][filter] [src/envoy/http/mixer/filter.cc:154] Called Mixer::Filter : check complete OK
[2019-06-06 17:05:53.589][26][debug][router] [external/envoy/source/common/router/router.cc:277]         
[C217][S126554576783690079] no cluster match for URL 'xxxxxxxx'
[2019-06-06 17:05:53.589][26][debug][filter] [src/envoy/http/mixer/filter.cc:133] Called Mixer::Filter : 
encodeHeaders 2
[2019-06-06 17:05:53.589][26][debug][http]         
[external/envoy/source/common/http/conn_manager_impl.cc:1305] [C217][S126554576783690079] 
encoding headers via codec (end_stream=true):
':status', '404'
'date', 'Thu, 06 Jun 2019 17:05:53 GMT'
'server', 'envoy'

It seems the request never arrive to the destination pod.

All the requirements are being honored. From port service names and label versions.
( https://istio.io/docs/setup/kubernetes/prepare/requirements )

Inspecting the two pods involved with istioctl I can see everything right, apparently

I don’t know if istio-pilot has some wrong configurations…is it possible to purge or delete the
routes ?

Also I can see now this… ( 50% synced…)

$ istioctl proxy-status
xxxxxxx                       SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-59478d45c6-nsfpr     1.1.3