[Pkg-puppet-devel] Bug#992800: puppet agent breaks after upgrade to bullseye on arm architecture

[stoeni]

Package: puppet
Version: 5.5.22-2
Severity: normal
X-Debbugs-Cc: none

After upgrading some Raspberry Pi (Zero, Model3/4) from buster to 
bullseye, the puppet client no longer works on this architecture.

Steps to reproduce this error:

- install rasbian buster on a Raspberry Pi
- upgrade to bullseye
- run e.g. "puppet agent"

running puppet without arguments works:

------------------<8------------------
root at moon:~# puppet
See 'puppet help' for help on available puppet subcommands
------------------>8------------------

running puppet with arguments aborts:

------------------<8------------------
root at moon:~# puppet help
Aborted
------------------>8------------------

puppet 5.5.10 runs well on buster with amd64 or arm architecture, 5.5.22 
runs on bullseye and amd64, not on arm.

as there are no log entries or any usable output how can i help to track 
this thing down? maybe its ruby related?

would some strace output help?


-- System Information:
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye
Architecture: armv7l

Kernel: Linux 5.10.52-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages puppet depends on:
ii  adduser              3.118
ii  facter               3.14.12-1+b1
ii  hiera                3.2.0-2.1
ii  init-system-helpers  1.60
ii  lsb-base             11.1.0+rpi1
ii  ruby                 1:2.7+2
ii  ruby-augeas          1:0.5.0-3+b4
ii  ruby-deep-merge      1.1.1-1
ii  ruby-shadow          2.5.0-1+b1

Versions of packages puppet recommends:
ii  debconf-utils  1.5.77
ii  lsb-release    11.1.0+rpi1
ii  ruby-selinux   3.1-3

Versions of packages puppet suggests:
pn  ruby-hocon  <none>
pn  ruby-rrd    <none>

-- no debconf information
Thank you for using reportbug


-- 
cheers,
stoeni

* yes, we scan ! *