https://github.com/QubesOS/qubes-issues/issues/3557
Related to:
https://github.com/QubesOS/qubes-issues/issues/3135
Root cause:
When changing TO fedora-26, the qubes-updates-proxy service fails to start on boot. A manual start of the service fixes the issue. A reboot seems needed to have it start on boot. Not a problem since sys-net changing templates is rare. I just didn't assume a reboot or manual service start would be needed.
No problem going FROM fedora-26 to another template, as the service starts properly on first run.
Solution:
running 'systemctl restart qubes-updates-proxy' in sys-net