Description of problem:appliance upgrade failing on db migrate due to ruby failure over gem package Version-Release number of selected component (if applicable):5.9.1.1 How reproducible: 100% Steps to Reproduce: 1.provision 5.8.3.2 2.add latest repos for 5.9.1.1 3.stop evmserverd 4.run yum update 5.run any ruby command Actual results: rake db:migrate Could not find psych-2.0.17 in any of the sources Run `bundle install` to install missing gems. Expected results: rake db:migrate and other rake tasks work correctly. Additional info: Repo with problem gem package http://pulp-read.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/ Package upgraded to rh-ruby23-rubygem-psych-2.1.0.1-67.el7.x86_64.rpm
rh-ruby23 was updated from 2.3.1 to 2.3.6 in Software Collection, along with its dependent packages including rubygem-psych. This resulted CFME upgrade to pick up a newer version of rubygem-psych than what we expected, causing the error.
https://github.com/ManageIQ/manageiq/pull/17203
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/3c74c05f423dac3bcf77478dc972c177a950c6e8 commit 3c74c05f423dac3bcf77478dc972c177a950c6e8 Author: Joe Rafaniello <jrafanie> AuthorDate: Mon Mar 26 11:07:15 2018 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Mon Mar 26 11:07:15 2018 -0400 Update to 2.3.6 on euwe. :sweat_smile: We previously tried to upgrade to 2.3.6 on euwe by backporting: https://github.com/ManageIQ/manageiq/pull/15993 This was causing a hang in the automation test suite on euwe and we reverted it in: https://github.com/ManageIQ/manageiq/pull/16087 https://bugzilla.redhat.com/show_bug.cgi?id=1560578 The prior 2 commits contain a manual backport of https://github.com/ManageIQ/manageiq/pull/14239 which solves the 100% cpu hang of the automate ruby method with ruby 2.3.2+. .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 1562454 has been marked as a duplicate of this bug. ***
Verified in 5.9.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/RHBA-2018:0556
*** Bug 1563588 has been marked as a duplicate of this bug. ***