Description of problem: openstack-rally-0.1.1-4.1.el7ost is working fine and because you have removed the post install script, openstack-rally-0.1.1-4.2.el7ost is not able to make the sqllite connection which in turn is breaking the entire rally rpm. Version-Release number of selected component (if applicable): openstack-rally-0.1.1-4.2.el7ost How reproducible: Everytime Steps to Reproduce: #rally deployment list Actual results: (sqlite3.OperationalError) no such table: deployments [SQL: u'SELECT deployments.enum_deployments_status AS deployments_enum_deployments_status, deployments.created_at AS deployments_created_at, deployments.updated_at AS deployments_updated_at, deployments.id AS deployments_id, deployments.uuid AS deployments_uuid, deployments.parent_uuid AS deployments_parent_uuid, deployments.name AS deployments_name, deployments.started_at AS deployments_started_at, deployments.completed_at AS deployments_completed_at, deployments.config AS deployments_config, deployments.admin AS deployments_admin, deployments.users AS deployments_users \nFROM deployments \nWHERE deployments.parent_uuid IS NULL'] Looks like Rally can't connect to it's DB. Make a sure that connection string in rally.conf is proper: sqlite:////tmp/rally.sqlite Expected results: There are no deployments. To create a new deployment, use: rally deployment create Additional info:
No config file is installed and the sample config file does not have a connection string either. current version of package is openstack-rally-0.1.1-4.2.el7ost to customize the config for an sqlite DB copy /etc/rally/rally.conf.sample to /etc/rally/rally.conf modify the config file to include see bug 1155128 for details on how to manually configure and generate the DB
on my test VM: I added connection entry to /etc/rally/rally.conf from /etc/rally/rally.conf.sample cp /etc/rally/rally.conf.sample /etc/rally/rally.conf add the following to /etc/rally/rally.conf connection = sqlite:////var/lib/rally/rally.sqlite then make the directory mkdir -p /var/lib/rally/ rally-manage db recreate # rally deployment list There are no deployments. To create a new deployment, use: rally deployment create
This is the intended behavior as noted above in comment 2 and comment 3
Hey Jon, So it means "openstack-rally-0.1.1-4.2.el7ost" rpm is unusable if you do a plain "yum install openstack-rally" and it would require the customer/partner to manually go through steps mentioned in comment 3. Does the RHELOSP team have official documentation for the steps mentioned in comment 3 which our customers/partners can follow?
Openstack-rally is TechPreview in OSP 8 - I don't know that documentation for what steps are needed to make rally work out of the box with a simple yum install. That should be on the list of items to get completed before GA. but what is configured and what is enabled and how you use rally needs to be customized for your installation. Please follow up on bug 1155128 if we have additional needs.