Bug 798810 - Deltacloud fails to start on F16
Summary: Deltacloud fails to start on F16
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: deltacloud-core
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Michal Fojtik
QA Contact: Ronelle Landy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 22:41 UTC by Matt Wagner
Modified: 2014-08-17 22:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:14:29 UTC
Embargoed:

Attachments (Terms of Use)

Description Matt Wagner 2012-02-29 22:41:49 UTC 
Description of problem:
On a fresh Fedora 16 install, with deltacloud-core from the Fedora repos, I am unable to start Deltacloud. "service deltacloud-core start" returns success immediately, but "service deltacloud-core status" shows it as "active (exited)".

/var/log/deltacloud-core/mock.log shows the following:

>> Writing PID to /var/run/deltacloud-core-mock.pid
>> Changing process privilege to nobody:nobody
>> Exiting!
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/daemonizing.rb:158:in `delete': Permission denied - /var/run/deltacloud-core-mock.pid (Errno::EACCES)
        from /usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/daemonizing.rb:158:in `remove_pid_file'
        from /usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/daemonizing.rb:59:in `daemonize'
/usr/share/deltacloud-core/lib/deltacloud/drivers/mock/mock_driver.rb:97:in `initialize': Please set either the DELTACLOUD_MOCK_STORAGE or USER environment variable (RuntimeError)
        from /usr/share/deltacloud-core/lib/deltacloud/drivers.rb:69:in `new'
        from /usr/share/deltacloud-core/lib/deltacloud/drivers.rb:69:in `driver'
        from /usr/share/deltacloud-core/lib/deltacloud/server.rb:59
        from /usr/lib/ruby/gems/1.8/gems/sinatra-1.2.6/lib/sinatra/base.rb:1211:in `configure'
        from (__DELEGATE__):3:in `send'
        from (__DELEGATE__):3:in `configure'
        from /usr/share/deltacloud-core/lib/deltacloud/server.rb:48
        from /usr/share/deltacloud-core/config.ru:25:in `load'
        from /usr/share/deltacloud-core/config.ru:25
        from /usr/lib/ruby/gems/1.8/gems/rack-1.3.0/lib/rack/builder.rb:51:in `instance_eval'
        from /usr/lib/ruby/gems/1.8/gems/rack-1.3.0/lib/rack/builder.rb:51:in `initialize'
        from /usr/share/deltacloud-core/config.ru:1:in `new'
        from /usr/share/deltacloud-core/config.ru:1




Version-Release number of selected component (if applicable):
deltacloud-core-vsphere-0.5.0-1.fc16.noarch
deltacloud-core-0.5.0-1.fc16.noarch
deltacloud-core-ec2-0.5.0-1.fc16.noarch
rubygem-deltacloud-client-0.5.0-1.fc16.noarch
deltacloud-core-rhevm-0.5.0-1.fc16.noarch



Steps to Reproduce:
1. Fresh F16 setup
2. yum install aeolus-all # probably more than is needed
3. service deltacloud-core status # and so on


Actual results:
deltacloud-core fails to start.


Expected results:
deltacloud-core starts properly


Additional info:
I hit this while testing something a while back but failed to track it then, so this isn't a brand-new issue.
Comment 1 Matt Wagner 2012-02-29 22:57:45 UTC 
This is fixed in the Aeolus testing repo (deltacloud-core-0.5.0-4.rc1.fc16.noarch) from http://repos.fedorapeople.org/repos/aeolus/conductor/testing/fedora-16/x86_64/ 

It's just the version in F16 itself that doesn't work. If we can get the version we're carrying in aeolus-testing into fedora-updates, I think this would be fixed.
Comment 2 Hugh Brock 2012-03-07 18:13:57 UTC 
This is not a product bug, removing cloudforms-1.0.0 flag.
Comment 3 Michal Fojtik 2012-03-07 21:25:58 UTC 
I pushed update for F16:

https://admin.fedoraproject.org/updates/deltacloud-core-0.5.0-2.fc16

This update should fix this issue. Please let me know if you experience any other issues with init scripts.
Note You need to log in before you can comment on or make changes to this bug.