[418] Error running provisioning: <type 'exceptions.OSError'>:[Errno 2] No such file or directory: '/var/www/cobbler/images/centos-x86_64/initrd.img', trace: /usr/lib64/ruby/2.1.0/xmlrpc/client.rb:271:in `call'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vladimir Sharshov | ||
5.0.x |
Fix Committed
|
High
|
Vladimir Sharshov |
Bug Description
{
"build_id": "2014-07-
"mirantis": "yes",
"build_number": "112",
"ostf_sha": "09b6bccf7d4767
"nailgun_sha": "f5ff82558f99bb
"production": "docker",
"api": "1.0",
"fuelmain_sha": "29301584330422
"astute_sha": "5df009e8eab611
"release": "5.0.1",
"fuellib_sha": "364dee37435cbd
}
Steps:
1. Create next cluster - Ubuntu, Simple, Nova Vlan network, 1 controller, 1 compute
2. Deploy cluster
3. After successful deployment reset it
4. After reset deploy it again
Actual result - deployment failed with
[418] Error running provisioning: <type 'exceptions.
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
Logs are attached
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Vladimir Sharshov (vsharshov) |
Looks like same task try to perform several time in parallel:
2014-07-11 03:44:48 DEBUG
[399] Cobbler syncing
2014-07-11 03:44:48 DEBUG
[399] Trying to reboot node: node-3
2014-07-11 03:44:48 DEBUG
[399] Trying to reboot node: node-1
2014-07-11 03:44:41 DEBUG
[404] Cobbler syncing
2014-07-11 03:44:41 DEBUG
[407] Cobbler syncing
2014-07-11 03:44:41 DEBUG
[418] Cobbler syncing
2014-07-11 03:44:41 DEBUG
[415] Cobbler syncing
2014-07-11 03:44:41 DEBUG
[404] Saving system node-3
2014-07-11 03:44:41 DEBUG
[399] Cobbler syncing
2014-07-11 03:44:41 DEBUG
[407] Saving system node-3
2014-07-11 03:44:41 DEBUG
[418] Saving system node-3
OR
2014-07-11 03:44:38 INFO
[407] : Starting removing of nodes: ["1", "3"]
2014-07-11 03:44:38 INFO
[404] : Starting removing of nodes: ["1", "3"]
2014-07-11 03:44:38 INFO
[399] : Starting removing of nodes: ["1", "3"]
2014-07-11 03:44:38 INFO
[418] : Starting removing of nodes: ["1", "3"]
2014-07-11 03:44:38 INFO
[415] : Starting removing of nodes: ["1", "3"]
Evidence:
2014-07-11 03:44:32 DEBUG [415] Main worker task id is b5577130- 20a9-452c- a25d-908e6f62e1 f8 20a9-452c- a25d-908e6f62e1 f8 20a9-452c- a25d-908e6f62e1 f8 20a9-452c- a25d-908e6f62e1 f8 20a9-452c- a25d-908e6f62e1 f8
2014-07-11 03:44:32 DEBUG [399] Main worker task id is b5577130-
2014-07-11 03:44:32 DEBUG [407] Main worker task id is b5577130-
2014-07-11 03:44:30 DEBUG [404] Main worker task id is b5577130-
2014-07-11 03:44:32 DEBUG [418] Main worker task id is b5577130-
Potencial reason why they do such things:
2014-07-11 03:44:32 WARNING [418] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:32 WARNING [415] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:32 WARNING [399] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:31 WARNING [404] Trying to reconnect to message broker. Retry 5 sec later...
34 warnings about connection problem like above.
7 warnings like 'TCP connection to AMQP failed'
Timeline:
2014-07-11 03:44:30 DEBUG [404] Dispatching message: {"args" =>{"task_ uuid"=> "b5577130- 20a9-452c- a25d-908e6f62e1 f8", ... =>{"task_ uuid"=> "b5577130- 20a9-452c- a25d-908e6f62e1 f8", =>{"task_ uuid"=> "b5577130- 20a9-452c- a25d-908e6f62e1 f8", =>{"task_ uuid"=> "b5577130- 20a9-452c- a25d-908e6f62e1 f8" =>{"task_ uuid"=> "b5577130- 20a9-452c- a25d-908e6f62e1 f8"
2014-07-11 03:44:31 WARNING [404] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:32 DEBUG [407] Dispatching message: {"args"
2014-07-11 03:44:32 WARNING [412] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:32 DEBUG [399] Dispatching message: {"args"
2014-07-11 03:44:32 WARNING [399] Trying to reconnect to message broker. Retry 5 sec later...
2014-07-11 03:44:32 WARNING [415] Trying to reconnect to message broker. Retry 5 sec later..
2014-07-11 03:44:32 WARNING [418] Trying to reconnect to message broker. Retry 5 sec later..
2014-07-11 03:44:32 DEBUG [415] Dispatching message: {"args"
2014-07-11 03:44:32 DEBUG [418] Dispatching message: {"args"
It is look like almost every time when worker reconnect, he got a copy of last message from queue.