Description of problem:
After an undercloud installation, the tuskar api service is not set up properly. The connection string is not set in the [database] section of /etc/tuskar/tuskar.conf. It is blank.
This causes a 500 error when called from the tuskarclient. tuskar-dbsync also throws an error (this is returned by the api to the client as well)
CRITICAL tuskar [-] ArgumentError: Could not parse rfc1738 URL from string ''
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Follow sphinx documents to install the undercloud.
2. Try to do any operation on the tuskar api.
Database not configured for tuskar
Database configured for tuskar
I have done some investigation here. Things started breaking here: https://github.com/rdo-management/instack-undercloud/commit/6f75c8dc3c37d489763b7310a7b57d00e1e70da2
Problem is that the info for tuskar was removed from elements/undercloud-stack-config/config.json.template.
So, I am working on implementing the necessary puppet to bring this in properly.
i put up a patch to correct this:
but that will conflict with the puppet work you're doing, so just let me know if you want me to hold off on merging it
I've now submitted a few patches to enable this:
puppet-tuskar - https://review.openstack.org/#/c/169072/
tripleo-puppet-elements - https://review.openstack.org/#/c/169070/
tuskar-packaging - https://review.gerrithub.io/#/c/228840/
instack-undercloud - https://review.gerrithub.io/#/c/228909/
We should go for slagle's patch for now. There is more work to be done on the puppet to have feature parity with the tripleo tuskar element.
Moving to MODIFIED; I just tested it on a new instack install and it works correctly.
Verified in puddle 2015-06-02 and openstack-tuskar-2013.2.0-dev2.el7.centos.noarch
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.