/usr/share//foreman not writeable: problem, or non-issue?

Starting to play with Katello 4.1 on a test server.

When I run foreman-rake console, I get a message about the foreman directory being non-writeable. Is this a concern, or is this expected behavior now with version 4.x?

[root@gray01 ~]# foreman-rake console
`/usr/share/foreman` is not writable.
Bundler will use `/tmp/bundler20210713-8221-bhu7yd8221' as your home directory temporarily.
Loading production environment (Rails

When I exit, I get more fun:

rake aborted!
Errno::EACCES: Permission denied @ rb_sysopen - /usr/share/foreman/config/irbrc_history
/opt/theforeman/tfm/root/usr/share/gems/gems/railties- `start'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties- `start'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties- `perform'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/opt/theforeman/tfm/root/usr/share/gems/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties- `perform'
/opt/theforeman/tfm/root/usr/share/gems/gems/railties- `invoke'
/usr/share/foreman/lib/tasks/console.rake:5:in `block in <top (required)>'
/opt/rh/rh-ruby27/root/usr/share/gems/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Tasks: TOP => console
(See full trace by running task with --trace)

If I understand correctly, you can ignore the warning.

This is indeed something you can ignore. We also have another issue somewhere that talks about this. In 1962757 – /usr/share/foreman is not writable for satellite-installer I laid out some concerns with fixing this.