3par does not return the encrypted flag from initialize_connection

[Anthony Lee]

3PAR does not include the 'encrypted' property for iSCSI and FC from the dictionary returned when initialize_connection is called.

The encrypted flag is later used when attaching encrypted volumes which is being skipped currently because the flag is never present.

The result of this bug is that a volume labeled as encrypted is being treated as unencrypted.

The solution is to return the property in the dictionary created in 3PAR iSCSI and FC's initialize_connection method.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/170346

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/170346
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=cbc67e012ad5f9234ea34a37e6240d608508da86
Submitter: Jenkins
Branch: master

commit cbc67e012ad5f9234ea34a37e6240d608508da86
Author: Anthony Lee <email address hidden>
Date: Thu Apr 2 22:07:27 2015 -0700

    Fixed encrypted property for 3PAR FC and iSCSI drivers

    3PAR FC and iSCSI drivers were not returning the 'encrypted'
    property when initialize_connection was called. This patch
    adds that property to the returned info.

    Closes-Bug: #1439917
    Change-Id: Icfbebd055ea1bae1fc4749b441eb4f90fa1bfacd