hello,

it's much more worse than https://issues.jenkins-ci.org/browse/JENKINS-35174

if Jenkins have 2 active clouds configured AND the same label is present in both clouds - something very strange appears.

first - Jenkins stopped to execute jobs even if slave with required label is present, connected and running.

second - Jenkins stopped to provision slaves

third - Jenkins web interface stopped working, it turns to endless "loading" 

–

My idea was to have 2 clouds configured, use private OpenStack as primary and DigitalOcean as secondary to extend capacity on demand, but seems it's not possible at all.

–

the only workaround is to set different labels for different clouds, like "os-centos-7-x64" and "do-centos-7-x64", what is not convenient, because we have 800+ jobs to reconfigure. another workaround is to serve i.e. 32bit nodes on DigitalOcean and 64bit nodes on OpenStack which is not scalable.

we have 140 plugins installed, so perhaps other installed plugins may prevent Jenkins from working normally, but I have no idea on how to debug that because there are no logs or errors. 

just an example of error re: plugins conflict. in our installation Terminal plugin prevents Openstack plugin configuration. every attempt to save added Openstack cloud ends with stacktrace. it was needed to deinstall Terminal plugin to use OpenStack in Jenkins. 

just a question. is there some priority also for configured clouds? i.e. create everything on private cloud, if full - create on paid cloud