If the user doesn't specify the connection on the tuskar config we throw an unhelpful error

Bug #1359654 reported by Dougal Matthews on 2014-08-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tuskar
Medium
Unassigned

Bug Description

The error currently looks like this:

    $ tuskar-dbsync --config-file etc/tuskar/tuskar.conf.sample
    2014-08-21 10:51:05.636 31110 CRITICAL tuskar [-] AttributeError: 'NoneType' object has no attribute 'drivername'

The only thing you need to change in the sample config (at the moment) is the connection= parameter.

We should at least make the error a bit more self explanitory - this may be something that needs to be fixed in oslo.db

Dougal Matthews (d0ugal) on 2014-09-12
Changed in tuskar:
importance: Undecided → Medium
status: New → Confirmed
Dougal Matthews (d0ugal) on 2014-09-25
Changed in tuskar:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers