[Upgrade] iptables rules for node-groups are missed after FM upgrade 8.0 -> 9.x
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Anastasia Balobashina |
Bug Description
Detailed bug description:
The following iptables rules are missed for node-groups after Fuel Master upgrade from 8.0 to 9.x:
-A INPUT -i enp0s4 -m comment --comment "input from admin network" -j ACCEPT
-A POSTROUTING -d 10.109.27.0/24 -p tcp -m tcp --dport 8888 -j SNAT --to-source 10.109.20.2
-A POSTROUTING -d 10.109.27.0/24 -o enp0s4 -p udp -m addrtype --src-type LOCAL -j SNAT --to-source
10.109.20.2
-A POSTROUTING -s 10.109.27.0/24 -o e+ -m comment --comment "004 forward_admin_net2" -j MASQUERADE
Steps to reproduce:
1. Deploy FM 8.0
2. Create cluster (HA) with Neutron VLAN/VXLAN/GRE
3. Add 3 controller + ceph nodes
4. Add 2 compute + ceph nodes
5. Create custom network group based on template endpoints assignment
6. Add existing computes to custom network group
7. Deploy cluster
8. Upgrade FM to 9.x
9. Run the "mco ping"
Expected results:
The nodes of custom network group aren't available via mcollective.
Actual result:
The nodes of custom network group aren't available via mcollective.
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 9.1 |
summary: |
- [Upgrade] The rules of ip-tables for node-groups isn't saved after - upgrade FM upgrade 8.0 -> 9.x + [Upgrade] iptables rules for node-groups are missed after FM upgrade 8.0 + -> 9.x |
Changed in fuel: | |
assignee: | nobody → Fuel Octane (fuel-octane-team) |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel Octane (fuel-octane-team) → Anastasia Balobashina (atolochkova) |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
assignee: | Anastasia Balobashina (atolochkova) → Sergey Novikov (snovikov) |
Changed in fuel: | |
assignee: | Sergey Novikov (snovikov) → Anastasia Balobashina (atolochkova) |
That'is not a bug of the restore procedure it's an forgotten functionality in system tests for upgrades. We found that fuel-qa uses alternative approach how to configure multi-rack to perform tests. Unit tests have to be changed to support this feature for upgrades tests.
[0] https:/ /github. com/openstack/ fuel-qa/ blob/8794c63cc0 07157a89415691d fda02854ca3db52 /fuelweb_ test/helpers/ multiple_ networks_ hacks.py# L44-L83