-
Bug
-
Resolution: Done
-
Major
-
RHODS_1.21.0_GA
-
False
-
None
-
False
-
Testable
-
No
-
-
-
-
-
-
-
No
-
No
-
Pending
-
None
-
-
-
RHODS 1.23
-
Moderate
Description of problem:
Right now, when entering a misconfiguration in the servingruntime spec for a Model Server creation, will only log an error in the console and fallback to the default configuration.
Prerequisites (if any, like setup, operators/versions):
Have rhods 1.21 installed
Steps to Reproduce
- Modify the servingruntimes-config configmap with wrong configuration
- Create a new model server
- Check that the modal will submit the action and a error is logged
Actual results:
The modal won't alert the user that is using the default configuration
Expected results:
The modal should have an indicator about the failing state of the servingruntime spec.
Reproducibility (Always/Intermittent/Only Once):
Always
Testing steps
1. Delete the `servingruntimes-config` ConfigMap
2. Create a new Model Server
3. The new model deploy should have the fallback image
4. Create again the configmap with malformed values
5. Try to create a new Model Server
6. It will fail displaying a new message.
- mentioned on