Description of problem: Version-Release number of selected component (if applicable): How reproducible: install according to the latest RDO https://www.rdoproject.org/RDO_test_day_Kilo#How_To_Test Steps to Reproduce: 1. run packstack with allinone 2. 3. Actual results: packstack failed on installation of openstack-cinder. You will need to edit the answerfile and enable epel (CONFIG_USE_EPEL=y) Expected results: packstack runs smoothly Additional info: Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 10.35.117.2_cinder.pp Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-cinder' returned 1: Error: Package: python-cinder-2015.1.0-2.el7.noarch (openstack-kilo-testing) You will find full trace in log /var/tmp/packstack/20150505-105735-7dDI34/manifests/10.35.117.2_cinder.pp.log and: # /usr/bin/yum -d 0 -e 0 -y install openstack-cinder Error: Package: python-cinder-2015.1.0-2.el7.noarch (openstack-kilo-testing) Requires: python-cheetah You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Packstack detects if it is installing RDO by checking if a package called rdo-release-* is installed. For the testing day, the package was called rdo-testing-kilo, so it was not detected. I doubt if we should consider this as NOTABUG (it will only happen in these cases), or we should find a better way to detect RDO. Any ideas?
With RDO >= Kilo EPEL will not be required, we'll carry CloudSIG EPEL rebuilds in RDO repo. Also in this case, EPEL will not help, this is an issue with segmented RHEL repos, python-cheetah is in rh-common. I'll try to handle RHEL specific repos in rdo-release|testing repos, so that Packstack doesn't need to have any special handling.
Exact names of RHEL repos which need to be enabled are: rhel-7-server-optional-rpms rhel-7-server-extras-rpms rhel-7-server-rh-common-rpms
subscription-manager repos --enable rhel-7-server-optional-rpms --enable rhel-7-server-extras-rpms --enable rhel-7-server-rh-common-rpms
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.