Bug 1665203
Summary: | custom system purpose values not shown in content host details dropdowns | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Jonathon Turel <jturel> |
Component: | Hosts - Content | Assignee: | Jonathon Turel <jturel> |
Status: | CLOSED ERRATA | QA Contact: | Stephen Wadeley <swadeley> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5.0 | CC: | egolov, jturel |
Target Milestone: | 6.5.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-3.10.0.11-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 12:39:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jonathon Turel
2019-01-10 16:56:06 UTC
Created from redmine issue https://projects.theforeman.org/issues/25832 Upstream bug assigned to jturel Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25832 has been resolved. Hi Stephen, You can do this: 1) register a RHEL8 client 2) with the 'syspurpose' CLI tool on the client, set some of the values: - syspurpose set-role "my role" - syspurpose set-usage "development" - syspurpose add-addons "myaddon" They will now show up in the UI for this content host, but slightly differently than before. Prior to my change, you could see that any of the given values were assigned - but when going into edit mode they would disappear. Quite confusing. Now the currently set value will show in the dropdowns or checkboxes in the case of addons when going into edit mode. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222 |