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 1627709 - Host Group information when provisioning a discovered host doesn't autofill
Summary: Host Group information when provisioning a discovered host doesn't autofill
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.4
Hardware: All
OS: Linux
unspecified
high
Target Milestone: 6.4.0
Assignee: Rahul Bajaj
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-11 10:02 UTC by Nagoor Shaik
Modified: 2019-11-05 23:35 UTC (History)
6 users (show)

Fixed In Version: foreman-1.18.0.36-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24940 0 None None None 2018-09-14 09:44:14 UTC

Description Nagoor Shaik 2018-09-11 10:02:13 UTC
Description of problem:
Host Group information when provisioning a discovered host doesn't autofill

Version-Release number of selected component (if applicable):
satellite-6.4.0-13.el7sat.noarch
foreman-1.18.0.18-1.el7sat.noarch
foreman-discovery-image-3.4.4-5.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.0-2.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.4-1.el7sat.noarch
tfm-rubygem-foreman_discovery-12.0.2-1.el7sat.noarc

How reproducible:
100%

Steps to Reproduce:
1. Create a Host Group with some values
2. Discoverer a host and click on **Customize Host**
3. Select a Host Group, which should auto-fill the values from the Host Group, but it's always empty. 

Actual results:
Host Group details don't fill during provisioning a discovered host.

Expected results:
Values should be populated from the Host Group 

Additional info:

Comment 3 Marek Hulan 2018-09-14 09:44:12 UTC
Created redmine issue https://projects.theforeman.org/issues/24940 from this bug

Comment 4 Rahul Bajaj 2018-09-15 12:35:38 UTC
Suggested changes : https://github.com/theforeman/foreman/pull/6072

Comment 5 Satellite Program 2018-09-20 10:09:07 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24940 has been resolved.

Comment 6 Patrick Creech 2018-09-21 02:22:31 UTC
wrong bug

Comment 8 Patrick Creech 2018-09-21 17:20:53 UTC
Switching to failed cherry-pick, moving back to modified.  This was accidentally merged while introducing a unit test error

Comment 9 Lukas Zapletal 2018-09-24 10:09:50 UTC
This was me overlooking a failed test in set of other random failures upstream. I am investigating this.

Comment 10 Rahul Bajaj 2018-09-25 10:33:37 UTC
Sorry for the inconvenience caused, Lukas has fixed the upstream issue.

So the suggested changes are:

https://github.com/theforeman/foreman/pull/6088
https://github.com/theforeman/foreman/pull/6072

These changes fix the issue.

Comment 16 Bryan Kearney 2018-10-16 19:22:11 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:2927


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