Bug 1385528

Description of problem:
There are many places, where user is forced to set an attribute with a single option left.
e.g. New Host -> Location.
If there's only 'Default Location, the field remains 'null' by default and user is forced to manually set it before he's able to proceed with creating new host.

This has several negative effects:
1. It is simply annoying. And time consuming for a user to go through all prerequisites and select the mandatory field.
2. Especially at new-host dialog - user is not forced to choose the Taxonomies as the first step - he can navigate through all the tabs and set whatever fields he likes (including the ones, which don't exist in the Default Location). When he finally sets the location, many of the fields are rendered invalid, requiring user to select them again.

- similar thing happens on OS and provisioning templates. If a new kind of provisioning template is assigned to OS (e.g. PXEGrub template), a 'PXEGrub template' field will appear under OS->Provisioning templates.
Despite the fact, that only a single template has been assigned to the OS, the field is not being set and remains 'Null', causing an error during the actual provisioning.

Version-Release number of selected component (if applicable):
satellite 6.2+

How reproducible:
always

Steps to Reproduce:
1. have a single org and loc (e.g. default ones)
2. Navigate to Hosts -> New Hosts
3. notice the Organization & Location fields are marked as mandatory and are set to 'null' by default despite the fact, there is only 1 possible option for them - Forcing user to set it manually.

Actual results:
the mandatory fields with 1 possible value are not set, causing the values for the rest of the form not being filtered by the taxonomies, allowing user to choose invalid values before he sets the taxonomies themselves.

Expected results:
Set the values automatically everywhere, where possible.


Additional info:
The New Host dialog is not the only place, where similar thing happens.