-
Bug
-
Resolution: Done
-
Normal
-
None
-
RHODS_1.27.0_GA
-
False
-
None
-
False
-
Release Notes
-
Testable
-
No
-
-
-
-
-
-
-
No
-
-
Known Issue
-
Done
-
No
-
Pending
-
None
-
-
Description of problem:
Similarly to https://issues.redhat.com/browse/RHODS-6373 , in DS Pipeline we hit the same problem when we have long project title names.
Based on the info in this k8s document and some trials, we noticed that the combination of route name (i.e., ds-pipeline-pipelines-definition in our case - 32 chars) + project title) cannot exceed 63 62 characters.
Examples
1) project title: bertopipelines-abcdefghilmnopqr (31 chars): fails. The failure consists in
DS pipeline pods not being created. Sometime I saw only 2 out 4 pods, sometimes none of them
2) project title: bertopipelines-abcdefghilmnopq (30 chars): OK.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- create a DS project whose resource name has 31 or more characters
- create a pipeline server in the same DS project
Actual results:
Pipeline server fails to be created
Expected results:
TBD
Options:
- reduce the host prefix ds-pipeline-pipelines-definition to something shorter
- prevent users from inserting long project titles
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
RHODS v1.27.0
Workaround:
Additional info:
- is related to
-
RHODS-9373 hostname for model serving endpoint can be too long, causing the route to not be created
- Closed
- relates to
-
RHODS-6373 [DSG] Workbench fails to start when using long titles for both project and workbench
- Closed