-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
1.18.0
-
None
-
False
-
False
-
This issue is urgent because I could not find a workaround if the end-user is using serverless.
Worked with a previous version: Operator 1.17.0
I am having a warning message on serverless/knative ocp4.9 when I am trying to deploy a `helloWorld` service
Knative client: `v0.24.0`
cmd:
./kn -n pablo-test service create hello-world-two --image gcr.io/knative-samples/helloworld-go --env TARGET=Knative
Events warning message:
route-controller: Failed to update finalizers for "hello-world-two": Operation cannot be fulfilled on routes.serving.knative.dev "hello-world-two": the object has been modified; please apply your changes to the latest version and try again ingress-controller: Failed to update finalizers for "hello-world-two": Operation cannot be fulfilled on ingresses.networking.internal.knative.dev "hello-world-two": the object has been modified; please apply your changes to the latest version and try again revision-controller: failed to update deployment "hello-world-two-00001-deployment": Operation cannot be fulfilled on deployments.apps "hello-world-two-00001-deployment": the object has been modified; please apply your changes to the latest version and try again podautoscaler-controller: error reconciling SKS: error updating SKS hello-world-two-00001: Operation cannot be fulfilled on serverlessservices.networking.internal.knative.dev "hello-world-two-00001": the object has been modified; please apply your changes to the latest version and try again Readiness probe failed: HTTP probe failed with statuscode: 410
In my opinion, these warning messages are preventing promote the service from "Pending" to "Ready.", so the service is deployed and if you login into the pod `oc exec -it pod-id sh` and make a `curl HTTP://localhost:8080` the container is deployed as expected but looks that the route in order to expose this service is not "ready"