Skip to content
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

Closed
rhizoet opened this issue Jul 13, 2023 · 8 comments · Fixed by #215
Closed

Can not add Logo at setup or in settings #200

rhizoet opened this issue Jul 13, 2023 · 8 comments · Fixed by #215

Comments

@rhizoet
Copy link

rhizoet commented Jul 13, 2023

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:

Read-only file system @ rb_sysopen - /opt/zammad/public/assets/images/2e8e695017d62bf4d9cbb01703ac55c1.png

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

@rhizoet
Copy link
Author

rhizoet commented Jul 13, 2023

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.
Back-off restarting failed container postgresql-init in pod zammad-0_helpdesk(2e98ac3b-66ea-4d5f-b8b2-7b1ab772c321)

Edit: Ok, its based on the same error:
Errno::EROFS: Read-only file system @ rb_sysopen - /opt/zammad/public/assets/images/2e8e695017d62bf4d9cbb01703ac55c1.png

@monotek
Copy link
Member

monotek commented Jul 13, 2023

see: #197

@monotek
Copy link
Member

monotek commented Jul 18, 2023

fixed in: #197

@monotek monotek closed this as completed Jul 18, 2023
@rhizoet
Copy link
Author

rhizoet commented Jul 19, 2023

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 public will not be mounted. So this should also be accomplished by a volume I think

@rhizoet
Copy link
Author

rhizoet commented Jul 20, 2023

@monotek can you reopen the issue because it's not fixed?

@monotek monotek reopened this Jul 20, 2023
@klml
Copy link
Contributor

klml commented Jul 20, 2023

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:

$ oc logs zammad-0 -c postgresql-init
...
I, [2023-07-20T06:34:15.703646#11-6180]  INFO -- : Setting.set('product_logo', "83082929b160f0c39c212914ddff9cb3.png")
rake aborted!

I'm not sure if there might be a coincidence after all?

Full log

$ oc logs zammad-0 -c postgresql-init
I, [2023-07-20T06:34:13.200735 #11]  INFO -- : ActionCable is using the redis instance at redis://:zammad@zammad-redis-master:6379.
I, [2023-07-20T06:34:13.306528#11-6180]  INFO -- : Using memcached as Rails cache store.
I, [2023-07-20T06:34:13.306986#11-6180]  INFO -- : Using the Redis back end for Zammad's web socket session store.
I, [2023-07-20T06:34:15.703646#11-6180]  INFO -- : Setting.set('product_logo', "83082929b160f0c39c212914ddff9cb3.png")
rake aborted!
Errno::EROFS: Read-only file system @ rb_sysopen - /opt/zammad/public/assets/images/83082929b160f0c39c212914ddff9cb3.png
/opt/zammad/lib/static_assets.rb:177:in `initialize'
/opt/zammad/lib/static_assets.rb:177:in `open'
/opt/zammad/lib/static_assets.rb:177:in `sync'
/opt/zammad/config/initializers/logo.rb:11:in `block in <main>'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in `instance_exec'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in `block in make_lambda'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in `catch'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in `block in default_terminator'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:199:in `block in halting'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `block in invoke_before'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `each'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `invoke_before'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:105:in `run_callbacks'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/reloader.rb:88:in `prepare!'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/application/finisher.rb:124:in `block in <module:Finisher>'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in `instance_exec'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in `run'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/initializable.rb:61:in `block in run_initializers'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/initializable.rb:60:in `run_initializers'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/application.rb:391:in `initialize!'
/opt/zammad/config/environment.rb:7:in `<main>'
/usr/local/bundle/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/bundle/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/bundle/gems/zeitwerk-2.6.8/lib/zeitwerk/kernel.rb:38:in `require'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:332:in `block in require'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:299:in `load_dependency'
/usr/local/bundle/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:332:in `require'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/application.rb:367:in `require_environment!'
/usr/local/bundle/gems/railties-6.1.7.3/lib/rails/application.rb:533:in `block in run_tasks_blocks'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:58:in `load'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:58:in `kernel_load'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli/exec.rb:23:in `run'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli.rb:491:in `exec'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli.rb:34:in `dispatch'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/cli.rb:28:in `start'
/usr/local/bundle/gems/bundler-2.4.1/exe/bundle:45:in `block in <top (required)>'
/usr/local/bundle/gems/bundler-2.4.1/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/usr/local/bundle/gems/bundler-2.4.1/exe/bundle:33:in `<top (required)>'
/usr/local/bundle/bin/bundle:25:in `load'
/usr/local/bundle/bin/bundle:25:in `<main>'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)

@alexkorotysh
Copy link
Contributor

Any updates with broken logo?

@monotek
Copy link
Member

monotek commented Sep 25, 2023

will be fixed in: #215

@monotek monotek closed this as completed Sep 25, 2023
monotek pushed a commit that referenced this issue Sep 26, 2023
monotek added a commit that referenced this issue Sep 26, 2023
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants