| 2016-02-08 11:10:40 |
Alexander Gordeev |
bug |
|
|
added bug |
| 2016-02-08 11:10:40 |
Alexander Gordeev |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/bugs/1543063/+attachment/4566749/+files/cloud-init.log |
|
| 2016-02-08 11:13:42 |
Alexander Gordeev |
fuel: milestone |
|
9.0 |
|
| 2016-02-08 11:22:15 |
Alexander Gordeev |
description |
it's expected that 'write_files' will be executed at the very end of cloud-init and it must be likely the last module to be executed by cloud-init. At least, it shall be executed before 'runcmd'
cloud-init modules will be executed by the order they were defined in cloud.cfg:
Eg. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/config/cloud.cfg
having 'write_files' processed before 'runcmd' could indicate a node to be completely provisioned while it's not true. 'runcmd' could be executed and interfere with the first tasks of granular deployment.
in other words, this is the root cause of https://bugs.launchpad.net/fuel/+bug/1536924
provided fix for #1536924 only mitigates the issue. |
it's expected that 'write_files' will be executed at the very end of cloud-init and it must be likely the last module to be executed by cloud-init. At least, it shall be executed before 'runcmd'
cloud-init modules will be executed by the order they were defined in cloud.cfg:
Eg. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/config/cloud.cfg
having 'write_files' processed before 'runcmd' could indicate a node to be completely provisioned while it's not true. 'runcmd' could be executed and interfere with the first tasks of granular deployment.
https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/cloud_config_ubuntu.jinja2#L91-L103
in other words, this is the root cause of https://bugs.launchpad.net/fuel/+bug/1536924
provided fix for #1536924 only mitigates the issue. |
|
| 2016-02-08 12:09:37 |
Ilya Kutukov |
fuel: importance |
Undecided |
Medium |
|
| 2016-02-08 12:09:43 |
Ilya Kutukov |
fuel: importance |
Medium |
High |
|
| 2016-02-08 12:12:50 |
Ilya Kutukov |
fuel: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2016-02-08 12:12:53 |
Ilya Kutukov |
fuel: status |
New |
Confirmed |
|
| 2016-02-09 10:19:04 |
Dmitry Pyzhov |
tags |
|
area-python tech-debt |
|
| 2016-04-05 12:33:26 |
Sergey Slipushenko |
fuel: assignee |
Fuel Python Team (fuel-python) |
Sergey Slipushenko (sslypushenko) |
|
| 2016-04-13 10:40:23 |
Alexander Saprykin |
fuel: assignee |
Sergey Slipushenko (sslypushenko) |
Alexander Saprykin (cutwater) |
|
| 2016-04-13 10:40:45 |
Alexander Saprykin |
fuel: assignee |
Alexander Saprykin (cutwater) |
Sergey Slipushenko (sslypushenko) |
|
| 2016-04-19 09:08:16 |
Fuel Devops McRobotson |
fuel: milestone |
9.0 |
10.0 |
|
| 2016-04-19 09:08:18 |
Fuel Devops McRobotson |
fuel/mitaka: importance |
Undecided |
High |
|
| 2016-04-19 09:08:18 |
Fuel Devops McRobotson |
fuel/mitaka: status |
New |
Confirmed |
|
| 2016-04-19 09:08:18 |
Fuel Devops McRobotson |
fuel/mitaka: milestone |
|
9.0 |
|
| 2016-04-19 09:08:18 |
Fuel Devops McRobotson |
fuel/mitaka: assignee |
|
Sergey Slipushenko (sslypushenko) |
|
| 2016-04-20 17:09:08 |
Dmitry Pyzhov |
fuel/mitaka: status |
Confirmed |
Won't Fix |
|
| 2016-05-30 14:41:42 |
Sergey Slipushenko |
fuel: assignee |
Sergey Slipushenko (sslypushenko) |
Fuel Python (Deprecated) (fuel-python) |
|
| 2016-06-22 14:43:32 |
Dmitry Pyzhov |
fuel: assignee |
Fuel Python (Deprecated) (fuel-python) |
Fuel Sustaining (fuel-sustaining-team) |
|
| 2016-07-01 13:52:16 |
Mikhail Zhnichkov |
fuel: assignee |
Fuel Sustaining (fuel-sustaining-team) |
Mikhail Zhnichkov (mzhnichkov) |
|
| 2016-09-09 15:19:23 |
OpenStack Infra |
fuel: status |
Confirmed |
In Progress |
|
| 2016-09-15 12:21:10 |
OpenStack Infra |
fuel: status |
In Progress |
Fix Committed |
|
