-
Notifications
You must be signed in to change notification settings - Fork 7
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
can't list workflow runs in case of PVC failures #221
Projects
Comments
flaviodsr
added a commit
to flaviodsr/fuseml-core
that referenced
this issue
Sep 10, 2021
- design: Removes the `Enum` filter as the status can also returns a workflow failure reason. - when a workflow run fails report its status as `Failed (reason)`. Fixes: fuseml/fuseml#221
flaviodsr
added a commit
to flaviodsr/fuseml-core
that referenced
this issue
Sep 10, 2021
- design: Removes the `Enum` filter as the status can also returns a workflow failure reason. - when a workflow run fails report its status as `Failed (reason)`. Fixes: fuseml/fuseml#221
flaviodsr
added a commit
to flaviodsr/fuseml-core
that referenced
this issue
Sep 10, 2021
- design: Removes the `Enum` filter as the status can also returns a workflow failure reason. - when a workflow run fails report its status as `Failed (reason)`. Fixes: fuseml/fuseml#221
flaviodsr
added a commit
to flaviodsr/fuseml-core
that referenced
this issue
Sep 10, 2021
- design: Removes the `Enum` filter as the status can also returns a workflow failure reason. - when a workflow run fails report its status as `Failed (reason)`. Fixes: fuseml/fuseml#221 (cherry picked from commit 1f6746d)
flaviodsr
added a commit
to flaviodsr/fuseml-core
that referenced
this issue
Sep 10, 2021
- design: Removes the `Enum` filter as the status can also returns a workflow failure reason. - when a workflow run fails report its status as `Failed (reason)`. Fixes: fuseml/fuseml#221 (cherry picked from commit 1f6746d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is taken from a FuseML installation in a cluster that accidentally had two default storage classes configured. Upon trying to run the mlflow-e2e workflow, an error was triggered:
The underlying cause was fixed, but then listing workflow runs with FuseML stopped working properly because:
The text was updated successfully, but these errors were encountered: