If no configset exists, CREATE leads to a 500 error with never-ending logging and 100% CPU usage

Here's what I did:

> bin/solr start -e cloud -noprompt

> curl http://localhost:8983/solr/admin/collections?action=CREATE&name=thisshouldfail&numShards=1&configset=thisisaninvalidconfigset&wt=json

The above led to a new collection named thisshouldfail, with the config-set as gettingstarted. This call should have failed as there was no configset by that name. Instead, it picked up the only config set it found and used it.

There's more to this. I'm not sure how related this is but looks like it to me.

> bin/solr start -c

> curl http://localhost:8983/solr/admin/collections?action=CREATE&name=thisshouldfail&numShards=1&configset=thisisaninvalidconfigset&wt=json

This led to a 900M (and growing) log file in addition to 100% CPU until I killed Solr.