-
Bug
-
Resolution: Done
-
Major
-
1.5.0
-
Serverless Sprint 180
When I upgraded Serving to 0.12, the KnativeServing object and the "IMAGE_" variables surely upgrades to 0.12.1.
$ oc get ks -n knative-serving NAME VERSION READY REASON knative-serving 0.12.1 True $ oc rsh -n openshift-operators knative-serving-openshift-78b488d44b-znfvs env |grep -i image IMAGE_queue-proxy=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-queue IMAGE_activator=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-activator IMAGE_autoscaler=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-autoscaler IMAGE_autoscaler-hpa=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-autoscaler-hpa IMAGE_controller=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-controller IMAGE_webhook=registry.svc.ci.openshift.org/openshift/knative-v0.12.1:knative-serving-webhook
But the knative serving's deployment still uses v0.11.1 images.
$ oc get pod -n knative-serving -o yaml |grep image: |uniq
image: registry.svc.ci.openshift.org/openshift/knative-v0.11.1:knative-serving-activator
image: registry.svc.ci.openshift.org/openshift/knative-v0.11.1:knative-serving-autoscaler
image: registry.svc.ci.openshift.org/openshift/knative-v0.11.1:knative-serving-autoscaler-hpa
image: registry.svc.ci.openshift.org/openshift/knative-v0.11.1:knative-serving-controller
image: registry.svc.ci.openshift.org/openshift/knative-v0.11.1:knative-serving-webhook
By checking the build log history, it looks like all CI job on 0.12.1 has same issue. For example, I checked the logs on 12/Feb/2020/ (after bump to 0.12.1), it looks like the pod still uses v0.11.1 image. The log that I am checking is pod.json in here
Note, you can find the all log history from here
