https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# puppet-enterprise
s
This message was deleted.
✅ 1
b
for the rugged warnings; There's an open ticket since months, just no feedback in it
and how do you access the internet? via a proxy probably?
m
Yep via proxy - this hasn't been an issue in the past with this machine. Just a couple weeks ago I added a new module and it's fine.
I wonder what happens if I remove a module, deploy code manager and re-add it.
Do you know the ticket number? I'll open a support case to have them +1 me there
b
did you configure the proxy in code manager
m
that rugged issue is solved in 2021.7.0 or higher
m
So I'm upgrading from 2023.1.0 to 2023.2.0 to see if there is a fix
m
so all currently supported releases, may i ask what version you are on incase there is a reversion
m
Proxy is configured in code manager - as this worked a week or two ago just fine
Maybe the updater fixes things on the current installation
m
the proxy issue is different the rugged thing is just a cosmetic deprecation error which should be sorted,
Id raise a support ticket for your proxy issues
b
@Marty Ewings the rugged issue is still unresolved in PE 2021.7.4
m
yeah im trying to understand that from the r10k ticket thats says its resolved
ah i see in ENTERPRISE-1461
well ruby 3 is incoming, ill check and see if its an issue there still
b
@Moe coming back to the proxy, which setting do you use to configure the proxy?
m
The proxy is configured in the pe.conf 
"puppet_enterprise::profile::master::r10k_proxy"
b
and got that also added to the r10k config
m
I'm updating the primary server from 2023.1.0 to 2023.2.0 right now to see if my installation was somehow borked
👍 1
b
Afterwards check 
/opt/puppetlabs/server/data/code-manager/r10k.yaml
m
But again, this was a working setup before.
m
I would also recommend opening a ticket with Support, that will be the best way to get this resolved promptly
👍 1
m
I'll report back
Ok so it was indeed the missing proxy setting in the r10k.yaml file. This was missing due to an invalid format in the hocon config of the pe.conf during installation (we must've updated the pe installation which borked the pe.conf) and then it did not insert the proxy setting in the r10k.yaml. So problem resolved thanks to both of you providing me with good tips what to check 🙂 🎉
b
I recommend putting as much configuration as possible into hiera. not into the pe.conf and not into the classifier
👍 1
m
Yes I'll revisit this with my team and discuss
Good suggestion as welll
n
FWIW we’re finally updating Rugged in 2023.3
🙌 1
There were a lot of issues we needed to resolve to make the jump, but our hand was finally forced with the jump to Ruby 3 🙂
m
Ruby 3 is coming with 2023.3?
n
Yes. Or I suppose I should say, our August release 🙂
👍 1
August-ish? I don’t know what words I’m actually supposed to use 😛
m
I'll don't hold you accountable if it's September:P
thankyou 1
😂 1
m
Q2 release which is late summer in field team speak
n
That’s Q3, right? 🙂
m
Fiscal Q2 probably
n
Oh right. upside down yee haw
m
yep
i think the q3 release in in the new year?
i dont understand the quarter system we use
same 1
🌈 1
i think it reflects the work done in the preceding quarter
m
Anyway: it'll get fixed in the near future and that's good to hear. If I may: Maybe this could be added to the Jira case just so folks are informed?
n
For sure, will do
Open in Slack
PreviousNext
Powered by