This problem affects me too.
It was introduced around the time when kernel version 18.104.22.168 was relesased. Before that update the network connection worked flawlessly. Therefore I am marking it as a regression.
I can reproduce this bug with the same steps Mathieu pointed out:
ethtool -s eth0 autoneg off