Fuel for OpenStack

NetApp Plugin error

Asked by mario

When i deploy Openstack with NetApp plugin i receive the following errors:

[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'"]

I have tried with and without check Multibackend but i receive the same error.

Thanks

Mario

Question information

Language:
English Edit question
Status:
Answered
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#1

Mario, this is a bit generic problem description, do you have the full trace?

A snapshot would be even better.
I am filing a bug to the Fuel Plugins team. You will find the bug ID in the Related bugs section.

Best regards,
Fabrizio

Revision history for this message
mario (mariocastronovo) said : 		#2

Hi Fabrizio, in this link you can found the last diagnostic los

https://drive.google.com/open?id=0B7mHbSWW-vvyQXhJN2ZfSlJyTWs&authuser=0

Thanks

Mario

Revision history for this message
mario (mariocastronovo) said : 		#3

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

Revision history for this message
mario (mariocastronovo) said : 		#4

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.

Thanks

Mario

Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#5

Mario, thank you for reporting your findings.
Starting from now, can you please continue the discussion on the bug page? I will copypaste the content there.

Fabrizio

Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#6

Mario, have you found any useful progression in the linked bug/1449943 from our developers?

Best,
Fabrizio
Mirantis Fuel Team

Revision history for this message
mario (mariocastronovo) said : 		#7

Hi Fabrizio, i try to deploy an environment with NetApp plugin uncheck the multibackend and don't use Cinder LVM over iSCSI (i don't check the Cinder Roles on the compute host) but i received the same error.

In this moment i choose to use the NetApp nfs manually.

Thanks

Mario

Can you help with this problem?

Provide an answer of your own, or ask mario for more information if necessary.

To post a message you must log in.