lint/syntax/unit tests are failinig with "uninitialized constant Concurrent::RubyThreadLocalVar"

Bug #2003761 reported by Takashi Kajinami
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
puppet-openstack-spec-helper
New
Critical
Takashi Kajinami

Bug Description

concurrent-ruby 1.2.0[1] was just released.
It seems the version dropped RubyThreadLocalVar which is still used by puppet[2].

We have to pin the library until the fixed version of puppet is released.
Note that for stable branches we should keep that pin because we continue using the old version for some tests (eg unit tests).

[1] https://rubygems.org/gems/concurrent-ruby/versions/1.2.0
[2] https://github.com/ruby-concurrency/concurrent-ruby/issues/986

Changed in puppet-openstack-spec-helper:
importance: Undecided → Critical
assignee: nobody → Takashi Kajinami (kajinamit)
description: updated
Revision history for this message
Hadmut Danisch (hadmut) wrote :

Problem still exists in 23.04 with puppet-agent 7.23.0-1

There's a bug ticket at

https://tickets.puppetlabs.com/browse/PUP-11722

which says it was solved in 7.22 and 7.23, which does not seem to be the case.

However, I've noticed that puppet-agent was running well an a fresh Ubuntu 23.04 system. Then the bug occured after the first run installing lots of programs and libraries.

So I guess ther is some particular package causing that problem.

Revision history for this message
Hadmut Danisch (hadmut) wrote :

Found it.

one of the ruby gems I am installing in my puppet manifests is 'grape'. After installing grape, puppet again shows that error about RubyThreadLocalVar, because it somehow breaks the system, porobably by pulling in concurrent-ruby-1.2.2.

So even if it works with a fresh Ubuntu 23.04 install, installing ruby gems can break it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.