Compute Node Not Getting PXE boot During Scale-In/Out Activity
by Pradeep Antil
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@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
2 years, 11 months
[Meeting] RDO meeting minutes - 2022-01-12
by Joel Capitao
==============================
#rdo: RDO meeting - 2022-01-12
==============================
Meeting started by jcapitao at 14:02:58 UTC. The full logs are
available athttps://meetings.opendev.org/meetings/rdo_meeting___2022_01_12/2022/rdo...
.
Meeting summary
---------------
* roll call (jcapitao, 14:03:08)
* Upstream updates - Summit, Elections (jcapitao, 14:06:54)
* LINK: - https://cfp.openinfra.dev/ (spotz_, 14:10:05)
* LINK: https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals
(spotz_, 14:11:18)
* Devconf reminder (jcapitao, 14:19:23)
* LINK: https://devconfcz2022.sched.com/event/sjOE/rdo-meetup
(jcapitao, 14:24:24)
* Update about CentOS Stream 9 adoption (jcapitao, 14:26:52)
* LINK: https://review.rdoproject.org/r/c/rdo-jobs/+/37379 (jcapitao,
14:27:04)
* next week's chair (jcapitao, 14:34:17)
* ACTION: spotz_ to chair next week (jcapitao, 14:35:37)
* open floor (jcapitao, 14:35:46)
Meeting ended at 14:41:51 UTC.
Action items, by person
-----------------------
* spotz_
* spotz_ to chair next week
People present (lines said)
---------------------------
* jcapitao (36)
* spotz_ (21)
* amoralej (13)
* opendevmeet (8)
* ykarel (8)
* fserucas (1)
* rdogerrit (1)
* spotz (0)
Generated by `MeetBot`_ 0.1.4
2 years, 11 months
[Meeting] RDO meeting minutes - 2022-01-05
by Alfredo Moralejo Alonso
==============================
#rdo: RDO meeting - 2022-01-05
==============================
Meeting started by amoralej at 14:02:48 UTC. The full logs are
available athttps://meetings.opendev.org/meetings/rdo_meeting___2022_01_05/2022/rdo...
.
Meeting summary
---------------
* Status of CentOS Linux 8 EOL (amoralej, 14:06:52)
* CentOS Linux 8 is being removed from official mirrors on Feb 1st.
Anyone using it should move to CentOS Stream 8 (amoralej, 14:08:47)
* ACTION: RDO team to double check if centos/8/ repos are used
somewhere (amoralej, 14:10:41)
* Update about CentOS 9 adoption in RDO (amoralej, 14:12:16)
* RDO Trunk repo for CentOS9 and wallaby is consistent and running
https://trunk.rdoproject.org/centos9-wallaby/report.html (amoralej,
14:13:06)
* we are currently working to backport support for cs9 in upstream
projects (amoralej, 14:13:23)
* RDO will provide packages for CS8 and CS9 in Yoga for OpenStack
packages in coordinated release. For TripleO is still under
discussion. (amoralej, 14:17:48)
* ACTION: jcapitao will chair next week (amoralej, 14:22:01)
Meeting ended at 14:25:51 UTC.
Action items, by person
-----------------------
* jcapitao
* jcapitao will chair next week
People present (lines said)
---------------------------
* amoralej (12)
* opendevmeet (4)
* jcapitao (1)
* spotz (1)
* rdogerrit (1)
Generated by `MeetBot`_ 0.1.4
2 years, 11 months