Bug #26117
closedsystem purpose dropdowns are not disabled when no values present
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1678892
Description of problem:
Before a manifest containing syspurpose values has been imported the corresponding dropdowns on the content host details UI are empty
Steps to Reproduce:
1. register a content host
2. navigate to the host's details page and click the 'edit' icon next to any System Purpose field
Actual results: the 'edit' button is not disabled, revealing an empty dropdown when clicked
Expected results: 'edit' button should be disabled until the user has a manifest with syspurpose values OR they've set the syspurpose value from CLI tooling
Additional info:
- default values should be provided for Role, Usage, SLA
- edit should be disabled for addons unless they are set on the host or available through manifest