Bug #2216
closed
secret_token is generated with wrong file permissions
Description
After install and first access, I get
Permission denied - /usr/share/foreman/tmp/secret_token
Updated by Dominic Cleal about 11 years ago
- Category set to Packaging
How did you install Foreman, which packages? Was the file root-owned rather than foreman?
Updated by Jan Vansteenkiste about 11 years ago
Installed Packages
foreman.noarch 1.1stable-3.el6 @foreman
Files were root-owned.
Updated by Dominic Cleal about 11 years ago
- Status changed from New to Feedback
This must be something running Foreman/Rails as root during installation, but I can't see what it would be. I also haven't run into this on my foreman-installer tests.
Could you check your install procedure and see if you're running something (e.g. a db:migrate) as root?
Updated by Greg Sutcliffe about 11 years ago
does $approot/tmp exist? I seem to recall filing a bug about getting that error if $approot/tmp is missing....
Updated by Dominic Cleal about 11 years ago
Greg Sutcliffe wrote:
does $approot/tmp exist? I seem to recall filing a bug about getting that error if $approot/tmp is missing....
#2196, looks like it was included in the version that Jan's running.
Updated by Jan Vansteenkiste about 11 years ago
Is this something that will be fixed in initializers/secret_token.rb or should I fix the permissions using puppet after the initial installation?
Updated by Dominic Cleal about 11 years ago
- Status changed from Feedback to Rejected
It was a dbmigrate in Jan's manifests running as root, not foreman.