[1.0.2b2] Unable to upload Self Service Icons

[qu1gl3s]

Hi,

Currently unable to upload Self Service Icons, here is the error I'm receiving.

All other functionality is working as intended.

'self_service_icon': u'MSTeams.png',

JSSImporter: Found file: /Users/administrator/Library/AutoPkg/RecipeRepos/#####/MSTeams/MSTeams.png
Response Code: 404 Response: The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. https://#####:8443//JSSResource/fileuploads/policies/id/587.
Failed.

Error in #####.MSTeams: Processor: JSSImporter: Error: Response Code: 404 Response: The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. https://#####:8443//JSSResource/fileuploads/policies/id/587.

This is running as verbose with -vv

Thanks!

[grahampugh]

@qu1gl3s Are you using Jamf Cloud? I wonder if this is a delay issue where it is expecting to find policy 587 but it hasn't yet been replicated to the cloud node that it's attempting to upload the icon to. We're seeing a few issues with this.

[grahampugh]

I believe this is a duplicate of #81

[qu1gl3s]

Hi Graham,

I'm not a Jamf Cloud customer, I'm on-premise so I can't see any reason so far that could explain the issue at hand.

Thanks!

[grahampugh]

OK, is this a generic issue with all icons or just the MSTeams icon? Have you tried running it on more than one Mac?

[qu1gl3s]

Yes, I've tried running it on more than one Mac and all icons are affected, including existing ones.

[grahampugh]

On prem or a cloud DP e.g. S3?

[qu1gl3s]

On-prem distribution point.

[perryk]

Hi,

I've run into this issue recently also. For me, icons failed to upload for an On-prem distribution point yet uploaded without any trouble to a Cloud based DP. I was receiving the same error message as above, although if I manually uploaded the icon and re-run the recipe it would complete ok.

I still have both instances in a testing environment, the Cloud based DP is a Jamf 10.13 Beta cloud instance.

I was also using 1.0.2b2, however, I can test with 1.0.2b3 shortly.

[perryk]

Ok, have tried this and 1.0.2b3 has the same issue with On-prem DP for me.

All good if manually uploading the icon and using STOP_IF_NO_JSS_UPLOAD to continue even if the package uploaded ok earlier.

[grahampugh]

Hi @perryk you say this affected you recently, could that be related to a Jamf Pro update? I started having some icon upload issues from last week using regular curl (not JSSImporter issues) where the icon is corrupted, around the same time I upgraded to 10.12. It’s probably unrelated but worth an ask!

Update: This was unrelated in the end - some issue with our nginx load balancer that went away when pointing directly to one of our JSSes.

[perryk]

Sorry, this is the first time I have stood up Autopkg/JSS Importer so actually I have only tested on 10.13 beta for On-Prem and 10.12 for Cloud.

[qu1gl3s]

Just confirming the issue is still occurring in 1.0.3.

Not sure whether there is an issue with the API accepting the image.

[aluminummonster00]

Having the same issue in 1.0.5, cloud distribution point.