Master node unable to start gravity-site Pod

[a-palchikov]

Description

What happened: From one of the failed upgrades - the to be upgraded master node failed to start gravity-site Pod due to the failure to pull the image from the current leader. It is suspected to do with the fact that the upgrade was initiated immediately after joining a new master node to the cluster and the node's registry being empty before it became the leader.

What you expected to happen: Master node should be able to come up back after upgrading the system container and able to start all services.

How to reproduce it (as minimally and precisely as possible): Sadly it is only a suspicion and a useful reproduction is not available.

Environment

• Gravity version [e.g. 7.0.11]: 7.0.34
• Platform [e.g. Vmware, AWS]: aws