-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
During upgrade, If a master is in unready state for 60 mins, upgrade fails with below error.
It wonderful, if there is option to set wait time for the below error.
Error:
Unable to apply 4.18.20: wait has exceeded 40 minutes for these operators: kube-apiserver
Version-Release number of selected component (if applicable):
Cluster version is 4.18.19
upgrading to 4.18.20
How reproducible:
Make a master node unready for 60 mins, then upgrade fails with the above message.
Steps to Reproduce:
1. start upgrade from 4.18.19 to 4.18.20
2. Make a master node unready by dropping all packets(100% packer loss) for 60 mins
docker run --rm --name=net --net=host -e NAMESPACE=default -e DURATION=3600 -e NODE_NAME="ip-10-0-73-242.us-west-2.compute.internal" -e TRAFFIC_TYPE=egress -e EGRESS='{loss: 100%}' -e KUBECONFIG=/tmp/config -e KRKN_KUBE_CONFIG=/tmp/config -e DISTRIBUTION='openshift' -v /tmp/config:/tmp/config:Z quay.io/krkn-chaos/krkn-hub:network-chaos
3. Upgrade fails due to
Unable to apply 4.18.20: wait has exceeded 40 minutes for these operators: kube-apiserver
Actual results:
upgrade from 4.18.19 to 4.18.20 fails
Expected results:
Having option to set wait time to avoid the above error.
Additional info:
- links to