Error running RPC method deploy: Internal error. Check: ["1", "3"], passed ["1"]

Bug #1349733 reported by Anastasia Palkina on 2014-07-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Critical
Vladimir Sharshov

Bug Description

"build_id": "2014-07-28_02-01-14",
"ostf_sha": "8c328521b1444f22c50463b9432193e20ed33813",
"build_number": "366",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "83cc9ed44ebc8dd97248483b6d414ebbc4cff3c0",
"production": "docker",
"fuelmain_sha": "9adfbf5a52cedbdd16ec1a74f6c44c5b3419b87c",
"astute_sha": "aa5aed61035a8dc4035ab1619a8bb540a7430a95",
"feature_groups": ["mirantis"],
"release": "5.1",
"fuellib_sha": "d1c7f67b3cf51978d3178c8666ea398f2477dcb5"

1. Create new environment (Ubuntu, HA mode)
2. Choose GRE segmentation
3. Add 3 controllers+cinder, 1 compute
4. Start deployment. It fas failed
5. There is error in astute.log after compute deployment:

2014-07-28 17:52:45 ERR

[392] Error running RPC method deploy: Internal error. Check: ["1", "3"], passed ["1"], trace: ["/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/puppetd.rb:99:in `calc_nodes_status'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/puppetd.rb:181:in `block in deploy_nodes'", "/usr/lib64/ruby/2.1.0/timeout.rb:91:in `block in timeout'", "/usr/lib64/ruby/2.1.0/timeout.rb:35:in `block in catch'", "/usr/lib64/ruby/2.1.0/timeout.rb:35:in `catch'", "/usr/lib64/ruby/2.1.0/timeout.rb:35:in `catch'", "/usr/lib64/ruby/2.1.0/timeout.rb:106:in `timeout'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/puppetd.rb:175:in `deploy_nodes'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/puppetd.rb:32:in `deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine/nailyfact.rb:33:in `deploy_piece'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:73:in `block (3 levels) in deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:73:in `each_slice'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:73:in `block (2 levels) in deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:71:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:71:in `block in deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:67:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/deployment_engine.rb:67:in `deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:42:in `deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/dispatcher.rb:58:in `deploy'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:135:in `dispatch_message'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:98:in `block in dispatch'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/task_queue.rb:64:in `call'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/task_queue.rb:64:in `block in each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/task_queue.rb:56:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/task_queue.rb:56:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:96:in `each_with_index'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:96:in `dispatch'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:84:in `block in perform_main_job'"]

Controllers node-1,2,3

Anastasia Palkina (apalkina) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/111214

Changed in fuel:
status: New → In Progress

Reviewed: https://review.openstack.org/111214
Committed: https://git.openstack.org/cgit/stackforge/fuel-astute/commit/?id=84155d98b74c311ffe00519969c86b59aa43bbab
Submitter: Jenkins
Branch: master

commit 84155d98b74c311ffe00519969c86b59aa43bbab
Author: Vladimir Sharshov <email address hidden>
Date: Fri Aug 1 13:19:26 2014 +0400

    Prevent to consider old hung nodes

    We can got situation when nodes already marked
    as error because was hanged, but we send it
    for analysis again.

    Change-Id: Iaa95403b7bed53be4d2183faf0b496797a8aacfb
    Closes-Bug: #1349733

Changed in fuel:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers