Bug #33013
bundler warns /usr/share/foreman is not writable
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Description
When running foreman-rake, Bundler complains the home directory is not writable.
Executing: foreman-rake upgrade:run `/usr/share/foreman` is not writable. Bundler will use `/tmp/bundler20210520-43729-pzug1w43729' as your home directory temporarily. 'ErbParser' is ignored. 'RubyParser' is ignored. ============================================= Upgrade Step 1/2: katello:correct_repositories. This may take a long while. ============================================= Upgrade Step 2/2: katello:clean_backend_objects. This may take a long while. Failed upgrade task: katello:clean_backend_objects, see logs for more information.
This is a problem with a recent enough Bundler (as present in rh-ruby27). In particular that contains a fix for https://access.redhat.com/security/cve/CVE-2019-3881 (https://github.com/rubygems/bundler/commit/02e7f67727b45).
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot over 1 year ago
Updated by - Assignee set to Ewoud Kohl van Wijngaarden
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8663 added
#2
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 3.0.0 added
#3
Updated by Ewoud Kohl van Wijngaarden over 1 year ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset foreman|f25a21e1b0c9642209df91558a9b51e24e820af9.
#4
Updated by Tomer Brisker over 1 year ago
Updated by - Category set to Packaging
#5
Updated by Evgeni Golov about 1 year ago
Updated by - Related to Bug #33520: bundler warns /usr/share/foreman-proxy is not writable added
Fixes #33013 - Silence bundler in production
In production deployments the Rails directory is usually not writable.
This leads to warnings. By using the silent UI this is hidden from
users.