NetApp deployment error: Failed to deploy plugin cinder_netapp-1.0.0

Bug #1449943 reported by Fabrizio Soppelsa
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel Plugins
New
Undecided
Fuel Plugin NetApp

Bug Description

6.0
HA

[430] Error running RPC method deploy: Failed to deploy plugin cinder_netapp-1.0.0, trace:
["/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/nailgun_hooks.rb:48:in `block in process'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/nailgun_hooks.rb:25:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/nailgun_hooks.rb:25:in `process'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/deployment_engine.rb:79:in `deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/orchestrator.rb:270:in `deploy_cluster'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/orchestrator.rb:35:in `deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/dispatcher.rb:59:in `deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/server.rb:142:in `dispatch_message'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/server.rb:103:in `block in dispatch'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/task_queue.rb:64:in `call'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/task_queue.rb:64:in `block in each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/server.rb:101:in `each_with_index'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/server.rb:101:in `dispatch'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.0.0/lib/astute/server/server.rb:85:in `block in perform_main_job'"]

Tried with and without check Multibackend but same error.

Tags: netapp
Revision history for this message
Fabrizio Soppelsa (fsoppelsa) wrote :

User comment:

I have try also this procedure but nothing, don't work.

I have verification that in cinder.conf i cannot found this comment:

enabled_backends=cinder_netapp

Maybe this feature it's not implemented??

https://github.com/stackforge/fuel-plugin-cinder-netapp

Maybe we have found a bug. When i set a password for NetApp that start with a special character for example $ we have a problem for connection ti nfs share. I must double the character.

See question https://answers.launchpad.net/fuel/+question/265799

Changed in fuel-plugins:
assignee: nobody → Dmitry Ukov (dukov)
tags: added: netapp
Changed in fuel-plugins:
assignee: Dmitry Ukov (dukov) → Fuel Plugin NetApp (fuel-plugin-cinder-netapp)
Revision history for this message
sbartel (samuel-bartel) wrote :

multi backend feature is not implemented (as specified in the settings tabs but may be we should remove it in order to avoid more confusion for now)

Revision history for this message
mario (mariocastronovo) wrote :

Hi Samuel, i try also to uncheck multibackend but i receive the same error. If i don't use multibackend how to use the cinder volume with NetApp?

I must enable one controller node as storage server with cinder, correct? In this case i must enable the multibackend with manual configuration?

The NetApp plugin configure this parameter "netapp_storage_family" with generic ONTAP instead i must use "ontap_7mode"

Thanks

Mario

Revision history for this message
sbartel (samuel-bartel) wrote :

Hi mario,

in the actual plugin implementation, when you enable netapp plugin, netapp volume will be used instead of the lvm default configuration so there is no need of manual configuration.

moreove, the plugin actually only support cluster mode: 7_mode and e_series are not yet supported (bug https://bugs.launchpad.net/fuel/+bug/1405186). it is on going but i have still some issues with the e-series partvalidation as netapp moved from DataOnapp appliance to Santricity

regards

Samuel

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.