Closed dpanshug closed 2 days ago
@simrandhaliw tagging you as well, since you were involved in this UX discussion.
Attention: Patch coverage is 0%
with 6 lines
in your changes missing coverage. Please review.
Project coverage is 84.86%. Comparing base (
947c09b
) to head (0390bef
). Report is 12 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
frontend/src/pages/projects/notebook/utils.ts | 0.00% | 3 Missing :warning: |
frontend/src/utilities/notebookControllerUtils.ts | 0.00% | 3 Missing :warning: |
@andrewballantyne @simrandhaliw with the recent design change in the workbenches https://github.com/opendatahub-io/odh-dashboard/pull/3207 , the tooltip is removed and instead of "Starting" it is displaying "Failed" as the status is Error.
Before
With latest design
Can you please confirm if the "Failed" status works in this case of ImagePullBackOff?
ImagePullBackOff errors are sometimes transient... Failed
is probably not the best word... but I don't think it's technically the wrong word.
@dpanshug is this UI the same on the Workbench Table as well as the Project screen?
@dpanshug is this UI the same on the Workbench Table as well as the Project screen?
@andrewballantyne yes it's same
/retest
@dpanshug I am not sure why the file scan keeps failing. Maybe try to rebase the main branch and push it again?
/lgtm
the tooltip error says it is a [Warning]
, should there be another state for this notebook status chip?
thx @dpanshug /lgtm
the tooltip error says it is a [Warning], should there be another state for this notebook status chip?
@Gkrumbach07 ImagePullBackOff are errors that occur when container running in a pod fails to pull the required image from a container registry. The message might mention it as warning, but as mentioned previously in the JIRA we should display it as an error.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Gkrumbach07, manaswinidas
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Closes: RHOAIENG-1132
Description
Added case to handle notebook failure when reason === "BackOff"
How Has This Been Tested?
Test Impact
N/A
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main
@xianli123