<div dir="ltr"><span class="gmail-ui-provider gmail-bzm gmail-bzn gmail-c gmail-d gmail-e gmail-f gmail-g gmail-h gmail-i gmail-j gmail-k gmail-l gmail-m gmail-n gmail-o gmail-p gmail-q gmail-r gmail-s gmail-t gmail-bzo gmail-bzp gmail-w gmail-x gmail-y gmail-z gmail-ab gmail-ac gmail-ae gmail-af gmail-ag gmail-ah gmail-ai gmail-aj gmail-ak" dir="ltr"><p>Hi Team,</p><p>Scenario:<br>
We were performing overcloud deployment.<br>
During this, we were continuously facing the following errors on two of the nodes out of the four nodes:</p><p> </p><p> PLAY [Overcloud Node Grow Volumes] *********************************************<br>
2023-06-02 19:07:33.483504 | 52540049-4965-0177-e681-00000000000a | TASK | Wait for provisioned nodes to boot<br>
[WARNING]: Unhandled error in Python interpreter discovery for host overcloud-<br>
controller-0: Failed to connect to the host via ssh: ssh: connect to host<br>
30.30.30.219 port 22: No route to host<br>
[WARNING]: Unhandled error in Python interpreter discovery for host overcloud-<br>
controller-0: Failed to connect to the host via ssh: ssh: connect to host<br>
30.30.30.219 port 22: Connection refused</p><p> </p><p>We faced this error when we were performing overcloud node provisioning.</p><p> </p><p>To resolve this issue, we had to update the image and create a user to access the nodes.<br>
We were able to access the nodes via this user through the BMC console.</p><p>This implied that OS was getting correctly installed on the node.<br>
Once we accessed the logs on the failed node we came across the following logs:</p><p> 2023-06-13 09:02:16.120 INFO os_net_config.utils._ordered_nics Finding active nics<br>
2023-06-13 09:02:16.120 INFO os_net_config.utils._ordered_nics eno1 is an embedded active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics ens2f0 is an active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics eno4 is an embedded active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics eno2 is an embedded active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics ens1f0 is not an active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics lo is not an active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics ens2f1 is an active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics eno3 is an embedded active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics ens1f1 is an active nic<br>
2023-06-13 09:02:16.121 INFO os_net_config.utils._ordered_nics No DPDK mapping available in path (/var/lib/os-net-config/dpdk_mapping.yaml)<br>
2023-06-13 09:02:16.122 INFO os_net_config.utils._ordered_nics Active nics are ['eno1', 'eno2', 'eno3', 'eno4', 'ens1f1', 'ens2f0', 'ens2f1']<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic2 mapped to: eno2<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic6 mapped to: ens2f0<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic5 mapped to: ens1f1<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic3 mapped to: eno3<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic7 mapped to: ens2f1<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic1 mapped to: eno1<br>
2023-06-13 09:02:16.122 INFO os_net_config.objects.mapped_nics nic4 mapped to: eno4</p><p> </p><p><br>
As we can see in the above logs, only 7 nics are active. <br>
But as per our bond config file, we required 8 interfaces:<br>
a. nic-1 for management IP<br>
b. nic-3 and nic-4 for the br-tenant-2 network.<br>
c. nic-5 and nic-6 for the br-tenant network.<br>
d. nic-7 and nic 8 for the br-ex network.</p><p> </p><p>The wire was faulty in this case and hence only 7 interfaces were available</p><p> </p><p>Query:<br>
The logs which are visible while we run "openstack overcloud node provision" are not very informative.<br>
Is there any way where we could get these logs on the undercloud node itself?<br>
This could save some time for future references</p></span><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr">~ Lokendra<br></div><div>skype: lokendrarathour</div><div dir="ltr"><img width="200" height="41" src="https://ci3.googleusercontent.com/mail-sig/AIorK4zyd6LpJOGqagxmzUlY59eMQx0-FN0t8HtjdtGE7VLZSKIxBUz3bI7z-MBqbgDVg1-XbtvHgN_ATJ10N6bonyO-JSGTtl5s_mNSbDoXBg"><br></div><div dir="ltr"><br></div></div></div></div></div>