This needs to be kept at the top so Jamf will actually give it any type of priority.
Anyone else having this issue PLEASE open a ticket.
@tomt I've been trying to do an initial sync from my on prem distribution point to the Jamf Cloud Distribution point when I started encountering problems on Thursday. I initially started it on Tuesday, but then started having on Thursday with files trying 3 to 5 times to upload - even if they are small files (such as 4 MB). I'm going to query the person I'm working with on my support ticket. I'm glad I found this thread.
Support told me today it's related to PI-005548 but given that, that appears to be a 2 year old issue I'm quite unimpressed
Except that SOMETHING changed in the last week that seems to have exacerbated whatever issue that PI is caused by.
My uploads are failing around 80% of the time!
We're seeing a lot of failures recently, no matter if the packages are uploaded through the web interface, via jssimporter, or through Jamf Admin. We finally sent in a note to support today. It's getting a bit ridiculous.
Another day of failed uploads for me 🙁
I was told that we should get word in this thread from someone on the Product Team.
Thanks for the update,@tomt ! Was a time frame given to you on when the Jamf Product Team might have a resolution?
No timeframe yet. I have been trying to get valid information out of Jamf for two days now. I've escalated this through both front and back channels (I know a few people) to get it this far.
"A Product Issue was re-opened to address the issue, PI-005548"
I don't want to copy/paste the entire email because that doesn't seem right. I will say that it was full of corporate buzzwords like Product Owner, Cadences, Efforts, etc. which does not give me a warm and fuzzy feeling. I hear them every day and usually they mean almost nothing.
That's why I prefer dealing with Engineers, they don't have time for bullshit.
Yeah, even 100 MB pkg uploads failing these days. Jamf Cloud Team ... PLEASE get some traction on this issue as I'm unable to get stuff done under these circumstances.
I got this note back on Monday:
I believe you have encountered an issue we are tracking currently here at Jamf regard to issue (PI-006754) uploading packages to Jamf Cloud. As far with our testing, even smallest package failed to upload to cloud distribution point and deleting package objects allow you to upload again. We also notice if you rename the package and deleting the object package titles also allow you to upload packages too.
@mscottblake That USED to work and seems to be the new standard boilerplate response from Support.
I only thought it noteworthy because I got a newer PI number.
@mscottblake Good call, I didn't notice the number. That's what I get for posting before coffee...
Having this issue today...joy
can confirm its any size, mine is only 15MB
I too put in a ticket and was told that it's being tracked in PI-005548... I dont think these are the same issues though.
I think these are all symptoms of the same general issue. There seems to be something broken in the communication between the Jamf Cloud web servers and their JCDS buckets in AWS.
The only common thing I have noticed with multiple postings is that everyone who has mentioned it is hosted on US-East.
Yup, US-East here as well...
Even though I'm on the west coast, I was provisioned with Jamf Cloud on US-East when we migrated from on-prem to cloud recently. So me too, US-East.
I know, this might not help, but I change to Chrome for .pkg uploads and saw improvements. I was trying to upload 10.15.5 (8+ GB)
C
At this point I would use IE on XP if it would work.
i am us-east, interesting...
@gachowski my custom 20MB pkg from Composer keeps failing
Ok, I combined a couple of the workarounds posted and it seems to be working for me.
- Replace any underscores with hyphens.
- Use only Chrome to upload.
I usually use Safari for everything and I have been using underscores in package names for a decade. I had my first success with a hyphenated name in Chrome. I then tried an underscore name in Chrome and it failed. I then tried a hyphenated name in Safari and it failed.
I have now done half a dozen new uploads using the hyphen/Chrome combination. Quitting Chrome in between just to reset the connection as a test. They were all 100mb or smaller since those were what I had waiting to go.
Can a few others give this combo a try so I know if I just got lucky or if this is really a valid workaround?
For me. I've only ever been using chrome. Hyphen, underscores and spaces whether there or not seem to make no difference. Size makes no difference (had a 4Gb package work earlier), renaming after deleting the failed package makes no difference. No matter the combination used only about 1 in 15 uploads works.
