Tianhao Geng
Tianhao Geng
The problem still persist on all k8s variants except 1.25, because upstream kubernetes only bump runc to latest version on 1.25 version. The rest k8s version still remain on old...
@applike-ss Thanks for opening this ticket. I'm going reproduce this issue and get you back.
@nike21oct Thanks for opening this issue! would mind sharing more details with us so we can try to reproduce this issue? what bottlerocket AMI you are using? What is you...
@nike21oct sorry for the late reply. I still try to reproduce this issue. I'll let you know if I need more infos from you or I complete the reproduce.
@nike21oct I wasn't able to reproduce this issue last week. I am working on another priority item now. I'll work on this issue as my next priority. Thank you! Pleas...
@james-masson Thanks for opening this issue! We will investigate on it. : )
That makes sense. However, I think current way people are still getting confused because they don't understand it's a retry test. Maybe we should find a better way to add...
I don't think it's correct maybe I'm wrong. >Currently, pooling for a new update seem to be every 10 seconds: The `attempt` logic here is to deal with 423 Locked...
We can follow up this [issue](https://github.com/bottlerocket-os/bottlerocket-update-operator/issues/326) here.
@14Rahul sorry for late reply. I'm trying to reproduce this issue and will get back to you soon.