A-I-O Duplex - PXe cant see the second controller

Bug #1883432 reported by BN
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
BN

Bug Description

Hello,

I have 3 HP Proiliant G6 server with 64GB RAM, 16 CPU, 3NIC's, 2 800HD on each server.

Simple setup: Router (10.0.0.0/16, gw 10.0.0.1) - connected to switch - all servers connected to that switch with 2 RJ-45. 2 servers are connected to each other via RJ45 as recommended here https://prnt.sc/szif9k. So I decided to go for AIO Duplex setup where I will have 2 controllers and 1 extended worker node.

Thus, I installed StarlingX 3.0 on USB stick and deployed it on my first controller-machine. All info related to my controller-0 machine: http://paste.openstack.org/show/794744/

Thereafter, I want to deploy starlingx on second controller and as I understood I dont need to run installation on second controller using usb stick again. I can just use PXE to start installation on second controller. Following https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_duplex_install_kubernetes.html#install-software-on-controller-1-node I start my second server in Network boot mode as you can see by that screenshot - it cant find boot filename via PXE: https://prnt.sc/sziek5 ; Any suggestions on that please? I can see that network is configured on my first machine therefore, I cant figure out why second machine cannot start deployment via network boot.

Thank you and regards

Tags: stx.config
BN (zatoichy)
description: updated
Revision history for this message
BN (zatoichy) wrote :

Issue was related to network interface misconfiguration.

Closed. thank you

Changed in starlingx:
assignee: nobody → BN (zatoichy)
status: New → Invalid
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
tags: added: stx.config
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.