Red Hat Bugzilla – Bug 1488804
python-pankoclient is missing in installed packages
Last modified: 2018-02-05 14:12:42 EST
Description of problem: When installing undercloud, get an error message Error: Execution of '/bin/yum -d 0 -e 0 -y install python-pankoclient' returned 1: Error: Nothing to do Error: /Stage[main]/Panko::Client/Package[python-pankoclient]/ensure: change from purged to present failed: Execution of '/bin/yum -d 0 -e 0 -y install python-pankoclient' returned 1: Error: Nothing to do Version-Release number of selected component (if applicable): Build 2017-09-05.9 How reproducible: Always Steps to Reproduce: 1. Try to deploy undercloud with DEFAULT.enable_telemetry=True 2. 3. Actual results: Deployment fails Expected results: No errors Additional info:
Prad, looks like the package is installed on undercloud but the packages does not ship a binary: (overcloud) [stack@undercloud-0 ~]$ rpm -ql python-aodhclient-0.9.0-0.20170814164842.eb82760.el7ost.noarch | grep bin /usr/bin/aodh /usr/bin/aodh-2 /usr/bin/aodh-2.7 (overcloud) [stack@undercloud-0 ~]$ rpm -ql python-pankoclient-0.3.0-1.el7ost.noarch | grep bin (overcloud) [stack@undercloud-0 ~]$
(In reply to Julien Danjou from comment #6) > Prad, looks like the package is installed on undercloud but the packages > does not ship a binary: > > (overcloud) [stack@undercloud-0 ~]$ rpm -ql > python-aodhclient-0.9.0-0.20170814164842.eb82760.el7ost.noarch | grep bin > /usr/bin/aodh > /usr/bin/aodh-2 > /usr/bin/aodh-2.7 > (overcloud) [stack@undercloud-0 ~]$ rpm -ql > python-pankoclient-0.3.0-1.el7ost.noarch | grep bin > (overcloud) [stack@undercloud-0 ~]$ Thats expected in 0.3.0, use 'openstack event ' command instead. The upstream version dint have a binary when we packaged this.
You're right and there's no more recent version than 0.3.0 anyway, so we're good.
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:3462