tdnf update with PH 5.0 aarch64 results in degraded networking

Describe the bug

Raspberry Pi 4B, 8GB. Wrote photon-rpi-5.0-dde71ec57.aarch64.raw to a 32GB SD and booted without issue, resulting in:
VMware Photon OS 5.0
PHOTON_BUILD_NUMBER=dde71ec57

Aside from changing the password, nothing else is changed. tdnf update finds updates, and after rebooting, the system can no longer get an IP from DHCP. I've also tried a static IP, but that is unable to reach anything either.

Working back through, simply doing: tdnf update --exclude linux,systemd allows the system to work as expected (after a reboot). However, later updating and allowing either one (--exclude linux or --exclude systemd), the system does not work.

Just before rebooting before the last failure, I installed tcpdump. -netli eth0 showed that bootp/dhcp packets were leaving, and the system was able to see incoming CDP, but DHCP packets never progress further. I suspected it was a switchport configuration issue at first (trunk, with the native vlan set and allowed) and tried changing it to an access port on the vlan, but that too didn't work. Furthermore, I have x86_64 systems also running Photon 5.0 are running on the same switch, updated without issue.

Reproduction steps

1. install via image
2. tdnf update --exclude linux,systemd
3. reboot -> ok
4. tdnf update --exclude linux (allows systemd and systemd-{udev,rpm-macros,pam,libs} to install)
5. reboot -> does not work
6. reimage
7. tdnf update --exclude systemd
8. reboot -> does not work
9. reimage
10. tdnf update --exclude linux
11. reboot -> does not work
12. reimage
13. tdnf update --exclude linux,systemd
14. reboot -> ok
15. tdnf update
16. reboot -> does not work

Expected behavior

tdnf update should update packages and the system's networking should continue to work

Additional context

No response

Reproduce the failure on a Raspberry Pi 4B running the cited Photon OS 5.0 image, following the tdnf update and reboot sequence with the linux and systemd exclusions. Compare the working excluded-update state with the failing full update and verify DHCP, static networking, and packet behavior after reboot. Done means networking remains functional after tdnf update without exclusions.