Project

General

Profile

Actions

Support #17267

open

Unable to upload the facts to the foreman server

Added by Vikram C over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Discovery plugin
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi Team,

I am using the discovery plugin with the foreman and using the discovery-remaster script to generate own
fdi-bootable-3.0.5-161108_145955.iso

with the below options on the CISCO UCS Bare Metal server.

discovery-remaster fdi-bootable-3.0.5.iso "fdi.pxip=10.4.40.227/24 fdi.pxgw=10.4.40.1 fdi.pxdns=10.4.196.15 proxy.url=https://10.10.198.95:443 proxy.type=foreman fdi.pxfactname1=deployment_type fdi.pxfactvalue1=database_server fdi.pxmac=00:25:b5:04:32:dd fdi.pxauto=1"

Once i boot the server. it is failing to upload the facts to the server.

Please help me to fix the issue.

Regards,
Vikram


Files

discovery.PNG View discovery.PNG 14.1 KB Vikram C, 11/08/2016 04:50 AM
discovery_debug.txt discovery_debug.txt 31.4 KB Vikram C, 11/20/2016 02:59 PM

Related issues 1 (0 open1 closed)

Copied to Discovery - Support #17313: Unable to upload the facts to the foreman serverClosed11/08/2016Actions
Actions #1

Updated by Vikram C over 7 years ago

Adding my Pxe default template.

<%#
kind: PXELinux
name: PXELinux global default
>
<
# Used to boot unknown hosts, do not associate or change the name. %>

DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local

<%= snippet "pxelinux_chainload" %>

<%= snippet "pxelinux_discovery" %>

<% for profile in @profiles
url = default_template_url(profile[:template], profile[:hostgroup])
case profile[:pxe_type]
when 'kickstart'
append = "ks=#{url} ksdevice=bootif network kssendmac"
when 'preseed'
locale = profile[:hostgroup].params['lang'] || 'en_US'
append = "interface=auto url=#{url} ramdisk_size=10800 root=/dev/rd/0 rw auto hostname=unassigned-hostname locale=#{locale} console-setup/ask_detect=false console-setup/layout=USA console-setup/variant=USA"
else
raise("PXE type #{profile[:pxe_type]} not supported by template #{template_name}")
end >
LABEL <
= "#{profile[:hostgroup]} - #{profile[:template]}" >
KERNEL <
= profile[:kernel] >
APPEND initrd=<
= profile[:initrd] > <= append >
LABEL discovery
MENU LABEL Foreman Discovery
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 rd.debug=1 nomodeset proxy.url=https://10.10.198.95:443 proxy.type=foreman
ONTIMEOUT discovery
IPAPPEND 2
<
end %>

Actions #2

Updated by Vikram C over 7 years ago

  • Copied to Support #17313: Unable to upload the facts to the foreman server added
Actions #3

Updated by Lukas Zapletal over 7 years ago

Can you switch to tty3 (or enable ssh) and try network? Does it ping to gateway? Can you ping 10.10.198.95 as well? Also run discovery-debug script and pastebin the output.

What is the issue copy intended for?

Actions #4

Updated by Vikram C over 7 years ago

Hi Lukas,

Yes the network is working fine. i am able to ping the gateway 10.4.40.1 & the IP 10.4.40.227 ( configured by remastering the fdi discovery disk as above) from the foreman, i am able to ssh and login.

But still the error as attached, ( failed to upload facts, check your network credentials )

issue copy of this issue was done by mistake.

Regards,
Vikram

Actions #5

Updated by Vikram C over 7 years ago

Hi Lucas,

I have attached the dicovery-debug o/p, i have the sorted the output in reverse with the "tac" command.

Appreciate your time and help.

regards
Vikram

Actions #6

Updated by Vikram C over 7 years ago

I have logged into the server with ssh.

[root@fdi ~]# ifconfig enp6s0
enp6s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.4.40.227 netmask 255.255.255.0 broadcast 10.4.40.255
inet6 fe80::225:b5ff:fe04:32dd prefixlen 64 scopeid 0x20<link>
ether 00:25:b5:04:32:dd txqueuelen 1000 (Ethernet)
RX packets 3322 bytes 306004 (298.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 625 bytes 206142 (201.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@fdi ~]# ping 10.4.40.1
PING 10.4.40.1 (10.4.40.1) 56(84) bytes of data.
64 bytes from 10.4.40.1: icmp_seq=1 ttl=255 time=0.522 ms
64 bytes from 10.4.40.1: icmp_seq=2 ttl=255 time=0.433 ms
64 bytes from 10.4.40.1: icmp_seq=3 ttl=255 time=0.425 ms
64 bytes from 10.4.40.1: icmp_seq=4 ttl=255 time=0.507 ms
64 bytes from 10.4.40.1: icmp_seq=5 ttl=255 time=0.425 ms

Regards.
Vikram

Actions #7

Updated by Vikram C over 7 years ago

  • Assignee set to Lukas Zapletal
Actions #8

Updated by Lukas Zapletal over 7 years ago

  • Assignee deleted (Lukas Zapletal)
  • Priority changed from High to Normal

I was on vacation last week, sorry for the delay. You can see in the logs, the foreman rails application returns 301 Moved Permanently. We need to see the relevant bit from production.log from foreman server in this case. This should not happen as the "facts" REST API call will work without authorization. Doublecheck if the IP you are requesting from is really Foreman server and not something else.

I'd suggest to run "foreman-fail" on the Foreman server and try to discover once again, pastebin the output. Also run "foreman-debug -u" to upload the debug tarball to our server and paste the URL (file will be password protected).

Foreman version? Katello installed? Discovery plugin version?

Actions

Also available in: Atom PDF