Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to bring up Physical BMS server as worker node using PXE booting #261

Open
vpadarthi-git opened this issue Dec 27, 2021 · 1 comment
Labels
help wanted Extra attention is needed question/support This is not a bug but a question or support

Comments

@vpadarthi-git
Copy link

We have broughtup our helper node using centos7 . once helper nodes comes up configured vars.yaml file and main.yaml file ,ran ansible palybooks and successful.
Created manifests and ignition configs sucessfuly and copied

cp ~/ocp4/*.ign /var/www/html/ignition/

restorecon -vR /var/www/html/

restorecon -vR /var/lib/tftpboot/

chmod o+r /var/www/html/ignition/*.ign

We are trying to bringup mixed mode setup (Both VM and 1 Physical BMS as compute node).We are trying to bring 3 master VM's , 2 worker vm's and 1 Physicl bms server as worker node

Master VM's -3
Woeker VM's -2
Physicl BMS as worker node -1

bootstarp,Master ,Worker vm's coming up fine. but we are facing issue while physical bms server brining up as worker node.

Physical BMS server boot option set as network boot , This sever able to do PXE boot up ,Get IP address from DHCP server ,able to down load RHCOS images and install it.
But this process is repeating as loop in the server . Need help to fix this issue .

Am i missing any configuration ?
Is there some configuration I need to handle from PXE server configuration end .which resides in Helper node ?
Please help to fix the issue

image

Output from Physical BMS server (able to install the image but repeating the same process as loop)
=======================

Intel(R) Boot Agent GE v1.3.98
Copyright (C) 1997-2012, Intel Corporation

CLIENT MAC ADDR: 00 25 90 C4 E8 A7 GUID: 00000000 0000 0000 0000 002590C4E8A6
CLIENT IP: 192.168.7.13 MASK: 255.255.255.0 DHCP IP: 192.168.7.77
CLIENT IP: 192.168.7.13 MASK: 255.255.255.0 DHCP IP: 192.168.7.77
GATEWAY IP: 192.168.7.1

PXELINUX 4.05 0x5bd8f633 Copyright (C) 1994-2011 H. Peter Anvin et al
!PXE entry point found (we hope) at 951A:0106 via plan A
UNDI code segment at 951A len 56B0
UNDI data segment at 8EDD len 63D0
Getting cached packet 01 02 03
My IP address seems to be C0A8070D 192.168.7.13
ip=192.168.7.13:192.168.7.77:192.168.7.1:255.255.255.0
BOOTIF=01-00-25-90-c4-e8-a7
SYSUUID=00000000-0000-0000-0000-002590c4e8a6
TFTP prefix:
Trying to load: pxelinux.cfg/01-00-25-90-c4-e8-a7 ok
boot:
Loading rhcos/kernel...........
Loading rhcos/initramfs.img....................................................
.........................ready.

Configurations:

[root@helper ocp4-helpernode]# cat vars.yaml

disk: sda
helper:
name: "helper"
ipaddr: "192.168.7.77"
dns:
domain: "example.com"
clusterid: "ocp4"
forwarder1: "8.8.8.8"
forwarder2: "8.8.4.4"
dhcp:
router: "192.168.7.1"
bcast: "192.168.7.255"
netmask: "255.255.255.0"
poolstart: "192.168.7.10"
poolend: "192.168.7.30"
ipid: "192.168.7.0"
netmaskid: "255.255.255.0"
bootstrap:
name: "bootstrap"
ipaddr: "192.168.7.20"
macaddr: "52:54:00:60:72:67"
masters:

  • name: "master0"
    ipaddr: "192.168.7.21"
    macaddr: "52:54:00:e7:9d:67"
  • name: "master1"
    ipaddr: "192.168.7.22"
    macaddr: "52:54:00:80:16:23"
  • name: "master2"
    ipaddr: "192.168.7.23"
    macaddr: "52:54:00:d5:1c:39"
    workers:
  • name: "worker0"
    ipaddr: "192.168.7.11"
    macaddr: "52:54:00:f4:26:a1"
  • name: "worker1"
    ipaddr: "192.168.7.12"
    macaddr: "52:54:00:82:90:00"
  • name: "worker2" >>>>>>Physical BMS Server
    ipaddr: "192.168.7.13"
    macaddr: "00:25:90:c4:e8:a7"
    other:
  • name: "non-cluster-vm"
    ipaddr: "192.168.7.31"
    macaddr: "52:54:00:f4:2e:2e"

[root@helper ocp4-helpernode]# cat vars/main.yml

ssh_gen_key: true
install_filetranspiler: false
staticips: false
force_ocp_download: false
remove_old_config_files: false
ocp_bios: "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live-rootfs.x86_64.img"
ocp_initramfs: "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live-initramfs.x86_64.img"
ocp_install_kernel: "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.6/4.6.8/rhcos-4.6.8-x86_64-live-kernel-x86_64"
ocp_client: "https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.6.36/openshift-client-linux-4.6.36.tar.gz"
ocp_installer: "https://mirror.openshift.com/pub/openshift-v4/clients/ocp/4.6.36/openshift-install-linux-4.6.36.tar.gz"
helm_source: "https://get.helm.sh/helm-v3.5.0-linux-amd64.tar.gz"
chars: (\_|\$|\|\/|\=|\)|\(|\&|\^|\%|\$|\#|\@|\!|\*)
ppc64le: false
uefi: false
chronyconfig:
enabled: false
setup_registry:
deploy: false
autosync_registry: false
registry_image: docker.io/library/registry:2
local_repo: "ocp4/openshift4"
product_repo: "openshift-release-dev"
release_name: "ocp-release"
release_tag: "4.6.36-x86_64"
[root@helper ocp4-helpernode]#

Helper node services:

[root@helper ocp4-helpernode]# /usr/local/bin/helpernodecheck services
Status of services:

Status of dhcpd svc -> Active: active (running) since Fri 2021-12-24 11:34:29 PST; 2 days ago
Status of named svc -> Active: active (running) since Fri 2021-12-24 11:34:27 PST; 2 days ago
Status of haproxy svc -> Active: active (running) since Fri 2021-12-24 11:34:27 PST; 2 days ago
Status of httpd svc -> Active: active (running) since Fri 2021-12-24 11:34:29 PST; 2 days ago
Status of tftp svc -> Active: active (running) since Fri 2021-12-24 12:54:15 PST; 2 days ago
Unit keepalived.service could not be found.
Status of keepalived svc ->
Unit local-registry.service could not be found.
Status of local-registry svc ->
[root@helper ocp4-helpernode]#

[root@helper ocp4-helpernode]# ls -ltr /var/lib/tftpboot/pxelinux.cfg/
total 36
-r-xr-xr-x. 1 root root 444 Dec 24 11:33 01-52-54-00-60-72-67
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-52-54-00-e7-9d-67
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-52-54-00-80-16-23
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-52-54-00-d5-1c-39
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-52-54-00-f4-26-a1
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-52-54-00-82-90-00
-r-xr-xr-x. 1 root root 427 Dec 24 11:33 01-00-25-90-c4-e8-a7

[root@helper pxelinux.cfg]# cat 01-52-54-00-60-72-67

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Bootstrap Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/bootstrap.ign

[root@helper pxelinux.cfg]# cat 01-52-54-00-e7-9d-67

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Master Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/master.ign

[root@helper pxelinux.cfg]# cat 01-52-54-00-80-16-23

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Master Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/master.ign
[root@helper pxelinux.cfg]#
[root@helper pxelinux.cfg]# cat 01-52-54-00-d5-1c-39

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Master Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/master.ign
[root@helper pxelinux.cfg]# cat 01-52-54-00-f4-26-a1

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Worker Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/worker.ign
[root@helper pxelinux.cfg]# cat 01-52-54-00-82-90-00

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Worker Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/worker.ign
[root@helper pxelinux.cfg]#
[root@helper pxelinux.cfg]# cat 01-00-25-90-c4-e8-a7

default menu.c32
prompt 1
timeout 9
ONTIMEOUT 1
menu title ######## PXE Boot Menu ########
label 1
menu label ^1) Install Worker Node
menu default
kernel rhcos/kernel
append initrd=rhcos/initramfs.img nomodeset rd.neednet=1 ip=dhcp coreos.inst=yes coreos.inst.install_dev=sda coreos.live.rootfs_url=http://192.168.7.77:8080/install/rootfs.img coreos.inst.ignition_url=http://192.168.7.77:8080/ignition/worker.ign
[root@helper pxelinux.cfg]#

@christianh814 christianh814 added help wanted Extra attention is needed question/support This is not a bug but a question or support labels Feb 4, 2022
@christianh814
Copy link
Contributor

We've switched to 4.9 ...can you try again with the latest version of the playbook from main?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question/support This is not a bug but a question or support
Projects
None yet
Development

No branches or pull requests

2 participants