Description of problem:
Customer deployed a RHEL VM on Red Hat Openstack (already installed and working). Now inside the RHEL guest, customer is willing to install the Openstack **client** tool (cmdline neutron, nova) to interact with OSP APIs.
The issue is that after installing the cmdline tools (via yum install python-openstackclient inside a container) in that RHEL guest, the tools fail to work due a missing dependecy (package "which").
The goal is to include which as a dependency for python-cmd2.
$ rpm -qf /usr/lib/python2.7/site-packages/openstackclient/shell.py
$ rpm -qf /usr/lib/python2.7/site-packages/cmd2.py
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This issue is very low priority since the workaround is extremely simple (yum install which) and the chances of hitting this are remote (grub2 requires which, so almost *any* system would have the package).
Our version of python-cmd2 is a repackage of the version in the RDO community (which is in turn a repackage of the fedora version) so cloning this around for tracking in those systems.
(In reply to Mike Burns from comment #1)
> This issue is very low priority since the workaround is extremely simple
> (yum install which) and the chances of hitting this are remote (grub2
> requires which, so almost *any* system would have the package).
> Our version of python-cmd2 is a repackage of the version in the RDO
> community (which is in turn a repackage of the fedora version) so cloning
> this around for tracking in those systems.
In this case, the issue raised when the commands for managed were installed inside a container, so not really sure about the grub dependency to be satisfied there.
Even if it has a simple workaround, wouldn't it be also very simple to declare that dependency as the RPM do really require that package to be installed?
Once that's done in the .spec for OSP 7 that this bz was reported against, it should be easy to have the fix on any rpm built after it.
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.