-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.0.3] Unable to complete recipe run without erroring, but upload appears to succeed. #167
Comments
I've tested it against another Jamf Cloud instance which is running the current 10.15.1 release and it looks like AutoPkg + JSSImporter is working correctly (please see output below). I'm going to follow up with Jamf to see if this is an issue with the 10.16 beta version we're running on the first Jamf Cloud instance.
|
Thanks for the updates @rtrouton. Bit busy today but will try and look at it as soon as I submit a certain draft presentation with a looming deadline ... |
Hi Rich, But, after that check, the 500 error came. A 500 error is not what I’m normally coming across here; normally we see a 404 or 409. 500 is an internal server error, so I’d be looking to see if there’s some connection issue. On new beta instances I normally get 503 errors for a while, until everything is spun up. I don’t think they actually spin up a repo until you request one (I.e. do something that requires one). But again: 503 is not 500. |
I'm seeing an odd problem with a Jamf Cloud-hosted server, where I can see the server return the ID number of the uploaded package, but JSSImporter isn't able to properly work with it for some reason:
macOS 10.14.6 (fully updated)
AutoPkg 1.2
python-jss version: 2.0.1.
JSSImporter version: 1.0.3.
Jamf Pro server is running a beta version of 10.16.x.
Full output of run is below. In this case, I'm trying to upload a Mozilla Firefox installer package.
The text was updated successfully, but these errors were encountered: