Deployment fails when multibackend is enabled

Bug #1602541 reported by Stanislav Kolenkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel Plugin Cinder Netapp
New
Undecided
Unassigned

Bug Description

MOS 8.0
Plugin: cinder_netapp 4.1.1

How to reproduced:
1. Configure environment with the following parameters:
1.1 Cinder LVM over iSCSI for volumes - Enable
1.2 Cinder and NetApp integration - Enable
1.3 Enable Multibackend for NetApp plugin
1.4 NetApp Storage Family - Clustered Data ONTAP
1.5 NetApp Storage Protocol - NFS
1.6 Transport Type - https

Below the puppet log from controller node:
2016-07-12 21:12:56 +0000 /Stage[main]/Main/Create_cinder_types[netapp]/Cinder::Type[netapp]/Exec[cinder type-create netapp]/returns (err): change from notrun to 0 failed: cinder type-create netapp returned 1 instead of one of [0]
2016-07-12 21:12:56 +0000 /Stage[main]/Main/Create_cinder_types[netapp]/Cinder::Type[netapp]/Exec[cinder type-create netapp] (info): Evaluated in 11.32 seconds
2016-07-12 21:12:56 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm] (info): Starting to evaluate the resource
2016-07-12 21:12:56 +0000 Exec[cinder type-create volumes_lvm](provider=posix) (debug): Executing check 'cinder type-list | grep -qP '\bvolumes_lvm\b''
2016-07-12 21:12:56 +0000 Puppet (debug): Executing 'cinder type-list | grep -qP '\bvolumes_lvm\b''
2016-07-12 21:12:57 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/unless (debug): ERROR: Service Unavailable (HTTP 503)
2016-07-12 21:12:57 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (debug): Exec try 1/2
2016-07-12 21:12:57 +0000 Exec[cinder type-create volumes_lvm](provider=posix) (debug): Executing 'cinder type-create volumes_lvm'
2016-07-12 21:12:57 +0000 Puppet (debug): Executing 'cinder type-create volumes_lvm'
2016-07-12 21:12:57 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (debug): Sleeping for 5.0 seconds between tries
2016-07-12 21:13:02 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (debug): Exec try 2/2
2016-07-12 21:13:02 +0000 Exec[cinder type-create volumes_lvm](provider=posix) (debug): Executing 'cinder type-create volumes_lvm'
2016-07-12 21:13:02 +0000 Puppet (debug): Executing 'cinder type-create volumes_lvm'
2016-07-12 21:13:02 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (debug): Sleeping for 5.0 seconds between tries
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (notice): ERROR: Service Unavailable (HTTP 503)
2016-07-12 21:13:07 +0000 Puppet (err): cinder type-create volumes_lvm returned 1 instead of one of [0]
/usr/lib/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
/usr/lib/ruby/vendor_ruby/puppet/type/exec.rb:160:in `sync'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:204:in `sync'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:128:in `sync_if_needed'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:89:in `block in perform_changes'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `each'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `perform_changes'
/usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:204:in `apply'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:217:in `eval_resource'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 levels) in evaluate'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:335:in `block in thinmark'
/usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:334:in `thinmark'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in evaluate'
/usr/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
/usr/lib/ruby/vendor_ruby/puppet/transaction.rb:138:in `evaluate'
/usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:169:in `block in apply'
/usr/lib/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination'
/usr/lib/ruby/vendor_ruby/puppet/transaction/report.rb:112:in `as_logging_destination'
/usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:168:in `apply'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:120:in `block in apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:161:in `block in benchmark'
/usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:119:in `apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:227:in `run_internal'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:134:in `block in run'
/usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'
/usr/lib/ruby/vendor_ruby/puppet.rb:244:in `override'
/usr/lib/ruby/vendor_ruby/puppet/configurer.rb:133:in `run'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:302:in `apply_catalog'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:236:in `block in main'
/usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'
/usr/lib/ruby/vendor_ruby/puppet.rb:244:in `override'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:198:in `main'
/usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:159:in `run_command'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:507:in `plugin_hook'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block in run'
/usr/lib/ruby/vendor_ruby/puppet/util.rb:496:in `exit_on_fail'
/usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `run'
/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run'
/usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'
/usr/bin/puppet:8:in `<main>'
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm]/returns (err): change from notrun to 0 failed: cinder type-create volumes_lvm returned 1 instead of one of [0]
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Exec[cinder type-create volumes_lvm] (info): Evaluated in 11.43 seconds
2016-07-12 21:13:07 +0000 Cinder::Type_set[LVM-backend] (info): Starting to evaluate the resource
2016-07-12 21:13:07 +0000 Cinder::Type_set[LVM-backend] (info): Evaluated in 0.00 seconds
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Cinder::Type_set[LVM-backend]/Exec[cinder type-key volumes_lvm set volume_backend_name=LVM-backend] (info): Starting to evaluate the resource
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Cinder::Type_set[LVM-backend]/Exec[cinder type-key volumes_lvm set volume_backend_name=LVM-backend] (notice): Dependency Exec[cinder type-create volumes_lvm] has failures: true
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Cinder::Type_set[LVM-backend]/Exec[cinder type-key volumes_lvm set volume_backend_name=LVM-backend] (warning): Skipping because of failed dependencies
2016-07-12 21:13:07 +0000 /Stage[main]/Main/Create_cinder_types[volumes_lvm]/Cinder::Type[volumes_lvm]/Cinder::Type_set[LVM-backend]/Exec[cinder type-key volumes_lvm set volume_backend_name=LVM-backend] (info): Evaluated in 0.00 seconds

Revision history for this message
Roman Sokolkov (rsokolkov) wrote :

Stanislav, please error from provide /var/log/cinder/cinder-api.log from controllers.

"cinder type-create" failed with error 503 service unavailable, looks like cinder-api failed to start.

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

Other bug subscribers

Remote bug watches

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