Description
Component:
'salt'
What happened:
If we trigger cluster expansion by deploying a new node and in parallel import a new solution in the cluster, the node will fail to deploy. Actually, when importing a solution the salt-master is restarted to mount the new image and due to this the node deployment job is failing.
What was expected:
We should not be able to trigger solution import if a node deployment going on. more generally speaking, all actions requiring a salt-master restart should be aborted if a node deployment is going on.
Steps to reproduce
Launch node deployment from the UI
Launch solution import right after
as a side note, after doing this, the UI was broken: the Node and Volume Pages were not displaying content anymore and some salt-api connection error was displayed in the console. The only way to get rid of this situation was to restart salt-api container.
Resolution proposal (optional):