This message was deleted.
# puppet-enterprises
Slackbot
11/17/2022, 1:28 PMThis message was deleted.
r
Robert FD
11/17/2022, 2:11 PMWe created a zendesk ticket with the number
50290d
David Sandilands
11/18/2022, 10:46 AM@Robert FD I think this is in hand with the support case but just in case anyone else searches this message to give a relevant point from the case.
Taking a look at the error in particular, it seems to be coming from snakeyaml:
https://bitbucket.org/snakeyaml/snakeyaml/commits/72dfa9f1074abe2b8a6c8776bee4476b0aed02e3
This is a yaml parser used in PE and the version has been updated.
It appears not to be handling larger YAML files as the previous version did and is being investigated by support and product
r
Robert FD
11/18/2022, 1:10 PMI appreciate that you are circling around to this even within the community site, @David Sandilands. Having multiple ways for people to find a similar issue AND possible solution is helpful to the customer AND the vendor! I know one of us will do a final circle back when resolved. Kudos!!
Also, great avatar pic!! 😁
highfive2 1
d
David Sandilands
11/22/2022, 9:42 AMhttps://tickets.puppetlabs.com/browse/SERVER-3228 is the publically visible ticket related to this. I will set a weekly reminder and come back to confirm a version fix when it happens
👍 1
r
Robert FD
11/28/2022, 2:07 PMI believe Puppet Enterprise LTS was NOT released under 7.9.1, correct? We are in the overlap version 6.x family.
d
David Sandilands
11/28/2022, 2:30 PM@Robert FD PE LTS is 2021.7.1 (LTS) 7.20.0
https://puppet.com/docs/pe/2021.7/component_versions_in_recent_pe_releases.html#component_versions_in_recent_pe_releases
r
Robert FD
11/28/2022, 2:33 PMYep, that was what I thought. Okay, Again my thanks for the updates!!
d
David Sandilands
02/03/2023, 9:51 AMI am still monitoring this and I will chase when I get back from leave as I know others have hit this when doing upgrades
r
Robert FD
02/03/2023, 1:08 PMThanks for keeping an eye on it. We have an official ticket in as well and working through that. I can DM you that ticket if you want. Just let me know
d
David Sandilands
02/03/2023, 1:11 PMThat would be great thanks
David Sandilands
03/14/2023, 11:34 PM@Robert FD the ticket has now moved to our public jira https://puppet.atlassian.net/browse/SERVER-3228
and I am unable to update it due to some transisition permissions issues but I did get the following response
"The limit of 3 million codepoints is quite large and we find users who surpass that either have files that are unwieldy and should instead be integrated with a DB (eg hiera_vault), or are inserting large values that should instead be handled by a file resource. We recommend users do not surpass the limit instituted by SnakeYAML..
However, JRuby will support configuring SnakeYAML limits in 9.4. Because JRuby 9.4 implements Ruby 3.1 we will be shipping it in Puppet Platform 8/Puppet Server 8. If they backport the configuration to JRuby 9.3 then we will also take it up in Puppet Server 7. Configuring JRuby to adjust the SnakeYAML limit will be possible via JAVA_ARGS in the defaults file.
Depending on user demand we may look into providing a way via Puppet Server's config to configure the limits once JRuby supports doing so, but that would be quite a ways out. "
David Sandilands
03/15/2023, 10:07 AMHaving found the public cloud jira is locked into read only I have updated the private jira which should update with this
David Sandilands
03/15/2023, 10:08 AMI will stop tracking this now as it seems this ticket has an answer to approach for now, let me know if there's anything else needed or representation required
r
Robert FD
03/16/2023, 1:09 PMThanks so much for the follow up!! We have been in the process of moving things over to json, but wondering if there will be any limits imposed on that in the future. Definitely exploring things on our end.