-
Notifications
You must be signed in to change notification settings - Fork 57
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
[BUG]Can create folder in upper case but cannot access the folder #662
Comments
Checkmk forum link as a cross-reference. In the forum the issue sounded more like a feedback topic, in a sense that a design decision is challenged. This issue now makes it sound more like a bug, so we need to investigate first and then see, how to proceed. |
there is a quick bug fix,
one should only remove have tested already. |
@msekania you want to do the honours of creating a PR, or should we do it? |
It's just a single line, I do not mind if you directly do the changes in develop branch |
Pushed the fix: fbcd840 @mike1098 can you install the collection from the |
I am currently testing site integration. Please let me finish this first. I hope I will be able t test devel next Tuesday. |
I tested devel branch OK with following folder structure:
|
Marvelous! Then the fix will be released with version |
Will it also contain pull request from Lars #654 Distri Sites? |
Describe the bug
I can create a folder in upper case:
But if I then try to cerate a subfolder it fails because path is forced to be in lower case.
### Error message:
"These fields have problems: parent", "fields": {"parent": ["The folder \‘/local_monitoring/de\’ could not be found."]}}'"}
Component Name
Component Name: folder
Ansible Version
Checkmk Version and Edition
2.2.0p33.cee
Collection Version
To Reproduce
see above
Expected behavior
I expect that I can create and access folders in upper and lower case on OS level.
Actual behavior
I can create a folder on OS level in upper case but I cannot access the folder because the path is forced to be in lower case.
Minimum reproduction example
See above
Additional context
Not applicable
The text was updated successfully, but these errors were encountered: