User is unable to create successful db clusters if the name of the db cluster is very long.
Steps to reproduce:
Create DB cluster
Give a long name to the DB cluster
Create DB cluster with default or custom resources
Actual result:
DB cluster remains in down state. It displays an error multiple time for the DB cluster.
Expected result:
There should be a limit defined for the length of the DB cluster name.
The error should only be displayed one time to the user.
DB cluster should get created successfully.
Environment
None
Attachments
6
100% Done
Activity
Iaroslavna Soloveva September 27, 2023 at 12:43 PM
Thanks, Yusaf! I will prepare a fix for this
Yusaf Awan September 27, 2023 at 9:51 AM
not a blocker, but we should have better error message for both upper case letter and symbols/special-characters. Also, the "Continue" option should be faded and made non-clickable when there is any error on this form, and we can not continue without resolving that error.
Oksana Grishchenko September 14, 2023 at 9:24 AM
the BE already works this way with the PR I merged earlier, however I realized that to avoid confusion we need to update the error message and the codebase so it would reference to RFC-1035 instead of RFC-1123. Created another PR to address the problem.
Diogo Recharte September 14, 2023 at 8:43 AM
Looks like we should also update the BE to use RFC1035 with a max length of 22 instead of the RFC1123 we were using before.
In summary both the FE and the BE should validate the names to respect:
contain at most 22 characters
contain only lowercase alphanumeric characters or '-'
start with an alphabetic character
end with an alphanumeric character
Oksana Grishchenko September 14, 2023 at 8:38 AM
Edited
So the problem wasn't in the name length, it was in the first digit. You can see the "mysql-3211234567890123" cluster name which is 22 symbols long and is ready, but all others that starts with a digit are stuck in initializing
User impact:
User is unable to create successful db clusters if the name of the db cluster is very long.
Steps to reproduce:
Create DB cluster
Give a long name to the DB cluster
Create DB cluster with default or custom resources
Actual result:
DB cluster remains in down state. It displays an error multiple time for the DB cluster.
Expected result:
There should be a limit defined for the length of the DB cluster name.
The error should only be displayed one time to the user.
DB cluster should get created successfully.