patches welcome :slightly_smiling_face:
# puppet-enterprise
b
patches welcome šŸ™‚
s
@steveax which version of
hiera-eyaml
went out with 2025.11.2? I suspect decryption is the actual problem as
eyaml createkeys
and
eyaml encrypt
are commonly run under CRuby.
Older versions of the
hiera-eyaml
gem did load the x509 certificate during
decrypt
.
So, that's the most logical place for BouncyCastle validation to be blowing up.
s
while we ship hiera-eyaml in the runtime, it's the puppetserver user installed module that's failing here
s
Hmmm, that doesn't match the failure case I saw - decrypt seemed fine,
3.4.0
is what ships in the runtime on
2025.11.2
but that wasn't in play in my testing. Would be great if you could give that PR a poking at
s
Yeah. I'm looking at it. Empty issuer is a problem, but I want to make sure we're solving the actual cause of the failures --- because running
eyaml createkeys
under JRuby is just odd. I don't think the
eyaml
bin stub is even set up to execute under
puppetsever ruby
--- unless PE is doing something different in
puppet-runtime
.
s
I tested pretty hard in a PE install, but less so in a standalone puppetserver
admittedly, this is not my strongest wheelhouse either, so happy to get more šŸ‘€ on it
s
A stack trace from the user operation that is failing would help.
b
did the user just do a
lookup()
of a eyaml value or something else?
s
this is from my repo:
s
Exactly. If it's
lookup()
, then we're likely chasing a red herring in regard to
Issuer:
s
That wasn't confirmed to match @vchepkov’s failure though.
s
true
b
do they have some magic to check if keys exist and if not, call a function to create them?
s
should we move this conversation to the PR?
s
Ah. A custom function that called directly into
hiera-eyaml
as a library would make sense.
b
yeah
well "sense" is a strong word
s
šŸ˜‰
b
if it would be an exec resource or type/provider, it would just work šŸ˜„
ā˜ļø 1
I rebased my jruby10 branch against yours: https://github.com/voxpupuli/hiera-eyaml/pull/428
šŸ‘ 1
v
In the middle of the upgrade peadm failed, because puppetserver wasn't able decrypt/compile catalog I patched my fork of peadm here https://github.com/vchepkov/puppetlabs-peadm/commit/f2c3aa50f679eac48127056c4aad9500865cea4a
s
Ok, so that is a failure in
decrypt
and not
create_keys
.
v
yep
s
Which should be fixed starting with
hiera-eyaml
4.1.0
v
traveling, will check after vacation:)
b
I give you bonus points for creative solution
v
It's a hack and I know it :)
btw, my AL2023 fix is still not merged ā˜¹ļø
šŸ‘€ 2
s
on the decrypt side,
puppetserver gem install hiera-eyaml -v 5.0.1
should take care of that I think?
s
Should do. That's what OpenVox Server is shipping with, and I wasn't able to re-produce a decrypt failure.
catjam 1