tags 935268 unreproducible
thanks
On Wed, 21 Aug 2019, David Venhoek wrote:
Hi,
> On a fresh debian 9 opencloud image system, after running apt update and apt
> upgrade, trying to install ferm with
> ``/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o
> "Dpkg::Options::=--force-confold" install ferm | tee /dev/null``
> results in the ferm service failing during the execution of the apt-get
> command.
>
> This results in ferm not being properly installable using tools like ansible.
Despite of installing ferm via ansible all the time I am not able to
reproduce your problem in a test environment:
DEBIAN_FRONTEND="noninteractive" /usr/bin/apt-get -y -o
"Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" install
ferm | tee /dev/null
The following NEW packages will be installed:
ferm
Preconfiguring packages ...
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0
B/112 kB of archives.
After this operation, 309 kB of additional disk space will be
used.
Selecting
previously unselected package ferm.
(Reading database ... 326357 files and directories currently installed.)
Preparing to unpack .../archives/ferm_2.4-1_all.deb ...
Unpacking ferm (2.4-1) ...
Setting up ferm (2.4-1) ...
Created symlink /etc/systemd/system/sysinit.target.wants/ferm.service →
/lib/systemd/system/ferm.service.
Processing triggers for man-db (2.9.0-2) ...
Processing triggers for systemd (244-3) ...
root@lisa:~#
gives me a clean installation.
Installation via ansible works fine:
-m apt -a "pkg=ferm state=present" localhost
localhost | CHANGED => {
"cache_update_time": 1578131047,
"cache_updated": false,
"changed": true,
"stderr": "",
"stderr_lines": [],
*snip*
"Preparing to unpack .../archives/ferm_2.4-1_all.deb ...",
"Unpacking ferm (2.4-1) ...",
"Setting up ferm (2.4-1) ...",
"Created symlink /etc/systemd/system/sysinit.target.wants/ferm.service
-> /lib/systemd/system/ferm.service.",
"Processing triggers for man-db (2.9.0-2) ...",
"Processing triggers for systemd (244-3) ..."
]
}
I therefore need information on how to reproduce the problem in a clean test
environment.
Thanks
Alex
