https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# puppet-enterprise
s
This message was deleted.
b
v
Ha, I forgot I saw that ticket already
b
why are both zendesk tickets closed...
v
¯\_(ツ)_/¯
I will open ticket about other issue
b
let me check if I can see the zendesk ticket
v
btw, have you figured out how to insert code block in the ticket? No matter what I do, it inserts bunch of empty lines between
b
it's impossible
v
facepalm
b
I need to say I never created tickets on my own, I just recently got the SDP certification. but coworkers rant about code formatting in zendesk since zendesk is used
v
yeah, drives me nuts
And no idea where they get picture for my gravatar, I wish I was 20 years younger, like on that picture 🙂
b
😄
nice, now my login doesn't work
/me sighs
v
yeah, they have migrated support portal and file server, so no way to upload file from enterprise script
at least I didn't find a way
b
I've the feeling zendesk doesn't like the special chars in my password
g
Folks - If you can dig out your tickets we can link them to the above Jira. When you raise a ticket that is linked to a Jira - we tend close the zendesk ticket and track via the Jira. We (in Support) use the linked Zendesk tickets and input from yourselves in the field to add to the Jira to get traction on it. However, it’s over to the the product and development teams to triage and address the Jira’s in line with their projects and plans. We will keep advocating on your behalf, as always! If you have file upload issues (using the new MFT server) let us know and we can look into it. SFTP remains for the moment - so their shouldn’t be issues, but again let us know if that is an issue. Bear in mind we will likely be moving away from SFTP as a supported upload path going forward to utilise the MFT server. We did add some facility for formatting in Zendesk but we are at the mercy of Zendesk and have been requesting proper markdown for years (among many others!) Any issues with logins etc - let us know and the Zendesk team here can investigate. Thanks as always! g…
b
my issue is the lack of visibility form Product/development
I raised over 200 jira issues over the years I think. are they triaged? were they maybe looked at but added to the backlog with a lower prio? probably sometimes. but why isn't that communicated? they tickets are just sitting around
So I don't know if people saw the ticket, if it's being worked on or not. that's just so annoying
and sometimes tickets are cloned into an RK or PE ticket. those projects are not public. so there even is some engineering/development work, and it's logged to jira, just not visible to us external people, who raised the issue
https://tickets.puppetlabs.com/projects/ENTERPRISE/issues/ENTERPRISE-1487 I wrote some thoughts related to that down some time ago
g
Tim, I’ve passed this link into the dev ticket also for reference and I will follow up again by escalating this to my Senior Manager also. g…
❤️ 1
b
so clarifly: I'm really happy with the work the PE support and engineering delivers, I would just hope a bit more communication about the work
👍 1
g
@binford2k - can you also see who you can escalate this feedback to? thanks, g..
b
@bastelfreak and/or @vchepkov -- could you validate the r10k versions you're seeing the issue on? According to our PE component matrix, a fixed r10k should be shipping in every supported PE version now.
b
I can check that on Monday. Maybe @vchepkov is faster
👍 1
v
sure, but I keep opening PE tickets for new LTS 😞
Copy code
# rpm -q pe-r10k
pe-r10k-2021.7.3.15.4-1.el8.x86_64
b
that's what the matrix says too. And there's no way that you might somehow have a different version installed too?
v
I doubt
Copy code
# r10k version
r10k 3.15.4
b
okie doke. We'll poke at it more.
👍 1
v
there is one under blt-server
Copy code
/opt/puppetlabs/server/apps/bolt-server/lib/ruby/gems/r10k-3.15.3/lib/r10k
b
the problem should have been fixed in 3.14 so.....
Ok, looks like there are still some upstream problems with the version of rugged we're using. They were fixed in v1.0.1. We're going to need to upgrade it for ruby 3, so at that point, the warnings will go away.
gratitude thank you 1
Open in Slack
PreviousNext
Powered by