4.1 in dom0, 4.2 in sys-firewall

General Discussion
1

In dom0:
cat /etc/os-release gives version 4.1
Running command ```
cat /etc/yum.repos.d/qubes-r4.repo

and in sys-firewall"cat /etc/os-release
NAME="Fedora Linux"
VERSION="39 (Thirty Nine)"  and 
cat /etc/yum.repos.d/qubes-r4.repo   gives 
"[qubes-vm-r**4.2**-current]
name = Qubes OS Repository for VM (updates)
baseurl = https://yum.qubes-os.org/r4.2/current/vm/fc$releasever"
So it seems I have both 4.1 and 4.2 in different locations???
2

Can you check what you have inside that file in dom0:

cat /etc/yum.repos.d/qubes-dom0.repo

Have you performed an in-place upgrade?

3

Tried to many times, but it always fails at one step or another -
never clears all five steps.

4

Where does it fail and what are the errors?

5

Hereā€™s some I posted in Update issus Qubes 4.1 NOT using apt-cacher - #7 by cordial

qubes-dist-upgrade just goes to root@dom0

qubes-dist-upgrade --update ends after step 1 and goes to root@dom0

qubes-dist-upgrade -k ā†’ root@dom0

qubes-dist-upgrade -k --all-pre-reboot -y --keep-running sys-firewall ->6 templates OK then back to root@dom0

qubes-dist-upgrade --all-pre-reboot -y --keep-running sys-firewall ā†’ gives the error
qubes-dom0-update -y qubes-dist-upgrade ā†’ gives the error

There were several other variations that I canā€™t recall. They all seem to either end in the user prompt, give the error, or
stop after step one. One of the attempts skipped the first 4 steps, went straight to step 5 clean up but the upgrade
did not occur. Never saw steps 2,3, or 4.
Once I got ""Errors during downloading metadata for repository ā€˜3isec -dom0-Currintā€™ -Status Code 404
Cannot download repodata/repomd.xml All mirrors tried. ā€œā€

6

What happens when you run this?

sudo qubes-dist-upgrade --release-upgrade --dist-upgrade
7

It goes straight to Stage 2, then the sys-firewall pops up with 8 lines ending with ""Fetching updates failed wity code 1; Press Enter to exit ā€œā€

8

Are you able to ping an external IP from sys-firewall?

9

ping 8.8.8.8 gives
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of date
then just a blinking cursor, nothing else

10

what if you make a NetVM qube and use sys-net to it? If it works, you could replace sys-firewall by this one?

11

ping in sys-net gives same result

12

Can you check in sys-net if you have been assigned an IP from your internal network?

ip a
13

There are 4 items listed:
1)lo: <LOOPBACKā€¦
2)ens6: NO-CARRIERā€¦
3)wls7: <BROADCASTā€¦
4)vif5.0:<BROADCASTā€¦
whole lotta numbers and letters after each

as an aside: it also says 4.2 in sys-net as well.

14

What do you get when you run ip r ?

Also, can you check this service logs:

sudo journalctl -u qubes-iptables -b
15

[user@sys-firewall ~]$ ip r
default via 10.137.0.5 dev eth0 onlink
10.137.0.5 dev eth0 scope link
10.137.0.16 dev vif16.0 scope link metric 32736

[user@sys-net ~]$ ip r
default via 192.168.1.1 dev wls7 proto dhcp src 192.168.1.181 metric 600
10.137.0.6 dev vif5.0 scope link metric 32747
192.168.1.0/24 dev wls7 proto kernel scope link src 192.168.1.181 metric 600

16

Can you ping your gateway (192.168.1.1)?

17

[user@sys-firewall ~]$ ip r
default via 10.137.0.5 dev eth0 onlink
10.137.0.5 dev eth0 scope link
10.137.0.16 dev vif16.0 scope link metric 32736
[user@sys-firewall ~]$ sudo journalctl -u qubes-iptables -b
Jan 16 10:48:35 sys-firewall systemd[1]: Starting qubes-iptables.service - Qube>
Jan 16 10:48:35 sys-firewall qubes-iptables[525]: nft: Applying firewall rules:>
Jan 16 10:48:35 sys-firewall qubes-iptables[525]: nft: Applying firewall rules:>
Jan 16 10:48:35 sys-firewall systemd[1]: Finished qubes-iptables.service - Qube>

18

Can you use your arrow keys to make sure you have ā€œOKā€ and not ā€œFAILEDā€ after these lines?

19

[user@sys-firewall ~]$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=1.85 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=1.73 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=63 time=1.75 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=63 time=2.63 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=63 time=1.62 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=63 time=1.70 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=63 time=4.33 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=63 time=1.62 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=63 time=1.58 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=63 time=1.80 ms
and it just keeps going on and onā€¦

20

[user@sys-net ~]$ sudo journalctl -u qubes-iptables -b
Jan 16 10:48:26 sys-net systemd[1]: Starting qubes-iptables.service - Qubes base firewall settings.>
Jan 16 10:48:27 sys-net qubes-iptables[553]: nft: Applying firewall rules: OK
Jan 16 10:48:27 sys-net qubes-iptables[553]: nft: Applying firewall rules: OK
Jan 16 10:48:27 sys-net systemd[1]: Finished qubes-iptables.service - Qubes base firewall settings.

user@sys-firewall ~]$ sudo journalctl -u qubes-iptables -b
Jan 16 10:48:35 sys-firewall systemd[1]: Starting qubes-iptables.service - Qubes base firewall settingsā€¦
Jan 16 10:48:35 sys-firewall qubes-iptables[525]: nft: Applying firewall rules: OK
Jan 16 10:48:35 sys-firewall qubes-iptables[525]: nft: Applying firewall rules: OK
Jan 16 10:48:35 sys-firewall systemd[1]: Finished qubes-iptables.service - Qubes base firewall settings.