Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-09-01 Thread Amish
On 18/08/21 12:24 pm, Amish wrote: Hello Further to my previous email: I see that there is already an *extremely similar issue* reported on July 12, 2021 and it has been fixed. https://github.com/systemd/systemd/issues/20203 But I do not know if this fix exists in systemd v249.3 (Arch

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-18 Thread Arian van Putten
https://github.com/systemd/systemd-stable/pull/111 has not landed in a v249 point release yet. v249.3 was tagged 12 days ago; and that fix was only merged 8 days ago. On Wed, Aug 18, 2021 at 8:56 AM Amish wrote: > Hello > > Further to my previous email: > > I see that there is already an

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-18 Thread Amish
Hello Further to my previous email: I see that there is already an *extremely similar issue* reported on July 12, 2021 and it has been fixed. https://github.com/systemd/systemd/issues/20203 But I do not know if this fix exists in systemd v249.3 (Arch Linux) If it exists that means that fix

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-18 Thread Amish
Hello, Thank you for your reply. I can understand that there can be race. *But when I check logs, there is no race happening*. *Let us see and analyze the logs.* Stage 1: System boots, and kernel assigns eth0, eth1 and eth2 as interface names. Aug 18 09:17:13 kk kernel: e1000e :00:1f.6

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-17 Thread Colin Guthrie
Hiya, As has been said, this is racy. "Sufficiently early" is just a hope, rather than a guarantee. Perhaps something in the kernel made things more or less efficient (try booting with the old kernel to see if it helps, but as this is a race, it may only work some of the time.). Or perhaps

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-16 Thread Amish
On 16/08/21 5:39 pm, Lennart Poettering wrote: On Mo, 16.08.21 17:31, Amish (anon.am...@gmail.com) wrote: On 16/08/21 5:25 pm, Lennart Poettering wrote: On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote: Some old scripts that we have expect interface names starting with eth. But

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-16 Thread Lennart Poettering
On Mo, 16.08.21 17:31, Amish (anon.am...@gmail.com) wrote: > > On 16/08/21 5:25 pm, Lennart Poettering wrote: > > On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote: > > > > > Some old scripts that we have expect interface names starting with eth. > > > But > > > those names are not

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-16 Thread Amish
On 16/08/21 5:25 pm, Lennart Poettering wrote: On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote: Some old scripts that we have expect interface names starting with eth. But those names are not predictable. So to get predictable names starting with eth*, first I temporarily rename

Re: [systemd-devel] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured

2021-08-16 Thread Lennart Poettering
On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote: > Some old scripts that we have expect interface names starting with eth. But > those names are not predictable. > > So to get predictable names starting with eth*, first I temporarily rename > all interface with tmpeth*. This is done via