Rollback commits when encountering an exception

[jgwerner]

• Adds the SQLAlchemy rollback() method when encountering an exception

[Abhi94N]

LGTM

[codecov]

Codecov Report

Merging #582 (1d91463) into main (814e11f) will increase coverage by 8.09%.
The diff coverage is n/a.

❗ Current head 1d91463 differs from pull request most recent head a9dfbc7. Consider uploading reports for the commit a9dfbc7 to get more accurate results

@@            Coverage Diff             @@
##             main     #582      +/-   ##
==========================================
+ Coverage   66.54%   74.63%   +8.09%     
==========================================
  Files          12       15       +3     
  Lines         807     1025     +218     
==========================================
+ Hits          537      765     +228     
+ Misses        270      260      -10     

Impacted Files	Coverage Δ
...illumidesk/illumidesk/apis/setup_course_service.py	62.06% <ø> (ø)
src/illumidesk/illumidesk/grades/handlers.py	63.15% <0.00%> (ø)
src/illumidesk/illumidesk/grades/senders.py	78.86% <0.00%> (ø)
src/illumidesk/illumidesk/grades/exceptions.py	100.00% <0.00%> (ø)
src/illumidesk/illumidesk/authenticators/utils.py	96.29% <0.00%> (+0.37%)	⬆️
...c/illumidesk/illumidesk/authenticators/handlers.py	82.17% <0.00%> (+2.38%)	⬆️
...umidesk/illumidesk/authenticators/authenticator.py	87.87% <0.00%> (+13.42%)	⬆️
.../illumidesk/illumidesk/authenticators/validator.py	85.48% <0.00%> (+24.19%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 814e11f...a9dfbc7. Read the comment docs.

[Abhi94N]

closing session after rollback LGTM

[jgwerner]

@Abhi94N here is a summary of the errors encountered with this PR so we can find the root cause.

• AWS EKS cluster in us-west-2 region
• Kubernetes namespace: illumidesk
• Helm chart version: latest
• Grader setup service image: illumidesk/grader-setup-service:582 (built from this PR's sources)

The errors are related to permissions issues when the grader-setup-service attempts to deploy a new shared grader notebook. To view a stack trace of the error one just needs to replicate the POST request sent to the http://grader-setup-service:8000/services/<org_name>/<course_name> endpoint:

• Open a terminal tab and then into the grader setup service: kubectl exec --stdin --tty grader-setup-service-<id> <namespace> -- /bin/bash
• Open a new terminal tab and stream logs: kubectl logs -f grader-setup-service-<id> -n <namespace>
• From the first tab, create a POST request with curl: curl -v -X POST http://localhost:8000/services/<org_name>/<course_name>
• The stack trace should display an issue related to kubernetes permissions

We tested updating the illumidesk/helm-chart repo so that the ClusterRole and ClusterRoleBinding removes typos and duplicate entries. We also successfully created a new deployment from the grader-setup-service pod using this example.