[qubes-users] dependency problem after upgrading standalone debian 11 VM

qboser · April 12, 2023, 10:13pm

Hello!

a while ago when migrating Qubes 4.0 to Qubes 4.1
I restored a standalone debian VM (created on r4.0) on a fresh r4.1 system and did not
notice that I also should replace the r4.0 repos _in_ the VM to r4.1 repos
but it still worked fine.

Today I replaced this line:
deb [arch=amd64] Index of /r4.0/vm/ bullseye main

with this:
deb [arch=amd64] Index of /r4.1/vm/ bullseye main

in the standalone VM.

After an
apt update
apt upgrade
apt dist-upgrade

I'm running into this error:

The following additional packages will be installed:
   xen-utils-guest
The following NEW packages will be installed:
   xen-utils-guest
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
36 not fully installed or removed.
Need to get 0 B/30.1 kB of archives.
After this operation, 53.2 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 242630 files and directories currently installed.)
Preparing to unpack .../xen-utils-guest_4.14.5-20+deb11u1_amd64.deb ...
Unpacking xen-utils-guest (4.14.5-20+deb11u1) ...
dpkg: error processing archive /var/cache/apt/archives/xen-utils-guest_4.14.5-20+deb11u1_amd64.deb (--unpack):
  trying to overwrite '/lib/systemd/system/xendriverdomain.service', which is also in package xen-utils-common 2001:4.8.5-42+deb11u1
Errors were encountered while processing:
  /var/cache/apt/archives/xen-utils-guest_4.14.5-20+deb11u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Do you have any recommendation on how to solve this issue?

thanks!

qboser · April 12, 2023, 11:04pm

Do you have any recommendation on how to solve this issue?

I also tried:

github.com

QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72


      
          elif [ -e /etc/debian_version ]; then
              releasever="$(awk -F'.' '{print $1}' /etc/debian_version)"
              # Check Debian supported release
              if [ "$releasever" -lt 10 ]; then
                  exit 2
              fi
              # Backup R4.0 repository file
              cp /etc/apt/sources.list.d/qubes-r4.list /etc/apt/sources.list.d/qubes-r4.list.bak
              # We don't have $releasever into so manually replace it
              sed -i 's/r4.0/r4.1/g' /etc/apt/sources.list.d/qubes-r4.list
              # Ensure APT cache is cleaned
              apt-get clean
              apt-get update
              # "downgrade" to package without epoch
              if ! apt-get install --allow-downgrades -y \
                      'xen-utils-common=4.14*' \
                      'libxenstore3.0=4.14*' \
                      'xenstore-utils=4.14*'; then
                  exit 3
              fi

This file has been truncated. show original

found via:

github.com/QubesOS/qubes-issues

Debian 11 template upgrade problem, all guests broken

opened 07:26PM - 05 Nov 22 UTC

closed 06:35AM - 02 Apr 23 UTC

gangamstyle

T: bug R: not applicable C: Debian/Ubuntu P: default diagnosed C: updates

### Qubes OS release 4.1 ### Brief summary For a long time I used debian-11… template which worked fine. Today I tried to upgrade this template using Qubes upgrade tool and upgrade failed. After upgrade using "apt" I discovered that this happened because qubes tor repository now lacks r4.0 files (http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.0/vm) And I had this link in my /etc/apt/sources.list.d/qubes-r4.list , with r4.0 and not r4.1 in URL. To fix this problem I have changed repository link like this: http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.1/vm After that I restarted upgrade process using Qubes upgrade toot, upgrade failed without description. After this error template became unresponsive and unbootable. All template based guest vm's failed to boot. This part of the problem was fixed by removing this broken template and reinstalling Debian 11 template. But I also have standalone OS based on that template which I can't fix so simple and if fails to upgrade too. This is "apt upgrade" error: ``` .... Processing triggers for qubes-core-agent (4.0.65-1+deb11u1) ... /usr/lib/qubes/qrexec-client-vm: error while loading shared libraries: libqrexec-utils.so.2: cannot open shared object file: No such file or directory qrexec-client-vm: error while loading shared libraries: libqrexec-utils.so.2: cannot open shared object file: No such file or directory Traceback (most recent call last): File "/usr/bin/qvm-features-request", line 88, in <module> sys.exit(main()) File "/usr/bin/qvm-features-request", line 83, in main subprocess.check_call( File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['qrexec-client-vm', 'dom0', 'qubes.FeaturesRequest']' returned non-zero exit status 127. ............ ........... Setting up qubes-vm-dependencies (4.1.20-1+deb11u1) ... /usr/lib/qubes/qrexec-client-vm: error while loading shared libraries: libqrexec-utils.so.2: cannot open shared object file: No such file or directory ``` I tried: apt install --reinstall qubes-core-agent qubes-vm-dependencies but it fails too: ``` Unpacking xen-utils-guest (4.14.5-10+deb11u1) ... dpkg: error processing archive /tmp/apt-dpkg-install-1234/2-xen-utils-guest_4.14.5-10+deb11u1_amd64.deb (--unpack): trying to overwrite '/lib/systemd/system/xendriverdomain.service', which is also in package xen-utils-common 2001:4.8.5-42+deb11u1 ``` ... and after this standalone VM becomes broken and fails to boot.

but running:
apt-get install --allow-downgrades -y \
             'xen-utils-common=4.14*' \
             'libxenstore3.0=4.14*' \
             'xenstore-utils=4.14*'

fails because I did run
'apt upgrade; apt dist-upgrade'
already:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'xen-utils-common'
Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'libxenstore3.0'
Selected version '4.14.5+94-ge49571868d-1' (Debian-Security:11/stable-security [amd64]) for 'xenstore-utils'
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
qubes-core-agent : Depends: xen-utils-guest but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
exit

Is there a way out?

unman · April 14, 2023, 12:57pm

Exactly this issue arose on GitHub - it is, as you say, because you did
not update the qubes repository definition in timely way.
You can read the issue [here](Debian 11 template upgrade problem, all guests broken · Issue #7865 · QubesOS/qubes-issues · GitHub)

The resolution is to follow the steps in the upgrade script - courtesy
of Marek:

The source of the problem is that in R4.1 we actually stopped shipping own duplicated xen packages, and are relying on those from official Debian repositories. But the upgrade path requires manual step because of that.
The in-place R4.0 -> R4.1 upgrade tool handle that automatically, but in case of manual upgrade, see this part:
https://github.com/QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72

qboser · April 14, 2023, 2:10pm

Hi uman,

thanks for your reply.

'unman' via qubes-users:

Exactly this issue arose on GitHub - it is, as you say, because you did
not update the qubes repository definition in timely way.
You can read the issue [here](Debian 11 template upgrade problem, all guests broken · Issue #7865 · QubesOS/qubes-issues · GitHub)

The resolution is to follow the steps in the upgrade script - courtesy
of Marek:

The source of the problem is that in R4.1 we actually stopped shipping own duplicated xen packages, and are relying on those from official Debian repositories. But the upgrade path requires manual step because of that.
The in-place R4.0 -> R4.1 upgrade tool handle that automatically, but in case of manual upgrade, see this part:
https://github.com/QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72

Yes I know about this github ticket, I mentioned in my last email, but
I have the impression that these step can not be used _after_
running 'apt update; apt upgrade; apt dist-upgrade' anymore - which is the situation I'm in.

Is there also a way to recover a system after the 'apt upgrade' step happened already?

unman · April 14, 2023, 3:11pm

I'd probably be rolling back most of your recent changes, and starting
again, after making sure that I have a decent backup of the qube in its
current state.
You need to roll back those packages, and -f should work for the
install. I have some old templates hanging about - if you can wait until
tomorrow I'll pull one and work through the process in the morning.

qboser · April 14, 2023, 5:14pm

Hi unman,

I'd probably be rolling back most of your recent changes, and starting
again, after making sure that I have a decent backup of the qube in its
current state.
You need to roll back those packages, and -f should work for the
install. I have some old templates hanging about - if you can wait until
tomorrow I'll pull one and work through the process in the morning.

thanks that is very kind, I'll wait until tomorrow then.

thank you!

qboser · April 15, 2023, 8:14am

When creating a backup while the broken VM was still
running I noticed the text saying that the VM backup will contain
the VM's state before it booted, which was a perfect solution to revert
everything I did since the VM started.

This should solve my problem by restoring that newly created backup.

thank you anyway for your help!