Bug #716: Init script for rpm starts as foreman-proxy user, but that user has no write permission - Smart Proxy - Foreman

Actions

Copy link

Bug #716

closed

Init script for rpm starts as foreman-proxy user, but that user has no write permission

Added by Jeff Weiss about 13 years ago. Updated about 13 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Lukas Zapletal

Category:

Packaging

Target version:

0.1

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

[root@jweiss-foreman-1 smart-proxy]# service foreman-proxy start
Starting foreman-proxy: WARNING: Missing SSL setup, working in clear text mode !

/usr/lib/ruby/1.8/fileutils.rb:243:in `mkdir': Permission denied - /usr/share/foreman-proxy/bin/../tmp (Errno::EACCES)
from /usr/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir'
from /usr/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p'
from /usr/lib/ruby/1.8/fileutils.rb:215:in `reverse_each'
from /usr/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p'
from /usr/lib/ruby/1.8/fileutils.rb:201:in `each'
from /usr/lib/ruby/1.8/fileutils.rb:201:in `mkdir_p'
from /usr/share/foreman-proxy/bin/../lib/sinatra-patch.rb:15:in `run!'
from /usr/share/foreman-proxy/bin/smart-proxy:102
[FAILED]
[root@jweiss-foreman-1 smart-proxy]# rpm -q foreman-proxy
foreman-proxy-0.1-rc1.noarch

I think the fix might be to have it run as root (change the default FOREMAN_PROXY_USER to root in /etc/sysconfig/foreman-proxy). Alternative is that the rpm should create the foreman-proxy user with a HOME dir he can write to. Currently that is /usr/share/foreman-proxy and it is owned by root.