Bug 1285980 - Some parameters value display as N/A on 'Discovery Status' screen while performing unattended pxe-less discovery
Summary: Some parameters value display as N/A on 'Discovery Status' screen while perfo...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-27 06:54 UTC by Sachin Ghai
Modified: 2019-10-10 10:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-24 08:42:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Some parameters value display as N/A on 'Discovery Status' screen (24.27 KB, image/png)
2015-11-27 06:54 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12411 0 Normal New With pxeless discovery, discovery Status screen doesn't display the discovery server 2020-09-24 08:56:21 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.