I believe this is a problem in the Nexenta driver and not in the task-flow (or at least a compatibility between the two). It appears that your discover address is not being set correctly, I wonder if it's possible that you're model update or export methods are wrong?
Have you tried attaching a nexenta volume to an instance and compared the provider info?
I've run a number of tests with LVM and SolidFire and have not seen any issues leading me to believe there's something specific with the Nexenta driver.
I believe this is a problem in the Nexenta driver and not in the task-flow (or at least a compatibility between the two). It appears that your discover address is not being set correctly, I wonder if it's possible that you're model update or export methods are wrong?
Have you tried attaching a nexenta volume to an instance and compared the provider info?
I've run a number of tests with LVM and SolidFire and have not seen any issues leading me to believe there's something specific with the Nexenta driver.