Project

General

Profile

Actions

Bug #33013

closed

bundler warns /usr/share/foreman is not writable

Added by Ewoud Kohl van Wijngaarden about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Packaging
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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 1 (0 open1 closed)

Related to Smart Proxy - Bug #33520: bundler warns /usr/share/foreman-proxy is not writableClosedEvgeni GolovActions
Actions #1

Updated by The Foreman Bot about 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ewoud Kohl van Wijngaarden
  • Pull request https://github.com/theforeman/foreman/pull/8663 added
Actions #2

Updated by The Foreman Bot about 3 years ago

  • Fixed in Releases 3.0.0 added
Actions #3

Updated by Ewoud Kohl van Wijngaarden about 3 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Tomer Brisker almost 3 years ago

  • Category set to Packaging
Actions #5

Updated by Evgeni Golov almost 3 years ago

  • Related to Bug #33520: bundler warns /usr/share/foreman-proxy is not writable added
Actions

Also available in: Atom PDF