Bug 1285980

Summary: Some parameters value display as N/A on 'Discovery Status' screen while performing unattended pxe-less discovery
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: Discovery PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED UPSTREAM QA Contact: Sachin Ghai <sghai>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.5CC: bbuckingham, bkearney, dmoessne
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12411
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-24 08:42:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Some parameters value display as N/A on 'Discovery Status' screen none

Description Sachin Ghai 2015-11-27 06:54:53 UTC
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:

Comment 3 Bryan Kearney 2015-11-30 13:27:52 UTC
Connecting redmine issue http://projects.theforeman.org/issues/12411 from this bug

Comment 5 Lukas Zapletal 2016-05-13 07:11:49 UTC
Cosmetic issue, we get to it in the future.

Comment 7 Lukas Zapletal 2017-05-24 08:42:27 UTC
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.