I get a new missing dep - this time I've enabled epel end epel-testing manually: ERROR : Error during puppet run : err: /Stage[main]/Nova/Package[python-nova]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install python-nova' returned 1: Error: Package: python-nova-2013.2-0.19.b3.el6.noarch (openstack-havana) # yum install python-nova Loaded plugins: product-id, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package python-nova.noarch 0:2013.2-0.19.b3.el6 will be installed --> Processing Dependency: python-pyasn1 for package: python-nova-2013.2-0.19.b3.el6.noarch --> Processing Dependency: python-neutronclient for package: python-nova-2013.2-0.19.b3.el6.noarch --> Processing Dependency: python-jinja2 for package: python-nova-2013.2-0.19.b3.el6.noarch --> Processing Dependency: python-boto for package: python-nova-2013.2-0.19.b3.el6.noarch --> Running transaction check ---> Package python-boto.noarch 0:2.9.9-2.el6 will be installed ---> Package python-neutronclient.noarch 0:2.3.0-1.el6 will be installed --> Processing Dependency: python-cliff >= 1.0 for package: python-neutronclient-2.3.0-1.el6.noarch --> Processing Dependency: pyparsing for package: python-neutronclient-2.3.0-1.el6.noarch ---> Package python-nova.noarch 0:2013.2-0.19.b3.el6 will be installed --> Processing Dependency: python-jinja2 for package: python-nova-2013.2-0.19.b3.el6.noarch ---> Package python-pyasn1.noarch 0:0.0.12a-1.el6 will be installed --> Running transaction check ---> Package pyparsing.noarch 0:1.5.6-1.el6 will be installed ---> Package python-cliff.noarch 0:1.3-1.el6 will be installed --> Processing Dependency: python-cmd2 for package: python-cliff-1.3-1.el6.noarch ---> Package python-nova.noarch 0:2013.2-0.19.b3.el6 will be installed --> Processing Dependency: python-jinja2 for package: python-nova-2013.2-0.19.b3.el6.noarch --> Running transaction check ---> Package python-cmd2.noarch 0:0.6.4-7.el6 will be installed ---> Package python-nova.noarch 0:2013.2-0.19.b3.el6 will be installed --> Processing Dependency: python-jinja2 for package: python-nova-2013.2-0.19.b3.el6.noarch --> Finished Dependency Resolution Error: Package: python-nova-2013.2-0.19.b3.el6.noarch (openstack-havana) Requires: python-jinja2 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -------- Original Message -------- Subject: [Rdo-list] havana-test-day: installation with packstack fails Date: Wed, 11 Sep 2013 11:30:08 +0300 From: Rami Vaknin <rvaknin(a)redhat.com&gt; Reply-To: rvaknin(a)redhat.com Organization: Red Hat To: rdo-list(a)redhat.com I'm trying to install rdo havana on rhel 6.4, I've followed the instructions in http://openstack.redhat.com/QuickStartLatest, it seems that packstack's answer file with "CONFIG_USE_EPEL=y" on a machine without prior epel repo file does not set an epel repo well, and as a result packstack fails with the following error: /# packstack --allinone --os-neutron-install=y --debug// //...// //ERROR : Error during puppet run : err: /Stage[main]/Keystone/Package[keystone]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-keystone' returned 1: Error: Package: python-keystone-2013.2-0.5.b2.el6.noarch (openstack-havana)/ Another issue I've came across - packstack tries to access a glance conf file in a stage where openstack-glance is not yet installed, probably happens only when changing Neutron-related (why?) configurations in packstack's answer file: /ERROR : Error during puppet run : err: /Stage[main]//Glance_api_config[DEFAULT/notifier_strategy]/ensure: change from absent to present failed: Could not set 'present on ensure: No such file or directory - /etc/glance/glance-api.conf at /var/tmp/packstack/8da55081f3a447b1bd84d3451faaa36f/manifests/10.35.160.29_cinder.pp:43/ -- Thanks, Rami Vaknin, QE @ Red Hat, TLV, IL.

On 09/11/2013 09:30 AM, Rami Vaknin wrote: What do you mean by "not set well". Do you mean epel was already installed but disabled? If that's the case then I've noted it at: https://bugzilla.redhat.com/974971 I submitted https://bugzilla.redhat.com/1006816 thanks, Pádraig.

On 09/11/2013 11:48 AM, Rami Vaknin wrote: OK so I presume you rm'd the epel repo file rather than removing the epel-release package. It would be good for packstack to actually inspect the epel repo to detect such manglement. thanks, Pádraig.