Bug #12275
closed
Error on unattended discovery status screen: Error - primary - no such connection profile
Added by Sachin Ghai about 9 years ago.
Updated about 9 years ago.
Category:
Discovery plugin
|
|
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
This issue appears only on discovering a host with DHCP but without PXE, unattended mode.
Can you send me list of options the image was remastered with?
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"
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.
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
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.
- 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
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous