#1129767 debconf: success exit status on dpkg-reconfigure failure

Package:
debconf
Source:
debconf
Submitter:
Ernesto Alfonso
Date:
2026-03-06 18:55:01 UTC
Severity:
normal
Tags:
#1129767#5
Date:
2026-03-05 22:51:57 UTC
From:
To:
Dear Maintainer,

Running dpkg-reconfigure can fail with a zero or success exit status. This prevents scripts
that expect a certain reconfiguration from knowing that it failed.

    █[hp11][dotfiles][0]$ sudo DEBIAN_FRONTEND=noninteractive dpkg-reconfigure openafs-client
    Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
    █[hp11][dotfiles][0]$ echo $?
    0
    █[hp11][dotfiles][0]$


Ernesto

#1129767#10
Date:
2026-03-06 10:31:23 UTC
From:
To:
Control: reassign -1 openafs-client

dpkg-reconfigure just passes through the exit code of the maintainer
scripts it's executing.  If openafs-client is inappropriately exiting
non-zero (I haven't done the analysis to work out if it's really
inappropriate in this particular case), then that's a problem in that
package, or in whatever it's calling.

#1129767#19
Date:
2026-03-06 16:48:00 UTC
From:
To:
tags 1129767 moreinfo
thanks

Hi Ernesto,

Can you say a bit more about how you triggered this scenario?
Also the `systemctl status openafs-client` output would be helpful.

The openafs-client maintainers scripts are using debhelper for the systemd
interactions (and use `set -e`) so it's not immediately obvious what might
be failing.

I'm also not seeing a great way to get deb-systemd-invoke to tell us what
the actual failed command was -- Colin, do you have any tips there?

Thanks,

Ben

#1129767#26
Date:
2026-03-06 18:51:54 UTC
From:
To:
I don't have access to the machine with the logs right now, but the problem
was that the openafs-client was refusing to start because the cache size
exceeded 95% of the root partition size -- I had hard-coded a certain cache
size, which was too big for a chromebook with only around 13GB of space.

I tried to correct the cache size programmatically the same way I specified
the initial valuie,  by using debconf-set-selections, followed by
dpkg-reconfigure openafs-client. But it appears that the dpkg-reconfigure
refused to take the new value, and reverted the cache value as seen by
debconf-get-selections, and the openafs-client continued to complain about
the cache size. The logs for these commands were attached in my original
report.

In the end I resolved it by omitting the non-interactive flag to
dpkg-reconfigure and going through all the prompts manually, providing the
correct cache size manually.

Ernesto