Project

General

Profile

Actions
Copy link

Bug #12275

closed

Error on unattended discovery status screen: Error - primary - no such connection profile

Added by Sachin Ghai over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Discovery plugin
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman-discovery-image/pull/42
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

On unattended discovery, the host was successfully discovered but status screen doesn't show all the values. Please see the attached screenshot where
Primary NIC and IP address is missing.

Note: host was discovered with only one NIC.

Also, console screen has some error: Error - primary - no such connection profile

reproducible with build:

[root@cloud-qe-19 ~]# rpm -qa | grep discovery
tfm-rubygem-foreman_discovery-4.1.1-1.fm1_11.el7.noarch
tfm-rubygem-hammer_cli_foreman_discovery-doc-0.0.2-3.el7.noarch
rubygem-smart_proxy_discovery-doc-1.0.3-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_discovery-0.0.2-3.el7.noarch
rubygem-smart_proxy_discovery-1.0.3-1.el7.noarch
rubygem-smart_proxy_discovery_image-1.0.5-1.el7.noarch
rubygem-smart_proxy_discovery_image-doc-1.0.5-1.el7.noarch
[root@cloud-qe-19 ~]# ls

Image: fdi-bootable-3.0.2.iso

Files

profile_error.png View profile_error.png 26.6 KB Sachin Ghai, 10/23/2015 05:06 AM
discovery_debug_23oct.txt discovery_debug_23oct.txt 62.2 KB Sachin Ghai, 10/23/2015 05:08 AM

Related issues 1 (0 open — 1 closed)

Related to Discovery - Tracker #10294: PXEless discovery featureClosedLukas Zapletal04/28/2015

Actions
Actions
Copy link
 #1

Updated by Sachin Ghai over 8 years ago

discovery_debug

Actions
Copy link
 #2

Updated by Sachin Ghai over 8 years ago

Actions
Copy link
 #3

Updated by Sachin Ghai over 8 years ago

This issue appears only on discovering a host with DHCP but without PXE, unattended mode.

Actions
Copy link
 #4

Updated by Lukas Zapletal over 8 years ago

Can you send me list of options the image was remastered with?

Actions
Copy link
 #5

Updated by Sachin Ghai over 8 years ago

I just tried with following options and issue is reproducible.

./discovery_remaster fdi-bootable-3.0.2.iso "fdi.pxgw=192.168.100.1 fdi.pxdns=192.168.100.1 proxy.url=https://192.168.100.1:9090 proxy.type=proxy fdi.pxfactname1=myfact fdi.pxfactvalue1=somevalue fdi.pxmac=52:54:00:be:8e:7b fdi.pxauto=1"

Actions
Copy link
 #6

Updated by Lukas Zapletal over 8 years ago

Hmmm this line does not match with the log file, I see

Configuring 52:54:00:be:8e:8a with static info: ip=192.168.100.68/24 gw=192.168.100.1 dns=192.168.100.1

there which means you provided pxip. But I was able to reproduce. Its the unattended with DHCP without PXE scenario. Investigating. Thanks.

Actions
Copy link
 #7

Updated by Sachin Ghai over 8 years ago

Yeah.. the log file was from other host. So just to share the list of options I re-created the iso with some other mac. Sorry for confusion.

And yeah its with unattended with DHCP without PXE scenario. thanks

Actions
Copy link
 #8

Updated by Lukas Zapletal over 8 years ago

Ok you can only reproduce this on a network that does not have DHCP, in that case we throw ugly exception instead of nice message that network credentials could not be acquired. Fixing that, also removing the white warning on top.

If you do this on a network with DHCP server, it provisions fine for me.

Actions
Copy link
 #9

Updated by Lukas Zapletal over 8 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman-discovery-image/pull/42 added
Actions
Copy link
 #10

Updated by Anonymous over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF