Comment 13 for bug 1539460
Revision history for this message
| Vladimir Sharshov (vsharshov) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
We run several actions for this env:
2016-01-28 14:12:33 INFO [681] Processing RPC call 'granular_deploy'
2016-01-28 14:20:27 INFO [667] Processing RPC call 'granular_deploy'
2016-01-28 14:37:39 INFO [659] Processing RPC call 'reset_environment'
2016-01-28 14:45:46 INFO [659] Processing RPC call 'execute_tasks'
2016-01-28 15:10:25 INFO [652] Processing RPC call 'remove_nodes'
2016-01-28 15:11:26 INFO [671] Processing RPC call 'remove_nodes'
2016-01-28 15:11:53 INFO [657] Processing RPC call 'image_provision'
2016-01-28 16:19:58 INFO [657] Processing RPC call 'granular_deploy'
2016-01-28 17:26:17 INFO [676] Processing RPC call 'image_provision'
2016-01-28 17:29:24 INFO [676] Processing RPC call 'granular_deploy'
2016-01-28 18:08:13 INFO [681] Processing RPC call 'granular_deploy'
2016-01-29 07:54:38 INFO [667] Processing RPC call 'image_provision'
2016-01-29 08:16:54 INFO [659] Processing RPC call 'granular_deploy'
2016-01-29 08:26:23 INFO [652] Processing RPC call 'dump_environment'
We got fail on node 16. Critical nodes are not available for deployment: ["16"]. This is critical role primary-controller.
The last succeed action with it was 2016-01-28.
But as i can see in fuel node output, we do not have in list.
So my thoughts based on current info that problem is simple offline primary controller, because i do not see any actions
in Astute log which remove it from cluster.
In other hands: in what time was done? '''fuel node''' report which do not include such node as 16 but include node 4 which do not have role at all. I do not see any info in Astute log about this node 4, which has ready status.