+++ This bug was initially created as a clone of Bug #1726325 +++
Description of problem:
We would like to upgrade facter to facter3 to improve performance. See Bug 1711267
Packages have been built upstream https://review.rdoproject.org/r/#/c/21311/. We'll likely need the facter package & and it's dependencies as well as a puppet version bump with a dependency to require ruby-facter.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Alfredo Moralejo on 2019-07-05 12:59:55 UTC ---
New deps and a change in puppet is needed to make it depend on ruby-facter. Change in RDO for Rocky https://review.rdoproject.org/r/#/c/21311/
--- Additional comment from Alex Schultz on 2019-07-08 15:36:57 UTC ---
We'll need to make sure that we have the fix for https://bugs.launchpad.net/tripleo/+bug/1812938 before updating as well.
Following changes have been done in RDO Rocky to rebase facter to 3.9.3:
Added as runtime deps:
Special care needed for boost. Fedora and CentOS/RDO uses versioned name, boost159, etc... while RHEL uses just "boost" so specs man need to be fixed.
Following packages must be pushed together:
puppet-tripleo >= 8.4.1-16.el7ost
Note that this update should also be coordinated with OSP14 one in https://bugzilla.redhat.com/show_bug.cgi?id=1726325
Looks like we also need yaml-cpp-0.5.1-6.el7.x86_64.rpm
(In reply to Alex Schultz from comment #10)
> Looks like we also need yaml-cpp-0.5.1-6.el7.x86_64.rpm
yaml-cpp-0.5.1-8.el7ost.x86_64.rpm is already in the OSP13 and 14 repos. I tested the builds with it.
@steve, is there any problem with having a list of packages in fixed in?, iiuc, it should work.
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.
If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
*** Bug 1749885 has been marked as a duplicate of this bug. ***
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.