Red Hat Bugzilla – Bug 1411809
Error while evaluating a Function Call, uninitialized constant RGen::ECore::ELong during upgrade to RHOS-11
Last modified: 2017-07-05 15:44:56 EDT
Created attachment 1239124 [details] Undercloud upgrade log Description of problem: ----------------------- Attempt to upgrade undercloud from RHOS-10 to RHOS-11 fails with next message: Error: Evaluation Error: Error while evaluating a Function Call, uninitialized constant RGen::ECore::ELong at /etc/puppet/manifests/puppet-stack-config.pp:17:1 on node undercloud-0.redhat.local Version-Release number of selected component (if applicable): ------------------------------------------------------------- puppet noarch 4.6.2-2.el7 Steps to Reproduce: 1. Upgrade from RHOS-9 to RHOS-10 2. Try to upgrade undercloud from RHOS-10 to RHOS-11: openstack undercloud upgrade Actual results: --------------- Upgrade fails Expected results: ----------------- Undercloud is upgraded
Hi, Puppet is upgraded to version >4. It now includes its own rgen lib. But there is some package leftover on rhel plateform that breaks puppet, namely ruby-rgen-0.6.5-2.el7sat.noarch. You have to run this before the undercloud upgrade for puppet to continue to work. sudo rpm -e --nodeps ruby-rgen-0.6.5-2.el7sat.noarch Not sure what is the best course of action here. Do we : - improve packaging to make sure this one is absent (or conflict); - integrate it in python-tripleoclient; - do a documentation resolution;
It looks like the best course of action is to add the Obsoletes: ruby-rgen in the puppet spec file. Courtesy of mburns. Waiting for a package to test.
Yes, obsoletes is fine here. The 'ruby-rgen' package appears to have been built specifically for puppet a few years ago, and sort of does a strange unpack/repack of the rgen gem. Thus, Obsoletes: should be fine. rubygem-rgen should be used by other apps (if needed).
Hi, so could we have the package here, so that we can exclude the issue from what edannon is seeing ? Adjusting the status. Thanks.
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/RHEA-2017:1245