Bug 1485741 - upgrade from 5.6 to 5.8 db:rake error
Summary: upgrade from 5.6 to 5.8 db:rake error
Keywords:
Status: CLOSED DUPLICATE of bug 1414815
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.8.0
Hardware: All
OS: All
unspecified
high
Target Milestone: GA
: 5.8.2
Assignee: Gregg Tanzillo
QA Contact: luke couzens
URL:
Whiteboard: black:upgrade:migration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-27 22:15 UTC by Ryan Spagnola
Modified: 2023-09-14 04:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-04 20:38:57 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Spagnola 2017-08-27 22:15:04 UTC
Description of problem:
When customer runs the rake db:migrate command they get the following: 

[root@hen-cf4-db vmdb]# rake db:migrate
Could not find nokogiri-1.7.2 in any of the sources
Run `bundle install` to install missing gems.
[root@hen-cf4-db vmdb]# ^C
[root@hen-cf4-db vmdb]# ^C
[root@hen-cf4-db vmdb]# bundle install
/opt/rh/rh-ruby23/root/usr/bin/ruby: error while loading shared libraries: libruby.so.2.3: cannot open shared object file: No such file or directory
[root@hen-cf4-db vmdb]#

Version-Release number of selected component (if applicable):
migrate from 5.6 to 5.8.1

How reproducible:
this occured on one of the appliances so far

Steps to Reproduce:
1. run rake db:migrate during upgrade process
2.
3.

Actual results:


Expected results:
db is imported

Additional info:
Informed customer to run yum reinstall cfme-gemset
after doing so they are still getting errors with connecting to the db

Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1414815#c18

Comment 2 Gregg Tanzillo 2017-08-28 03:00:19 UTC
Ryan,

You can try reinstalling all the cfme repos -

yum reinstall cfme-appliance.x86_64 
yum reinstall cfme.x86_64 
yum reinstall cfme-gemset.x86_64

I rand into this issue a while back and that fixed it.

Comment 4 Yuri Rudman 2017-10-04 20:38:57 UTC

*** This bug has been marked as a duplicate of bug 1414815 ***

Comment 5 Red Hat Bugzilla 2023-09-14 04:06:58 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.