Need to re-configure routing after we add a new nodegroup (rack)
Bug #1502842 reported by
Aleksandr Didenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Aleksey Kasatkin |
Bug Description
When we have a working env with multiple nodegroups and we add nodes from new rack (new nodegroup), we should re-configure static routes on all nodes in the env.
Steps to reproduce:
1. Deploy multirack evn with 2+ nodegroups
2. Add new nodegroup
3. Add 1+ nodes (computes, for example) from new nodegroup
4. Deploy changes
5. Run OSTF
Expected result:
OSTF passes, there are routes to new nodegroup on all nodes
Actual result
OSTF fails, there are no routes to new nodegroup on old nodes
no longer affects: | fuel/8.0.x |
Changed in fuel: | |
assignee: | Aleksey Kasatkin (alekseyk-ru) → Fedor Zhadaev (fzhadaev) |
Changed in fuel: | |
assignee: | Fedor Zhadaev (fzhadaev) → Aleksey Kasatkin (alekseyk-ru) |
tags: | added: area-python |
tags: | added: on-verification |
tags: | removed: on-verification |
To post a comment you must log in.
Fixed with https:/ /review. openstack. org/#/c/ 250507/
Rerun network setup on deployed nodes
This is required to apply changes that could be made to the networking configuration of environment.
The major case is: add/remove node network group(s).
The configuration changes are not tracked as nailgun does not have proper functionality for that.
New key is introduced in task description: reexecute_on (list). Deployment tasks which are to be re-executed on deploy changes must have
reexecute_on:
- deploy_changes
DocImpact
Change-Id: I668fcb426826ce cf69a5c7fc1e92b 8ae8dfeef9f network- on-changes
Blueprint: redeploy-