Deploy Failed When Running "odl-service.pp" for OPNFV-Brahmaputra by FUEL-8.0

Bug #1627648 reported by ck tsai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Michal Skalski

Bug Description

Control node openstack installation stuck when running "odl-service.pp", deploying opnfv by FUEL-8.0.

There I established 3 nodes:
  Fuel Master Node
  1 Control Node
  1 Compute Node

These nodes are all virtual machines which created in VMWare Workstation 12.
For Fuel Master Node there is a NAT environment: 10.20.0.0/24.
And for both Control & Compute Node there are 2 NAT environments connected: 10.20.0.0/24 & 172.16.0.0/24.

Deployment stops at "Installing Openstack 100%" stage, astute log with err level is as following:
-----------------------------------------------------------------------------
2016-09-26 04:39:36 ERROR [429] Error running RPC method granular_deploy: Deployment failed on nodes 9, trace:
["/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:68:in `block (3 levels) in deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:51:in `each_slice'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:51:in `block (2 levels) in deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:49:in `each'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:49:in `block in deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:45:in `each'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/deployment_engine.rb:45:in `deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/orchestrator.rb:216:in `deploy_cluster'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/orchestrator.rb:52:in `granular_deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/dispatcher.rb:92:in `granular_deploy'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:189:in `dispatch_message'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:146:in `block in dispatch'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/task_queue.rb:64:in `call'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/task_queue.rb:64:in `block in each'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:144:in `each_with_index'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:144:in `dispatch'",
 "/usr/share/gems/gems/astute-8.0.0/lib/astute/server/server.rb:123:in `block in perform_main_job'"]
2016-09-26 04:39:36 ERROR [429] No more tasks will be executed on the node 9
2016-09-26 04:39:36 ERROR [429] Task '{"priority"=>3300, "type"=>"puppet", "id"=>"odl_configure", "parameters"=>{"puppet_modules"=>"puppet/modules:/etc/puppet/modules", "puppet_manifest"=>"puppet/manifests/odl-service.pp", "timeout"=>1400, "cwd"=>"/etc/fuel/plugins/opendaylight-0.8/"}, "uids"=>["9"]}' failed on node 9
-----------------------------------------------------------------------------

And puppet log with err level is as following:
-----------------------------------------------------------------------------
2016-09-26 04:44:29 ERR (/Stage[main]/Opendaylight::Service/Exec[wait-until-odl-ready]/returns) change from notrun to 0 failed: curl -o /dev/null --fail --silent --head -u admin:admin http://192.168.0.2:8282/restconf/operational/network-topology:network-topology/topology/netvirt:1 returned 22 instead of one of [0]
2016-09-26 04:44:08 ERR /usr/bin/puppet:8:in `<main>'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:496:in `exit_on_fail'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block in run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:507:in `plugin_hook'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block (2 levels) in run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:159:in `run_command'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:198:in `main'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet.rb:244:in `override'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:236:in `block in main'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:302:in `apply_catalog'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:133:in `run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet.rb:244:in `override'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/context.rb:64:in `override'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:134:in `block in run'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:227:in `run_internal'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:119:in `apply_catalog'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:160:in `benchmark'
2016-09-26 04:44:08 ERR /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:161:in `block in benchmark'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/configurer.rb:120:in `block in apply_catalog'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:168:in `apply'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/report.rb:112:in `as_logging_destination'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util/log.rb:149:in `with_destination'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:169:in `block in apply'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:138:in `evaluate'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in evaluate'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:334:in `thinmark'
2016-09-26 04:44:08 ERR /usr/lib/ruby/1.9.1/benchmark.rb:295:in `realtime'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:335:in `block in thinmark'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 levels) in evaluate'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'
2016-09-26 04:44:08 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:217:in `eval_resource'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction.rb:204:in `apply'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `perform_changes'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `each'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:89:in `block in perform_changes'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:128:in `sync_if_needed'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:204:in `sync'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/type/exec.rb:160:in `sync'
2016-09-26 04:44:07 ERR /usr/lib/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
2016-09-26 04:44:07 ERR curl -o /dev/null --fail --silent --head -u admin:admin http://192.168.0.2:8282/restconf/operational/network-topology:network-topology/topology/netvirt:1 returned 22 instead of one of [0]
-----------------------------------------------------------------------------

Also warning messages like:
-----------------------------------------------------------------------------
2016-09-26 04:18:23 WARNING You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 8 in file /etc/puppet/modules/haproxy/manifests/balancermember/collect_exported.pp
-----------------------------------------------------------------------------
keeps showing up.

Please help me with this, thanks.

Revision history for this message
ck tsai (hotsizle) wrote :
Revision history for this message
ck tsai (hotsizle) wrote :
Revision history for this message
ck tsai (hotsizle) wrote :
Revision history for this message
ck tsai (hotsizle) wrote :
Revision history for this message
ck tsai (hotsizle) wrote :
Revision history for this message
ck tsai (hotsizle) wrote :

The snapshot file is so large that server keeps return time out message. So I cut the snapshot file into 5 parts.

description: updated
Changed in fuel:
assignee: nobody → MOS Maintenance (mos-maintenance)
milestone: none → 8.0-mu-4
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Michal, could you please take a look at the issue?

Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Michal Skalski (mskalski)
milestone: 8.0-mu-4 → 8.0-updates
importance: Undecided → High
Revision history for this message
Michal Skalski (mskalski) wrote :

Hello,

odl-service.pp manifest is responsible for checking if ODL is fully initialized. In this case ODL was not able to start. As I see for node-9 where OpenDaylight role is assigned only 2GB of RAM is allocated, it's not enough, it should be around 7-8 GB because ODL easily consume such amount of memory. As you can see in snapshot dmesg.txt file from node-9, node was out of memory.

I also suggest to use newer release if possible: https://www.opnfv.org/colorado

In case of future bugs please report them here: https://bugs.launchpad.net/fuel-plugin-opendaylight/+filebug I know that plugin's readme file does not point there, I will fix that.

Changed in fuel:
status: New → Invalid
Revision history for this message
ck tsai (hotsizle) wrote :

Thanks Michal.

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.