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 1378571 - Selecting architecture in hostgroup doesn't update operating system
Summary: Selecting architecture in hostgroup doesn't update operating system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Martin Korbel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 18:47 UTC by Tom McKay
Modified: 2019-04-01 20:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:49:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16532 0 None None None 2016-09-22 18:47:03 UTC

Description Tom McKay 2016-09-22 18:47:02 UTC 
1. new hostgroup form
2. select architecture
3. operatingsystems select box stays empty.

Seems like a regressions from https://github.com/theforeman/foreman/commit/4cbf879ed5957978afd74b3707c8a6b16fa18225#diff-8f01b651da121a774de5a75ce7332f7dL48
Comment 1 Tom McKay 2016-09-22 18:47:05 UTC 
Created from redmine issue http://projects.theforeman.org/issues/16532
Comment 2 Tom McKay 2016-09-22 18:47:09 UTC 
Upstream bug assigned to lzap
Comment 4 Bryan Kearney 2016-09-22 20:20:27 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16532 has been resolved.
Comment 7 Martin Korbel 2016-10-19 11:36:12 UTC 
VERIFIED on foreman-1.13.0-1.el7

Reproducer:
1. we have got sat6 with synced one repo at least.
2. create new host group via WebUI
3. click on the "Operation System" tab
4. choose one of the architectures (in my case i386). selectbox "Operation system" is empty/disabled  (I do not have i386 repo synced).
5. choose the second architecture (in my case x86_64). The selectbox "Operation system" was updated, we can open it and choose OS (RHEL Server 7.2 in my case).
Comment 8 Oleksandr Shtaier 2017-08-10 09:26:48 UTC 
Not sure what scenario was exactly mentioned here. Was it about fact that 'operating system' field is auto-refreshed(selectbox is empty, but proper value can be selected) or auto-populated(selectbox is already contain first proper value from the list once architecture is selected). Anyway both scenarios can be covered by test automation scripts. Steps from Verification section are already present, so put qe_test_coverage to '+'
Comment 9 Satellite Program 2018-02-21 16:49:54 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.