Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-133

Serving Operator 0.6.0 forces installation of Maistra 0.10 when Maistra 0.11 is already installed (and fails)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • v0.6.0
    • v0.6.0
    • Operator
    • None
    • Serverless Sprint 168

      How to reproduce:
      Spin up OCP 4.1.0
      Install Maistra 0.11 from https://github.com/Maistra/istio-operator/tree/maistra-0.11
      Install knative-serving Operator from web console

      See the logs of knative-serving-operator pod:

      :
      :
      {"level":"info","ts":1559827002.3735862,"logger":"openshift","msg":"Setting","map":"config-network","istio.sidecar.includeOutboundIPRanges":"172.30.0.0/16"}
      {"level":"info","ts":1559827002.3788729,"logger":"openshift","msg":"Ensuring Istio is installed in OpenShift"}
      {"level":"info","ts":1559827002.3815267,"logger":"openshift","msg":"Maistra Operator already installed"}
      {"level":"info","ts":1559827002.3838506,"logger":"openshift","msg":"Installing Maistra ControlPlane"}
      {"level":"info","ts":1559827002.3838696,"logger":"manifestival","msg":"Reading file","name":"deploy/resources/maistra/maistra-controlplane-0.10.0.yaml"}
      {"level":"info","ts":1559827002.3929372,"logger":"manifestival","msg":"Creating","name":"istio-system/minimal-istio","type":"istio.openshift.com/v1alpha3, Kind=ControlPlane"}
      {"level":"info","ts":1559827002.5135388,"logger":"manifestival","msg":"Updating","name":"/knative-serving","type":"/v1, Kind=Namespace"}
      :
      :
      

      Even though there is Maistra 0.11 installed, it won't use it and tries installing Maistra ControlPlane 0.10 in the istio-system ns.

      Two pods will fail to start in istio-system:

      istio-ingressgateway-d7b59588c-2n2jd     0/1     ImagePullBackOff   0          5m14s
      istio-pilot-bffd855c8-qlbtw              0/1     ImagePullBackOff   0          5m17s
      

      Logs from istio-ingressgateway pod:

      Events:
        Type     Reason     Age                    From                                                Message
        ----     ------     ----                   ----                                                -------
        Normal   Scheduled  6m42s                  default-scheduler                                   Successfully assigned istio-system/istio-ingressgateway-d7b59588c-2n2jd to ip-10-0-158-79.us-west-2.compute.internal
        Normal   Pulling    5m4s (x4 over 6m35s)   kubelet, ip-10-0-158-79.us-west-2.compute.internal  Pulling image "maistra/proxyv2-ubi8:0.10.0"
        Warning  Failed     5m2s (x4 over 6m33s)   kubelet, ip-10-0-158-79.us-west-2.compute.internal  Failed to pull image "maistra/proxyv2-ubi8:0.10.0": rpc error: code = Unknown desc = Error reading manifest 0.10.0 in docker.io/maistra/proxyv2-ubi8: manifest unknown: manifest unknown
        Warning  Failed     5m2s (x4 over 6m33s)   kubelet, ip-10-0-158-79.us-west-2.compute.internal  Error: ErrImagePull
        Normal   BackOff    4m36s (x7 over 6m33s)  kubelet, ip-10-0-158-79.us-west-2.compute.internal  Back-off pulling image "maistra/proxyv2-ubi8:0.10.0"
        Warning  Failed     85s (x21 over 6m33s)   kubelet, ip-10-0-158-79.us-west-2.compute.internal  Error: ImagePullBackOff
      

      It seems that it took the original image "maistra/proxyv2-ubi8:0.11.0" and changed the version to 0.10, resulting in image "maistra/proxyv2-ubi8:0.10.0", which is not found.

              mgencur Martin Gencur
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: