After restore fuel master node iptables rules contain extra records

Bug #1362159 reported by Kirill Omelchenko
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Library (Deprecated)
5.1.x
Won't Fix
Medium
Matthew Mosesohn
6.1.x
Invalid
Medium
Matthew Mosesohn

Bug Description

http://jenkins-product.srt.mirantis.net:8080/view/0_master_swarm/job/master_fuelmain.system_test.centos.thread_1/149/testReport/%28root%29/backup_restore_master_base/backup_restore_master_base/

After restore of backed up master node two iptable rules appear:

-A FORWARD -i eth0 -o docker0 -p tcp -m state --state NEW -m tcp --dport 8000 -m comment --comment "nginx-tcp-8000-accept" -j ACCEPT
-A POSTROUTING -s 10.108.25.0/24 -p tcp -m tcp --dport 8000 -m comment --comment "nginx-tcp-8000-unmasquerade" -j ACCEPT

which doesn't seem to affect master node in any way
(manual deletion of those rules makes no observable changes, Fuel web-UI is accessible)

Revision history for this message
Kirill Omelchenko (komelchenko) wrote :
Changed in fuel:
milestone: 6.0 → 5.1
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

This is an issue where iptables fails to insert rules under heavy load. This is going to be intermittent and not easy to fix.

Changed in fuel:
importance: Undecided → Medium
status: New → Confirmed
milestone: 5.1 → 6.0
no longer affects: fuel/6.0.x
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/117496

Changed in fuel:
status: Confirmed → In Progress
Changed in fuel:
assignee: Matthew Mosesohn (raytrac3r) → Vladimir Kuklin (vkuklin)
Revision history for this message
Kirill Omelchenko (komelchenko) wrote :

After the fix rules regarding ports 8000, 8080 start to randomly disappear on the restored system.

Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Based on the conversation with Kirill, the insertion of rules randomly works and fails. It needs to be refactored and thoroughly tested. There needs to be more serious research here to figure out the best way to handle this. Moving to 6.0.

Changed in fuel:
assignee: Vladimir Kuklin (vkuklin) → Matthew Mosesohn (raytrac3r)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (master)

Change abandoned by Matthew Mosesohn (<email address hidden>) on branch: master
Review: https://review.openstack.org/117496
Reason: this does not solve the iptables bug because results are still random and unpredictable.

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Proposed change was abandoned, resetting status back to Confirmed.

Changed in fuel:
status: In Progress → Confirmed
assignee: Matthew Mosesohn (raytrac3r) → Fuel Library Team (fuel-library)
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

The best way to solve this is to upgrade Docker, so we don't have to use iptables workarounds for this outdated docker we're running. We won't need all the ugly hacks for deploying on Docker.

Changed in fuel:
status: Confirmed → Won't Fix
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

6.0 release-notes info: Sometimes iptables rules are missing immediately after restoring a Fuel deployment. This can be worked around in most cases by restarting Fuel Master.

tags: added: release-notes
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Docker was upgraded to 1.4.x in 6.1 release

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.