FA: introduce versioning for cloud-init templates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Alexander Gordeev |
Bug Description
right now, there's no any kind of versioning support for cloud-init templates.
It makes provisioning a node too risky for older version of fuel after upgrade. As cloud-init templates aligned with our custom build packages which may vary from one fuel release to another.
current version of fuel-agent with cloud-init templates is installed into bootstrap image. This image after upgrade will be replaced just to the newest one. cloud-init templates too. Therefore, it could break provisioning for old envs.
So, there's a flaw.
STR:
1) install 6.x version of fuel
2) deploy a cluster
3) upgrade fuel-master to 7.0
4) add new node to already deployed cluster
Actual result:
provisioning could lead to fail if cloud-init templates from 7.0 will be incompatible with 6.x environment.
Expected result:
provisioning succeeds. cloud-init templates for specific version of fuel will be applied, not just the newest one from 7.0
Related fix proposed to branch: master /review. openstack. org/208568
Review: https:/