controller-1 is not pxe booting in starlingx-5.0

Bug #1931915 reported by Sriram Dharwadkar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Incomplete
Low
Unassigned

Bug Description

On the single physical interface, mgmt and oam interfaces are created over vlans. pxe network is over an access vlan configured over the same physical interface.
Controller-0 is booted using virtual cd/dvd installation.
Controller-1 is tried over pxe network, but it is not coming up.
Same configuration works in starlingx-4.0 (August 5th release), but it is not working in StarlingX-5.0 (May 22nd release)

tags: added: stx.net
tags: added: stx.networking
removed: stx.net
Revision history for this message
Steven Webster (swebster-wr) wrote :

Hi Sriram,

Is this exactly the same lab environment that you installed the stx-5.0 on vs. stx-4.0? ie. Same switch configuration / same lab?

If you tcpdump on the pxeboot network on controller-0, do you see traffic from controller-1 trying to pxeboot?

Can you provide the output of the system host-if-list controller-[0/1] command?

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as Incomplete while waiting for a response from the reporter

Changed in starlingx:
status: New → Incomplete
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Please also note that due to the 4.18 kernel in stx.5.0, some older hardware is no longer supported. This can also result in failure to pxeboot. See https://bugs.launchpad.net/starlingx/+bug/1933094

Revision history for this message
Steven Webster (swebster-wr) wrote :

Setting priority for low. Still waiting for response from the reporter

Changed in starlingx:
importance: Undecided → Low
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.