Comment 4 for bug 1215064

Reviewed: https://review.openstack.org/43526
Committed: http://github.com/openstack/cinder/commit/3329158d784d5966fa2fdccd1c097295ebe37a67
Submitter: Jenkins
Branch: stable/grizzly

commit 3329158d784d5966fa2fdccd1c097295ebe37a67
Author: John Griffith <email address hidden>
Date: Wed Aug 21 13:05:30 2013 -0600

    Dont crash service if sf cluster isnt available

    Currently if the SolidFire driver is configured but the cluster
    isn't available for some reason the ensure_export call will raise
    an unhandled exception and crash the volume-service.

    We should be able to handle things like loosing connectivity to
    a single back-end without impacting the other volume-service
    backends.

    We'll wrap the ensure_export call in a try block here and
    return None in the case that the connection can't be made.
    This will keep the service from crashing and log an error
    message that the connection timed out.

    Additional work would include adding a periodic retry task
    to the manager to try and start the backend service for us
    on some regular interval incase the device comes back.

    Fixes: bug 1215064

    Change-Id: Ice3f517d220c40113074bb77adbb10d5e32abd0b
    (cherry picked from commit e13b7d8a46cd54e61bdc20500ad597c2545ffaed)