Project

General

Custom queries

Profile

Actions
Copy link

Bug #19070

closed

"Could not locate Gemfile (Bundler::GemfileNotFound)" starting standalone Foreman service

Added by Matt Renfrow about 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
High
Assignee:
Dominic Cleal
Category:
RPMs
Target version:
1.14.4
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Foreman - 1.15.0
Red Hat JIRA:

Description

It seems that a package-based installation (following 3.3.1 in the installation docs) do not currently work in either 1.13 or 1.14. As far as I can tell, using foreman-installer still works, but in our environment we cannot use the installer-based approach.

I am able to reproduce this on a new CentOS 7 AWS AMI or local CentOS install from media by doing the following on a fresh install:

sudo yum install -y http://yum.theforeman.org/releases/1.14/el7/x86_64/foreman-release.rpm
sudo yum install -y foreman-release-scl epel-release
sudo yum install -y foreman foreman-proxy foreman-debug foreman-cli foreman-sqlite
sudo -u foreman /usr/share/foreman/extras/dbmigrate
sudo systemctl start foreman

Foreman logs the following to syslog:

Starting foreman: /opt/rh/rh-ruby22/root/usr/share/gems/gems/bundler-1.7.8/lib/bundler/shared_helpers.rb:26:in `default_gemfile': Could not locate Gemfile (Bundler::GemfileNotFound)
from /opt/rh/rh-ruby22/root/usr/share/gems/gems/bundler-1.7.8/lib/bundler/shared_helpers.rb:31:in `default_lockfile'
from /opt/rh/rh-ruby22/root/usr/share/gems/gems/bundler-1.7.8/lib/bundler.rb:253:in `default_lockfile'
from /usr/share/foreman/bin/spring:10:in `<top (required)>'
from /usr/share/foreman/bin/rails:3:in `load'
from /usr/share/foreman/bin/rails:3:in `<main>'

Attempting to start foreman manually by invoking the rails server (using tfm-ruby) throws the same error.

As far as I can tell, I can't reproduce this behavior for installations using foreman-installer. This seems to only happen to package-based installs, and only on versions 1.13 and 1.14.

#2

Updated by Dominic Cleal about 8 years ago

  • Subject changed from CentOS 7 packaged installs in foreman-release 1.13 and 1.14 cause foreman not to start to "Could not locate Gemfile (Bundler::GemfileNotFound)" starting standalone Foreman service
  • Category set to RPMs
#4

Updated by Sandro Emma about 8 years ago

  • Priority changed from Normal to Urgent
  • Translation missing: en.field_release set to 209
  • Difficulty set to medium
#6

Updated by Dominic Cleal about 8 years ago

  • Priority changed from Urgent to High
  • Translation missing: en.field_release deleted (209)
#8

Updated by Dominic Cleal about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal
  • Translation missing: en.field_release set to 241
#9

Updated by Dominic Cleal about 8 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF