Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1678892 - system purpose dropdowns are not disabled when no values present
Summary: system purpose dropdowns are not disabled when no values present
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.5.0
Assignee: Jonathon Turel
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-19 20:06 UTC by Jonathon Turel
Modified: 2019-11-22 18:19 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-katello-3.10.0.25-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-14 12:40:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26117 0 Normal Closed system purpose dropdowns are not disabled when no values present 2020-07-17 04:54:18 UTC
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:40:23 UTC

Description Jonathon Turel 2019-02-19 20:06:16 UTC
Description of problem:

Before a manifest containing syspurpose values has been imported the corresponding dropdowns on the content host details UI are empty


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


How reproducible: always


Steps to Reproduce:
1. spin up a 6.5 satellite
2. register a content host
3. 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:

Comment 4 Jonathon Turel 2019-02-22 14:27:44 UTC
Created redmine issue https://projects.theforeman.org/issues/26117 from this bug

Comment 5 Bryan Kearney 2019-03-04 15:03:26 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26117 has been resolved.

Comment 8 Radovan Drazny 2019-04-29 11:04:27 UTC
Verified on Sat 6.5 Snap 25. Syspurpose dropdowns for a freshly registered content host contain following items:

Service Level (SLA):
 - Self-support
 - Standard
 - Premium

Usage Type:
 - Production
 - Development/Test
 - Disaster Recovery

Role:
 - Red Hat Enterprise Linux Server
 - Red Hat Enterprise Linux Workstation
 - Red Hat Enterprise Linux Compute Node

Add ons item is not editable without a subscription containing an Add-on attribute.

Comment 11 errata-xmlrpc 2019-05-14 12:40:09 UTC
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


Note You need to log in before you can comment on or make changes to this bug.