ray submit et al fail on a different yaml than the cluster was created with

[shadeofblue]

Actual result:
When you try ray submit, ray attach, etc. using a different cluster yaml file than what the cluster was spawned with, it results in an SSH password prompt

Expected result:
I'd expect the command to be somehow aware that the cluster had not been created for this particular yaml and to throw a more appropriate error to communicate the need to start this cluster first

[mateuszsrebrny]

For now:

• make this situation fail without misleading asking for ssh password

Ultimate solution (when we support multiple-clusters)

• check how AWS node provider handles that
• discover that this cluster is different and fail