Code Cleanup: Re-factor k8s-pod-recovery to handle failure conditions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
Unassigned |
Bug Description
Brief Description
-----------------
This is a follow-up on a comment in the following code review: https:/
Specifically:
Jim Somerville
kubernetes/
Line 170
I guess what I'm trying to say here is that I wouldn't necessarily block this code from going in, but would feel better if there is a story captured somewhere to improve the error paths in this script.
This LP will investigate what code cleanup should be pursued.
Severity
--------
Low - no reported issues now
Steps to Reproduce
------------------
N/A
Expected Behavior
------------------
N/A
Actual Behavior
----------------
N/A
Reproducibility
---------------
N/A
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
stx master
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
N/A
Workaround
----------
N/A
tags: | added: stx.containers |
Changed in starlingx: | |
importance: | Undecided → Low |
Changed in starlingx: | |
assignee: | nobody → Kyle MacLeod (kmacleod) |
status: | New → Triaged |
Changed in starlingx: | |
assignee: | Kyle MacLeod (kmacleod) → nobody |
tags: | added: stx.networking |