← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1306399] [NEW] Troubleshooting iptables failure is difficult

 

Public bug reported:

When there is an iptables failure, it's difficult to troubleshoot
because the exception references a line number from a piped in set of
rules that the user can't see. (e.g.
http://paste.openstack.org/show/75523/)

The rules should be dumped in this case so the user and subsequent
developers fixing the bug can see the rule that caused the problem.

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1306399

Title:
  Troubleshooting iptables failure is difficult

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When there is an iptables failure, it's difficult to troubleshoot
  because the exception references a line number from a piped in set of
  rules that the user can't see. (e.g.
  http://paste.openstack.org/show/75523/)

  The rules should be dumped in this case so the user and subsequent
  developers fixing the bug can see the rule that caused the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1306399/+subscriptions


Follow ups

References