Fixed double slash in secret breaking db insert#4392
Conversation
|
@blueorangutan package |
|
@Spaceman1984 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2154 |
|
Needs end to end testing |
|
Does this happen on Primate too @Spaceman1984 or just a UI issue, than backend issue? (related to secret input for adding ceph/rbd pool) |
|
I'll check Primate. |
|
@rhtyd I don't see RBD as an option on Primate for primary storage, my fix was for the UI, but I can't be sure if this works as expected, we need a working back end to test. Not testing end to end is the reason for the "Draft PR". |
|
Note - Needs testing |
|
Looks like this only affects the old UI, if we're not getting it in 4.15 we may want to check Primate and then close this. cc @sureshanaparti @DaanHoogland et al |
|
We can keep this open or merge it. old UI so no real consequences. |
|
I have seen this issue to register RBD pool via UI inded in case "/" appear in Rados secret. Quite a corner case to have "/" on the secret, thus not really noticed I guess. |
|
@GabrielBrascher can you test whether you have this issue in primate? |
|
@DaanHoogland @Spaceman1984 I just tested it. The same exception as the one presented at #4147 happens when adding RBD pool via the Primate UI. A password containing multiple multiple '/' (e.g. 1234//1234) resulted on the following exception; the same password with just one '/' does not preset this exception. Output with dummy values for adding a RBD pool with double slashes: |
|
Maybe this should be addressed on the backend. |
|
@GabrielBrascher I don't see a double slash in that output, what is the problematic field, and what was the input value? |
|
@Spaceman1984 the issue is reported on 4.13. can you rebase? |
|
@DaanHoogland sorry, I did not provide all the details on the test. What happens is that the double slashes break the input. For instance, I configured a RBD pool with a password of From the management server side it is possible to check the API request as: Note that the url had scaped one "/" (%2F) between 1234 and 12334 . URL: Full log: |
Description
Fixes: #4147
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
From the front end, add RBD primary storage pool with a secrect with 2 slashes next to each other - no error.