Jenkins hides/disables the master labeling and tie breaking options when the master is the only node. This makes sense for static slaves, but doesn't work for cloud, dynamically provisioned environments.

For example, let's say I have a master jenkins configured to dynamically provision slaves in the EC2 cloud as demand requires. If there isn't a job running, which would have forced a slave to be active, then I can't configure the master's labels and usage options. If I wait for a job to provision a slave, I can configure the options, but I'm not sure they persist or behave correctly after.

My suggestion would be to either leave the labeling options visible at all times, or make them visible when a Cloud is configured.