File resource path handling bug in Puppet Enterprise 2025.10? PE 2025.10 can't seem to be able to handle spaces in file resource paths. This even affects file resources managing recursive directory contents where there aren't any explicit spaces in any of the file resource’s attributes (name, path, source), but the source directory contains files with spaces in their names. PE 2025.10 server and Puppet Agent 8.17 on Ubuntu 24.04.

Yes, Fran, you are correct, there is an issue with spaces in file paths right now. I was on a call earlier today where this was brought up as well. Have you filed a support ticket yet? I know that there are a few tickets in about this already but it would be good to get your voice in there too so that the support team can get back to everybody when a fix or workaround is available.

I've submitted a ticket with Perforce but the response I received so far implies there have only been a few reports so I’m not sure it’s receiving adequate attention. In trying to figure out if the problem was me or PE, I've been able to reproduce the issue in both scenarios: 1. Ubuntu 22.04 PE 2025.7 to 2025.10 migration 2. Migrate PE 2025.7 from Ubuntu 22.04 to Ubuntu 24.04, then upgrade to 2025.10

Thank you so much for getting the ticket in there. I agree that it probably needs some attention as this is a blocker in the flow without much of a workaround, that I know of, yet. I'm going to try to find the internal thread where I saw this being raised and see if there is any more help yet, but from what I know this has only started being reported very recently.

Thank you.

is there note of this in a "known issues/changelog" that's available before upgrading?

I don't think anything has been published yet. We should try to get something into the release notes, though. I'll chat with docs.

@Jason St-Cyr Something else I noticed with PE 2025.10 on Ubuntu — almost all of the installed PE deb packages still reference 2025.9 in their name — is this intentional?

From what I remember, 2025.10 is essentially 2025.9 with a patch on it after 2025.9 was pulled. I bet a lot of the packages didn't get renamed in the process, but that doesn't mean that was intentional. I'll raise the flag on that and check!

@Jason St-Cyr Thank you; I appreciate your responsiveness.

No worries! Support is always the best path to get trackable answers, but happy to help out where I can. I did chat with some of the team and it seems like the package names were intentionally not renamed when the 2025.10 patch was released to replace 2025.9. So what you are seeing is correct!

@Jason St-Cyr Is there anywhere we can track the status of this issue? I haven't received any updates to my ticket with Perforce. The PE 2025.10 documentation still doesn't mention this as a known issue, but this is a severe bug that makes upgrading to PE 2025.10 not an option. This problem seems to have been introduced in the upgrade from Puppet Agent 8.16 to 8.17, which went from Ruby 3.2.8 to 3.2.10. Ruby 3.2.10 introduced significant changes to URI encoding and parsing.

Hi @Fran Gelfand, your support ticket should be where you can track the status of the issue. Somebody should have been able to respond to your ticket, I wonder if the status got switched to 'awaiting customer' or something similar? You can DM me the info about the ticket and I'll see what I can find out. I had thought there were supposed to be documentation updates about this known issue, but I'm not sure where that landed. Hopefully I can find an update.

as this is blocking upgrade to 2025.10, is there a documented reference for this known issue/a timeline for a fix?

@arjarj My Perforce support ticket was finally updated on Friday — the fix has been added to the upcoming release of PE 2025.11, scheduled for mid June. I'm very disappointed that this is still not listed in the PE 2025.10 Upgrade cautions.

thanks for the update! @Fran Gelfand

@Jason St-Cyr and @arjarj I upgraded to PE 2025.11 and the problem with file names containing spaces has not been resolved. I have to downgrade back to PE 2025.7. @Jason St-Cyr I have reopened my ticket with Perforce, but can you please advise further. Is this something the dev team is aware of already?

According to the release notes, this should have been fixed. I can see the case about it closed. Re-opening the ticket is the correct way. There were several support tickets from different users that were opened related to this, and it is possible that while the symptoms are the same the underlying cause for your situation might be different from the others. I'll tag a note on the engineering ticket for this to note that this wasn't resolved for you and note that you've re-opened the support ticket.

Thank you!

All I saw was a reference to PE 2025.12... Those fixes should also go into PE 2026 (they should both come out around the same time).