Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-613

Ingress-gw pod on second control plane cannot talk to pilot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • maistra-0.12.0
    • maistra-0.12.0
    • None
    • None
    • Maistra TP sprint 12

      • Install operator
      • Install first control plane
        • oc new-project i1
        • oc -n i1 apply -f <cr-full.yaml>
        • Verify everything is fine
      • Install second control plane
        • oc new-project i2
        • oc -n i2 apply -f <cr-full.yaml>
        • Verify ingress-gateway is not able to talk to pilot
      $ oc -n i2 get pods -l istio=ingressgateway
      NAME                                    READY   STATUS    RESTARTS   AGE
      istio-ingressgateway-568dbc5cbc-gjxv2   0/1     Running   0          73m
      
      
      $ oc -n i2 logs istio-ingressgateway-568dbc5cbc-gjxv2
      .... lots of:
      [2019-07-11 15:05:34.156][13][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:86] gRPC config stream closed: 2, gateway has no associated service instances
      2019-07-11T15:05:34.265273Z     info    Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected
      
      

      And on the pilot side:

      oc -n i2 logs istio-pilot-9595b9988-vd8kn -c discovery
      ... lots of:
      2019-07-11T16:13:10.634662Z     warn    istio.io/istio/pilot/pkg/serviceregistry/kube/controller.go:352: watch of *v1.Service ended with: Underlying Result Channel closed
      2019-07-11T16:13:11.052291Z     info    ads     ADS: "10.131.0.20:40658"  terminated rpc error: code = Canceled desc = context canceled
      
      

              rcernich1 Rob Cernich
              jsantana@redhat.com Jonh Wendell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: