Compute Node Not Getting PXE boot During Scale-In/Out Activity

Pradeep Antil pradeepantil at gmail.com
Tue Jan 25 12:15:32 UTC 2022


Hello Folks,

Hope you are doing well !

I have a compute node (SRIOV) in my RedHat Openstack 13 Lab. I have a task
to remove the sriov compute and add it back as a dpdk compute node.

After removing this node as scale-in activity via overcloud stack when I
tried to add it again, introspection for this node is failing. After
looking into the logs in undercloud , it appears like it is not getting the
ip address from pxe.

# cat /var/log/messages|grep -i "0c:42:a1:45:03:10" --color

[image: image.png]

[root at director ~]# tcpdump -n -i br-ctlplane -e | grep -i
"0c:42:a1:45:03:10" --color
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-ctlplane, link-type EN10MB (Ethernet), capture size 262144
bytes
23:54:08.653057 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 394
23:54:12.669877 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 394
23:54:20.744605 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 394
23:54:36.839226 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 394
23:56:48.967623 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6
(0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report
v2, 1 group record(s), length 28
23:56:49.044752 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300
23:56:49.269645 0c:42:a1:45:03:10 > 33:33:ff:45:03:10, ethertype IPv6
(0x86dd), length 86: :: > ff02::1:ff45:310: ICMP6, neighbor solicitation,
who has fe80::e42:a1ff:fe45:310, length 32
23:56:49.781577 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6
(0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report
v2, 1 group record(s), length 28
23:56:50.271663 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6
(0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
23:56:50.271922 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6
(0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router
solicitation, length 16
23:56:50.368576 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6
(0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6,
multicast listener report v2, 1 group record(s), length 28
23:56:54.274049 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6
(0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router
solicitation, length 16
23:56:54.675024 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300
23:56:58.282332 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6
(0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router
solicitation, length 16
23:57:07.638252 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300
23:57:10.053205 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300
23:57:18.720085 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300
23:57:32.817306 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800),
length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 0c:42:a1:45:03:10, length 300

Physical connectivity of this node is intact. Any idea and suggestions ?
how this issue can be fixed.

-- 
Best Regards
Pradeep Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220125/1543f254/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 147668 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220125/1543f254/attachment-0001.png>


More information about the openstack-discuss mailing list