properly handle disappearing deployment

apimeister / tibco-ems-operator

A Kubernetes operator for Tibco EMS.

Apache License 2.0

4 stars 2 forks source link

properly handle disappearing deployment #5

Open JensWalter opened 3 years ago

JensWalter commented 3 years ago

When a deployment does no longer exists, the following error is thrown in a continuous loop:

[2021-08-16T01:16:29Z ERROR tibco_ems_operator::scaler] scale up failed: Api(ErrorResponse { status: "Failure", message: "deployments.apps \"bw-intercab-booking\" not found", reason: "NotFound", code: 404 })

If a deployment does no longer exists, it should be remove from the deployment targets.

alexkunde commented 3 years ago

We should test, but I believe this was fixed in this commit

alexkunde commented 2 years ago

not fixed

[2022-09-09T05:43:42Z ERROR tibco_ems_operator::scaler] scale down failed: ApiError: deployments.apps "rs-dlq-processor" not found: NotFound (ErrorResponse { status: "Failure", message: "deployments.apps \"rs-dlq-processor\" not found", reason: "NotFound", code: 404 })