Your message dated Fri, 9 Jun 2023 15:56:44 +0530
with message-id 
<capp0f977igldwlkazdcw_-gvjmz1dfka8runcnowx6lu1hf...@mail.gmail.com>
and subject line Re: Bug#1037178: puppet does not sync files anymore after 
recent ruby2.5 security upload
has caused the Debian Bug report #1037178,
regarding puppet does not sync files anymore after recent ruby2.5 security 
upload
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libruby2.5
Version: 2.5.5-3+deb10u5
Severity: grave

Hi,

I can't quite figure out why, but the latest security upload of ruby2.5 in
Buster breaks the ability of the puppet agent to pull files from the master

With 2.5.5-3+deb10u4:
# puppet agent --onetime --server puppet-kom.srv.lrz.de  --test  --no-daemonize
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Info: Caching catalog for simrad3.slb.lrz.de
Info: Applying configuration version 'master-70189ef6ab5a'


# apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libruby2.5 ruby2.5
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3841 kB of archives.
After this operation, 2048 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://debian.mirror.lrz.de/debian-security buster/updates/main amd64 
libruby2.5 amd64 2.5.5-3+deb10u5 [3440 kB]
Get:2 http://debian.mirror.lrz.de/debian-security buster/updates/main amd64 
ruby2.5 amd64 2.5.5-3+deb10u5 [401 kB]
Fetched 3841 kB in 0s (30.3 MB/s)
Reading changelogs... Done
(Reading database ... 58907 files and directories currently installed.)
Preparing to unpack .../libruby2.5_2.5.5-3+deb10u5_amd64.deb ...
Unpacking libruby2.5:amd64 (2.5.5-3+deb10u5) over (2.5.5-3+deb10u4) ...
Preparing to unpack .../ruby2.5_2.5.5-3+deb10u5_amd64.deb ...
Unpacking ruby2.5 (2.5.5-3+deb10u5) over (2.5.5-3+deb10u4) ...
Setting up libruby2.5:amd64 (2.5.5-3+deb10u5) ...
Setting up ruby2.5 (2.5.5-3+deb10u5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+deb10u2) ...

# puppet agent --onetime --server puppet-kom.srv.lrz.de  --test  --no-daemonize
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources 
using 'eval_generate': Failed to open TCP connection to :8140 (Connection 
refused - connect(2) for "" port 8140)
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve 
file metadata for puppet:///pluginfacts: Failed to open TCP connection to :8140 
(Connection refused - connect(2) for "" port 8140)
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': Failed to open TCP connection to :8140 (Connection 
refused - connect(2) for "" port 8140)
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file 
metadata for puppet:///plugins: Failed to open TCP connection to :8140 
(Connection refused - connect(2) for "" port 8140)
Info: Retrieving locales
Error: /File[/var/lib/puppet/locales]: Failed to generate additional resources 
using 'eval_generate': Failed to open TCP connection to :8140 (Connection 
refused - connect(2) for "" port 8140)
Error: /File[/var/lib/puppet/locales]: Could not evaluate: Could not retrieve 
file metadata for puppet:///locales: Failed to open TCP connection to :8140 
(Connection refused - connect(2) for "" port 8140)
Info: Loading facts
Info: Caching catalog for simrad3.slb.lrz.de
Info: Applying configuration version 'master-70189ef6ab5a'
Error: 
/Stage[main]/Lrz_kom_radius::Radiussimrad/File[/etc/freeradius/.git/hooks/post-commit]:
 Could not evaluate: Could not retrieve file metadata for 
puppet:///modules/lrz_kom/classes/radius/git_post-commit_hook: Failed to open 
TCP connection to :8140 (Connection refused - connect(2) for "" port 8140)
Error: 
/Stage[main]/Lrz_common::Distributions::Debian::Vim/File[/etc/vim/vimrc.lrz-puppet]:
 Could not evaluate: Could not retrieve file metadata for 
puppet:///modules/lrz_common/vimrc.lrz-puppet: Failed to open TCP connection to 
:8140 (Connection refused - connect(2) for "" port 8140)
Error: 
/Stage[main]/Lrz_common::Distributions::Debian::Emacs/File[//etc/emacs/site-start.d/99lrz.el]:
 Could not evaluate: Could not retrieve file metadata for 
puppet:///modules/lrz_common/emacs/99lrz.el: Failed to open TCP connection to 
:8140 (Connection refused - connect(2) for "" port 8140)
Error: 
/Stage[main]/Lrz_common::Distributions::Debian/File[/etc/apt/trusted.gpg.d/debian-lrz.asc]:
 Could not evaluate: Could not retrieve file metadata for 
puppet:///modules/lrz_common/debian/debian-lrz.asc: Failed to open TCP 
connection to :8140 (Connection refused - connect(2) for "" port 8140)
Error: /Stage[main]/Puppetclient::Config/File[/usr/bin/waitrandom]: Could not 
evaluate: Could not retrieve file metadata for 
puppet:///modules/puppetclient/waitrandom: Failed to open TCP connection to 
:8140 (Connection refused - connect(2) for "" port 8140)
Notice: Applied catalog in 1.82 seconds

Note the empty servername in the "Failed to open TCP connection" messages.

Bernhard

--- End Message ---
--- Begin Message ---
Hello,

On Fri, Jun 9, 2023 at 12:23 PM Schmidt, Bernhard
<bernhard.schm...@lrz.de> wrote:
> Any news here?

The regression fix along with the fix for the two CVEs have been
rolled out via DLA 3450-1.


- u

--- End Message ---

Reply via email to