-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
False
-
False
-
Documentation (Ref Guide, User Guide, etc.)
-
No
-
-
-
-
-
-
No
-
No
-
Yes
-
None
-
Description of problem:
Deleting a rhods-notebook pod for a running application is disruptive and causes immediate termination of the notebook. The same scenario will occur during node maintainance (node/machine reboots)
Prerequisites (if any, like setup, operators/versions):
Setup a RHODS cluster using stage with build v1.1.1-44
Steps to Reproduce
1) Login as one of the configured used (eg: ldap-admin1)
2) launch a minimal python notebook using RHODS Console
3) Run a simple program in loop (the one shown in the screenshot)
4) Find the pod associated with the user and delete pod
eg:
$ oc delete pod jupyterhub-nb-ldap-2dadmin3 -n rhods-notebooks
pod "jupyterhub-nb-ldap-2dadmin3" deleted
$ oc get pods -n rhods-notebooks
No resources found in rhods-notebooks namespace.
5) Notice the pod is not recreated and the program stop immediately with keyboard interrupt.
- <steps>
Actual results:
Program abruptly ends
Expected results:
HA should ensure uninterrupted execution of the program
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
v1.1.1-41
Additional info:
Easy to reproduce
- is documented by
-
RHODS-2019 Doc: Do not run uninterruptible tasks on RHODS JupyterHub
- Closed