Pods get stuck at scaling to 0, and is persistent during reboots. A full shutdown/startup clears it.

Description

Since the upgrade to 22.02.01 I've had some issues with apps behaving weirdly. I didn't see much about it so I assume I did something. However, a reboot usually would fix it and I don't mind going that route. However, now pods are getting stuck at scaling to 0 when trying to restart or upgrade. This scaling to 0 task queues anything else and no actions will be taken until this finally decides to clear. The only way to clear this manually is a full shutdown, as a reboot leaves the scaling to 0 tasks still running. The error currently exists on my secondary box, which does have services I'd like to get running again. I can wait a bit in case there are things you need me to do.

Problem/Justification

None

Impact

None

Activity

Show:

Waqar 
May 25, 2022 at 4:43 PM

Feedback timeout

Waqar 
May 14, 2022 at 12:41 AM

I am not seeing any job stuck at scaling pods to either 0 or 1 or up. Secondly the pods themselves are running nicely as well and kubernetes is not reporting any stuck state at the time the debug was taken. Secondly you are on 22.02.0.1, can you please upgrade to latest stable version and confirm if this is an issue ? If it is, can you please attach a newer debug of the system right after reproducing the problem ? Thanks!

Joshua Walls 
May 3, 2022 at 12:04 AM

Attached is the new debug. Just a note, that problem happens 99% of the time the machine reboots. I'll have to reboot for 20-30 minutes straight before apps work again. So I try to not turn it off.

Joshua Walls 
May 3, 2022 at 12:03 AM

new debug

Waqar 
May 1, 2022 at 7:11 PM

at the time the debug was taken, the system was affected by so the cluster is not running at the time. Could you please reboot the system again and share a newer debug ? Thanks!

Need additional information

Details

Assignee

Reporter

Labels

Impact

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created April 28, 2022 at 1:34 PM
Updated July 6, 2022 at 8:58 PM
Resolved May 25, 2022 at 4:43 PM