-
Notifications
You must be signed in to change notification settings - Fork 41
Initialization failure with Puppet Agent 8.10.0 #901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can confirm that the fix is working (same software stack) |
@robeke thanks for raising this, i'll get this added to our backlog, and we will get round to it as soon as we can. This project is open-source, so if you want to submit a PR with your fix, I can get it reviewed and released much sooner. Otherwise, whoever picks up the ticket will keep this issue updated! Thanks |
@jordanbreen28 Thanks and I will look into submitting a PR to possibly speed things up. |
ubygems.rb has been removed in rubygems 3.2.0 with rubygems/rubygems#3102 Fixes puppetlabs#901
Please see #919 for a PR with the suggested fix. Feel free to commandeer the PR as you wish! |
What Versions are you running?
OS Version: Linux x64 6.6.63-1-MANJARO (Manjaro Linux 24.1.2)
VSCode Version: 1.95.3
Puppet Extension Version: 1.5.4
PDK Version: NA
What You Are Seeing?
Initialization of the server fails when running the extension using Puppet Agent 8.10.1.
What is Expected?
Normal server initialization.
How Did You Get This To Happen? (Steps to Reproduce)
The system update applied on 4 December included an upgrade of Puppet Agent from 7.33.0-1 to 8.10.0-1. The failure was first encountered after that upgrade.
Output Log
Workaround
Changing the value assigned to
RUBYOPT
in commandHelper.js (line 166) fromrubygems
to-rrubygems
allowed initialization to proceed without failure.The text was updated successfully, but these errors were encountered: