-
Notifications
You must be signed in to change notification settings - Fork 69
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
Can not add Logo at setup or in settings #200
Comments
Oh, the Zammad Pod does not come up again if I had done some changes and the GUI states, that I have to restart all the services. Edit: Ok, its based on the same error: |
see: #197 |
fixed in: #197 |
I'm always get the same error even with the new version of the chart. Can you have a look what's up with the images? Edit: As far as I see it, the Path |
@monotek can you reopen the issue because it's not fixed? |
We may have the same problem. We configured a logo via webinterface, after this, the statefulset zammad got "CrashLoopBackOff" at the init of zammad-0, the postgresql-init aborted after setting product_logo:
I'm not sure if there might be a coincidence after all? Full log
|
Any updates with broken logo? |
will be fixed in: #215 |
* Fixes #212, fixes #200 - Switch to Zammad 6.1. * Solve #203 - attachment upload * set rofs to true again & fix tmp dir issues Signed-off-by: André Bauer <andre.bauer@staffbase.com> --------- Signed-off-by: André Bauer <andre.bauer@staffbase.com> Co-authored-by: André Bauer <monotek@users.noreply.github.com>
Is this a request for help?: yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Kubernetes: 1.26.6
Helm: 3.12.0
Zammad-helm: 9.0.4
What happened:
When I install Zammad and get to the part where I can select a logo, the following error message comes up:
I have also already set
readOnlyRootFilesystem: false
for all init containers. However, this does not change anything.What you expected to happen:
I assume that I can upload a logo and this will be added to Zammad. There should be no error message that this is a
read-only fs
.How to reproduce it (as minimally and precisely as possible):
Install the current helm chart and try to add a logo during setup. Or in the settings when setup is finished.
Anything else we need to know:
![Screenshot_20230713_113854](https://private-user-images.githubusercontent.com/58997736/253234887-ff0ef066-05f7-4705-b722-0aa2e668cc24.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMwODQ2NDAsIm5iZiI6MTcyMzA4NDM0MCwicGF0aCI6Ii81ODk5NzczNi8yNTMyMzQ4ODctZmYwZWYwNjYtMDVmNy00NzA1LWI3MjItMGFhMmU2NjhjYzI0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODA4VDAyMzIyMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc1MDdkYjc1ZDM3Y2QwZWQ0NjA0YWUxMmJkMzBjYWEyNmE5NTQ1YTJkMjM4YjU5N2E4NTE4ODMwNDE5MDFlNDAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Dne818qkgYDQrBsqeOVgMFGzlsvJ-riMp3Ai4NbalPY)
The text was updated successfully, but these errors were encountered: