Multiple cluster networks dnsmasq user-defined cobbler template gets lost after containers destruction
Bug #1473483 reported by
Vladimir Kuklin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Sergey Yudin | ||
6.1.x |
Won't Fix
|
High
|
Alexey Stupnikov |
Bug Description
6.1 GA
Install master node
Alter config files of cobbler to configure PXE boot of additional node groups.
I.e. edit dnsmasq cobbler template to add additional dhcp range as described here:
https:/
Destroy containers
Start containers
Expected result:
all the configurations are restored
Actual result:
additional dhcp ranges are lost as cobbler container gets regenerated along with dnsmasq config
Proposed solution - back this data up during container upgrade, convert it into astute.yaml fields and fix fuel library to regenerate these config fields during container bootstrap or even more - link this file into container.
tags: | added: feature-nodegroup |
tags: | added: on-verification |
tags: | added: wontfix-feature |
To post a comment you must log in.
Do we really going to support manual modyfication of config files?
Even accroding to the doc
>Note that the dnsmasq.template file is managed by Puppet so all changes are overwritten/removed when the Puppet container is restarted or the Fuel Master node is rebooted.
this is not supported, and, probably, we must implement this via UI or something, instead of manual modyfication.