Lost internet on all VMs after updating from testing repos

[Simon-Davies]

Qubes OS version:

Qubes 4.0 - Latest version of qubes from testing repos

Affected component(s):

All VMs

---

Steps to reproduce the behavior:

Connect to Wi-Fi and browse internet with Firefox

Expected behavior:

I have internet connectivity

Actual behavior:

I have no Internet connectivity. I can't even ping google - www.google.com or 8.8.8.8

General notes:

---

Related issues:

[tasket]

See issue #3939 which might be the same.

Are you using Fedora 27 or 28? Check the status of qubes-iptables.service on your proxyVMs (sys-firewall) and sys-net: sudo service qubes-iptables status

[tasket]

See issue #3939 which might be the same.

Are you using Fedora 27 or 28? Check the status of qubes-iptables.service on your proxyVMs (sys-firewall) and sys-net: sudo service qubes-iptables status

[andrewdavidwong]

Can you provide the list of packages that were updated with version numbers?

[andrewdavidwong]

Can you provide the list of packages that were updated with version numbers?

[Simon-Davies]

I didn't make a note of which packages were upgraded, sorry mate.

[Simon-Davies]

I didn't make a note of which packages were upgraded, sorry mate.

[andrewdavidwong]

It's probably still avaliable using sudo dnf history, then sudo dnf history info X, where X is the number in the history list corresponding to the transaction that seems to have caused the problem.

[andrewdavidwong]

It's probably still avaliable using sudo dnf history, then sudo dnf history info X, where X is the number in the history list corresponding to the transaction that seems to have caused the problem.

[marmarek]

It's definitely QubesOS/updates-status#550. It fixes Fedora 28, but at the same time breaks Fedora 26.

[marmarek]

It's definitely QubesOS/updates-status#550. It fixes Fedora 28, but at the same time breaks Fedora 26.

[Simon-Davies]

I'm using fedora-26 templates so this sounds right @marmarek

The question is how do I fix this without flashing a clean ISO of Qubes OS.

How can I update with no Internet connectivity? Is there a way of temporarily removing all iptable rules so I can upgrade my fedora-26 templates to fedora-28?

[Simon-Davies]

I'm using fedora-26 templates so this sounds right @marmarek

The question is how do I fix this without flashing a clean ISO of Qubes OS.

How can I update with no Internet connectivity? Is there a way of temporarily removing all iptable rules so I can upgrade my fedora-26 templates to fedora-28?

[marmarek]

dnf in the template should still work, you can downgrade qubes-core-agent* to previous version (dnf downgrade ...).

[marmarek]

dnf in the template should still work, you can downgrade qubes-core-agent* to previous version (dnf downgrade ...).

[Simon-Davies]

I ran the below in the fedora-26 template:

sudo dnf downgrade qubes-core-agent*

I get:

Error: Failed to synchronize cache for repo 'updates'

Edit: I just tried installing the last version of every qubes-core-agent* package manually by downloading them from the repo and running dnf downgrade path/to/.rpm --disablerepo=*

I still have No internet connectivity :/

[Simon-Davies]

I ran the below in the fedora-26 template:

sudo dnf downgrade qubes-core-agent*

I get:

Error: Failed to synchronize cache for repo 'updates'

Edit: I just tried installing the last version of every qubes-core-agent* package manually by downloading them from the repo and running dnf downgrade path/to/.rpm --disablerepo=*

I still have No internet connectivity :/

[RefinedSoftwareLLC]

I was able to fix an "Error: Failed to synchronize cache for repo 'updates'" error by using "sudo qubes-dom0-update --clean". Can anyone else tell us if that is safe to try as a fix?

[RefinedSoftwareLLC]

I was able to fix an "Error: Failed to synchronize cache for repo 'updates'" error by using "sudo qubes-dom0-update --clean". Can anyone else tell us if that is safe to try as a fix?

[jimtahu]

I ran into this issue as well (qubes-iptables was failing with error messages about the firewall rules), was able to "fix" by reverting my template (fedora-27) root volume

[jimtahu]

I ran into this issue as well (qubes-iptables was failing with error messages about the firewall rules), was able to "fix" by reverting my template (fedora-27) root volume

[Simon-Davies]

When you say by reverting what do you mean by this? I tried downgrading all the qubes-core-agent* packages in the fedora-26 VM to the last version but it's still broken for me.

I'm thinking of wiping the system and starting fresh as it's really annoying having no internet.

[Simon-Davies]

When you say by reverting what do you mean by this? I tried downgrading all the qubes-core-agent* packages in the fedora-26 VM to the last version but it's still broken for me.

I'm thinking of wiping the system and starting fresh as it's really annoying having no internet.

[jimtahu]

qvm-volume has an option to revert a volume.

For me, this meant doing this in dom0:
qvm-volume list fc27 (see volumes, including fc27:root)
qvm-volume info fc27:root (see that fc27:root has a previous versions, named something like number-bak)
qvm-volume revert –verbose fc27:root number-bak

After restarting sys-net and sys-firewall (based on fc27), networking resumed working.

[jimtahu]

qvm-volume has an option to revert a volume.

For me, this meant doing this in dom0:
qvm-volume list fc27 (see volumes, including fc27:root)
qvm-volume info fc27:root (see that fc27:root has a previous versions, named something like number-bak)
qvm-volume revert –verbose fc27:root number-bak

After restarting sys-net and sys-firewall (based on fc27), networking resumed working.