Bug 1468376
Summary: | upgrade to CF 4.5 complains about "could not find nokogiri-1.6.8" during "rake db:migrate" | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Ryan Spagnola <rspagnol> |
Component: | Build | Assignee: | Satoe Imaishi <simaishi> |
Status: | CLOSED ERRATA | QA Contact: | luke couzens <lcouzens> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.8.0 | CC: | abellott, gtanzill, jhardy, lcouzens, mfeifer, myoder, obarenbo, rspagnol, sacpatil, simaishi |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.8.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | black:upgrade:migration | ||
Fixed In Version: | 5.8.1.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-02 17:33:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Bug | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: |
Description
Ryan Spagnola
2017-07-06 21:24:32 UTC
Hey Ryan, Is there any extra info you could give on this? I have tried on 6 appliances now and none are seeing this issue. What version did you update to 5.8.1.0? Thanks, Luke Hey Luke, We have no problem upgrading from 5.7.2 to 5.8.0. The problem is only going from 5.7.3 to 5.8.0. 5.7.3 seems to install this as a prereq: rh-ruby23-rubygem-nokogiri-1.7.2-1.el7cf.x86_64 But, 5.8.0 has a lower version. rh-ruby23-rubygem-nokogiri-1.6.8-1.el7cf.x86_64 Best, Yoder Hi Yoder, I see the same thing now on 5.7.3.2 to 5.8.0.17. Originally I was testing 5.7.3.2 - 5.8.1 as the bz just said 5.8.z, so thanks for the clarification. *** Bug 1469015 has been marked as a duplicate of this bug. *** The workaround is to run "yum downgrade rh-ruby23-rubygem-nokogiri-1.6.8-1.el7cf.x86_64" after "yum update". Verified in 5.8.1.2 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. https://access.redhat.com/errata/RHSA-2017:1758 |