Error running RPC method stop_deploy_task: can't convert NilClass into time interval, trac

Bug #1339024 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Vladimir Sharshov

Bug Description

"build_id": "2014-07-08_13-57-45",
"mirantis": "yes",
"build_number": "107",
"ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
"nailgun_sha": "c0082e3a0e8544bad7bd45c15c5dd8632ea045b5",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "b0f5151d12751b9b55dcd69bd1445d0d480012d6",
"astute_sha": "a4edb51661f50c66e247e0b8d00f2d01e0658fe6",
"release": "5.0.1",
"fuellib_sha": "d4cb36208efaf51a7c0ca012fa63d596d4ee2e29"

1. Create new environment (CentOS, simple mode)
2. Choose VLAN segmentation
3. Choose Ceph for images
4. Add controller, compute, cinder, 2 ceph
5. Untag storage and management networks and move them to other different interfaces
6. Start deployment
7. Stop deployment during provisioning
8. Deployment has failed with error: Error occurred while running method 'stop_deploy_task'. Inspect Orchestrator logs for the details.

In Astute logs:

2014-07-08 12:38:03 ERR

[396] Error running RPC method stop_deploy_task: can't convert NilClass into time interval, trace: ["/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:310:in `sleep'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:310:in `block in stop_provision_via_mcollective'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:309:in `times'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:309:in `stop_provision_via_mcollective'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/orchestrator.rb:167:in `stop_provision'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/dispatcher.rb:194:in `stop_current_task'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/dispatcher.rb:160:in `stop_deploy_task'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:128:in `dispatch_message'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:89:in `block in dispatch'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:87:in `each'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:87:in `each_with_index'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:87:in `dispatch'", "/usr/lib64/ruby/gems/2.1.0/gems/astute-0.0.2/lib/astute/server/server.rb:82:in `block in perform_service_job'"]

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Changed in fuel:
status: New → Confirmed
status: Confirmed → In Progress
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

We need in config NODES_REMOVE_INTERVAL

This option was added by this pull https://review.openstack.org/#/c/103518/.

We can also backport it to 5.0.1 or just add this option to config.

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-astute (stable/5.0)

Reviewed: https://review.openstack.org/105459
Committed: https://git.openstack.org/cgit/stackforge/fuel-astute/commit/?id=741b4fa9b964d73d9ab8f2fbcf5bb02836c98da1
Submitter: Jenkins
Branch: stable/5.0

commit 741b4fa9b964d73d9ab8f2fbcf5bb02836c98da1
Author: Vladimir Sharshov <email address hidden>
Date: Mon Jun 30 13:56:42 2014 +0400

    Avoid high load for Cobbler TFTP when delete many nodes.

    Delete operation does not have limit for nodes, but it
    erase disks and reboot nodes after which they try to boot
    using network. Cobbler installed at master node provide
    ability to boot using network and have limited resources.

    To prevent high load for Cobbler this changes add two things:
    * split all nodes to groups (default - 10) which process
    in series;
    * wait some time (default - 10 sec) between such groups.

    Both of this parameters can be changed in config.

    Closes-Bug: #1330938
    Closes-Bug: #1339024

    Backport from 5.1

    Change-Id: I9c3af6e8ab3c7c610e31baa6e58ec86aae20708d

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Verified on ISO #111
"build_id": "2014-07-09_14-02-00",
"mirantis": "yes",
"build_number": "111",
"ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
"nailgun_sha": "f5ff82558f99bb6ca7d5e1617eddddf7142fe857",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "b6f0d76964d0e8a0c4d9cc705338fb84512ea9d5",
"astute_sha": "5df009e8eab611750309a4c5b5c9b0f7b9d85806",
"release": "5.0.1",
"fuellib_sha": "364dee37435cbdc85d6b814a61f57800b83bf22d"

Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
Meg McRoberts (dreidellhasa) wrote :

Marked as "Fixed issue" in 5.0.1 Release Notes.

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.