Create a bucket with an invalid name on Windows and server stays in Warmup state

Build 2213

I discovered this while running an automated test but it is equally reproducible from the UI:
1. Attempt to create a bucket with an invalid name, for Windows an example is CON or COM1
2. On the GUI the bucket stays amber indefinitely.
3. The rest call to get the nodes e.g. http://172.23.105.126:8091/nodes/self returns the node status as warmup indefinitely.

Let me know invalid bucket names for Linux and I will test there.

Logs are attached.

Would it be possible to throw an error in this case

This problem looks like it was there for a while.
From the test cases I see the following invalid bucket names for Windows:
CON, AUX, COM1, LPT,PRN.