Skip to content
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

Clicking 'Start Now' Fails to run Execution Policy #10

Closed
1 of 2 tasks
vailster opened this issue Mar 31, 2022 · 4 comments
Closed
1 of 2 tasks

Clicking 'Start Now' Fails to run Execution Policy #10

vailster opened this issue Mar 31, 2022 · 4 comments
Assignees
Labels

Comments

@vailster
Copy link

vailster commented Mar 31, 2022

Describe the bug
Choosing the 'Start Now' option results in an error message.

Python 3

Note: Issues opened without specifying one of the following options will be ignored.

  • I am using the macadmins Python distribution that I installed on the affected Mac.
  • I am using a Python 3 runtime I installed myself, and I updated the script's shebang to point to the that python3 binary.

To Reproduce
Steps to reproduce the behavior:

  1. Run the 'Prompt' policy
  2. Select Start Now, click ok
  3. Get error baked into the script 'A problem occurred processing your request. Please contact your administrator for assistance'

Expected behavior
To run the 'Execution' policy

Error output
'A problem occurred processing your request. Please contact your administrator for assistance'

Just to add, if the execution policy is deferred, it runs fine at the specified deferred time.

@haircut haircut self-assigned this Apr 2, 2022
@haircut haircut added the bug label Apr 2, 2022
@haircut
Copy link
Owner

haircut commented Apr 2, 2022

👋 @vailster

I believe I've corrected this issue in 32a1308. I was not correctly handling the bytes string returned by jamfHelper after the transition to Python 3.

Would you please copy the latest version of the script from the repository, then try your workflow again? Please let me know the result.

@vailster
Copy link
Author

vailster commented Apr 4, 2022

Thanks @haircut - gave it a test this morning. Looks like the error is gone when running the execution policy immediately. But, it seems now that the execution policy doesn't actually start, either immediately or when deferred.

@vailster
Copy link
Author

vailster commented Apr 4, 2022

Ignore me, I removed and re-added the script to Jamf again and this time it worked 🎉
Thanks for your help @haircut 🙌

@vailster vailster closed this as completed Apr 4, 2022
@vailster
Copy link
Author

vailster commented Apr 4, 2022

All working 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants