kong

kong copied to clipboard

Is there an existing issue for this?

• [X] I have searched the existing issues

Kong version ($ kong version)

Kong 2.6.1

Current Behavior

2022/05/10 01:37:28 [error] 1364#0: *10394083 [lua] targets.lua:169: on_target_event(): could not stop DNS renewal for target removed from 844a12e4-ff37-4b09-84d7-b3023b651f95: target object does not contain name and port, context: ngx.timer

Expected Behavior

as it is only thrown when upstream targets are updated.

Steps To Reproduce

1.deploy kong helm chart in k8s cluster
2.rolling update the upstream service
3.error logs are showed

Anything else?

hi team. we are using helm kong in AKS (kong ingress rule -> k8s service). when rolling update out application service,somehow,kong throw this error.I suspect it is kong can not update dns record in time.but there are two replicas for our service,ie one k8s service with two k8s endpoints.

the error is thrown by source(kong/runloop/balancer/targets.lua#L169)

same kong version and same error

@zffocussss @w313062006 We always recommend updating to the latest release. Does this reproduce for 3.4?

@zffocussss @w313062006 We always recommend updating to the latest release. Does this reproduce for 3.4?

I am using 3.2.2 now.

@zffocussss @w313062006 We always recommend updating to the latest release. Does this reproduce for 3.4?

I am using 3.2.2 now.

And did you still get this error message in your new version of 3.2.2?

This issue is marked as stale because it has been open for 14 days with no activity.

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks. We're sorry that your issue could not be resolved. If any new information comes up that could help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look our pledge to the community for more information.

Sincerely, Your Kong Gateway team

StarlightIbuki

3.7版本依然有这个问题