list datasource fails if Driver could not be loaded

[Anusha]

If any driver fails to load, all other drivers are failed to list. So, at congress startup, it should fail instead if any Driver could not be loaded. One case, it occurs if any change done to config file ENABLED_DRIVERS section. These cases to be properly handled.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/329772
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=10475c534dca335d60f6d9323d8b04fef04b8ad3
Submitter: Jenkins
Branch: master

commit 10475c534dca335d60f6d9323d8b04fef04b8ad3
Author: Anusha Ramineni <email address hidden>
Date: Tue Jul 26 16:03:49 2016 +0530

    Exit if datasource could not be loaded

    This commit exits code, if any datasource driver could not be loaded
    and also provides a new option --delete_missing_driver_datasources to be
    specified while starting congress server, to cleanup any stale datasources
    from database.

    Eg: /usr/local/bin/congress-server --config-file /etc/congress/congress.conf --delete_missing_driver_datasources

    Closes-Bug: #1606523
    Change-Id: Iee260b0d4204ece6b8347d1fe578cbc52d9ccc57

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/congress 4.0.0.0b3 development milestone.