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.

Created attachment 1099596 [details]
Some parameters value display as N/A on 'Discovery Status' screen

Description of problem:

In case of unattended pxeless discovery, I found some parameters have same "N/A" value. like:

Primary NIC: N/A
Primary IPv4: N/A

Latest server response:

We should populate the correct values with them. Please see the attached screenshot.

Version-Release number of selected component (if applicable):
satellite 6.1.5 compose2 (Satellite-6.1.0-RHEL-7-20151125.0/)

How reproducible:
always

Steps to Reproduce:
1. discover a host via unattended pxe-less discovery
2.
3.

Actual results:
Some parameters value display as N/A on 'Discovery Status' screen while performing unattended pxe-less discovery

Expected results:
We should populate the correct values with them

Additional info:

Connecting redmine issue http://projects.theforeman.org/issues/12411 from this bug

Cosmetic issue, we get to it in the future.

Guys, this is trivial thing that does not need to be tracked here, we have an upstream issue, I am unlikely to work on that soon.