Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1113631

Summary: Gem loading error: Unable to activate staypuft-0.1.4
Product: Red Hat OpenStack Reporter: Dan Radez <dradez>
Component: rubygem-staypuftAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 6)CC: aberezin, ajeain, mburns, mlopes, rhos-maint, sasha
Target Milestone: ga   
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby193-rubygem-staypuft-0.1.5.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-21 18:04:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Radez 2014-06-26 14:16:22 UTC 
Description of problem:
Using a livecd from the 20140625.2 puddle.
when I run the installer I get an error that db migrate failed. When I run the db:migate by hand I get the error

[root@livecd ~]# foreman-rake db:migrate
rake aborted!
Gem loading error: Unable to activate staypuft-0.1.4, because dynflow-0.7.1 conflicts with dynflow (~> 0.6.1), foreman-tasks-0.6.4 conflicts with foreman-tasks (~> 0.5.3)

Version-Release number of selected component (if applicable):
20140625.2
ruby193-rubygem-staypuft

How reproducible:
every time

Steps to Reproduce:
1. build livecd
2. run installer
3.

Actual results:
installer fails

Expected results:
installer completes

Additional info:
Comment 1 Mike Burns 2014-06-26 14:53:01 UTC 
This can impact people not running the livecd.
Comment 2 Alexander Chuzhoy 2014-06-26 16:42:51 UTC 
Environment:
ruby193-rubygem-staypuft-0.1.4-1.el6ost.noarch
rhel-osp-installer-0.0.25-2.el6ost.noarch

Running rhel-osp-installer resulted in the following errors:

Could not start Service[foreman-tasks]: Execution of '/sbin/service foreman-tasks start' returned 10:                                                                                                               
 /Stage[main]/Foreman::Plugin::Tasks/Service[foreman-tasks]/ensure: change from stopped to running failed: Could not start Service[foreman-tasks]: Execution of '/sbin/service foreman-tasks start' returned 10:     
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[staypuft.lab.eng.rdu2.redhat.com]: Could not evaluate: 500 Internal Server Error                                                                            
Installing             Done                                               [100%] [.................................................................................................................................] 
Not running provisioning configuration since installation encountered errors, exit code was 6                                                                                                                        
  Something went wrong! Check the log for ERROR-level output                                                                                                                                                         
  The full log is at /var/log/foreman-installer/foreman-installer.log      



Furthermore:
Attempted to start the foreman-tasks service manually (service foreman-tasks start) - it took too long:
real    5m2.547s
user    0m2.002s
sys     0m0.325s
Comment 3 Omri Hochman 2014-06-26 16:47:01 UTC 
After starting the foreman-tasks service manually (takes 5 minutes..) and rerun rhel-osp-installer   

I'm getting the next error :
--------------------------------  /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[staypuft.lab.eng.rdu2.redhat.com]: Could not evaluate: 500 Internal Server Error  .
Comment 11 Alexander Chuzhoy 2014-08-06 16:45:44 UTC 
Verified: rhel-osp-installer-0.1.6-5.el6ost.noarch



Running rhel-osp-installer results in successful installation.
Comment 12 errata-xmlrpc 2014-08-21 18:04:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1090.html