Iptables chaine name is to long for nova-api-metadata

Bug #944184 reported by Tomasz Paszkowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Vish Ishaya

Bug Description

Each nova component creates iptables chain name based on executable name. nova-api-metadata-POSTROUTING is 29 chars long and breaks this component from working with msg below:

"iptables-restore v1.4.10: Invalid chain name
`nova-api-metadata-POSTROUTING' (28 chars max)\nError occurred at
line: 16\nTry `iptables-restore -h' or 'iptables-restore --help' for
more information.\n"

Temporary workaround is to change executable name to sth shorter.

Tags: essex-rc1
affects: glance → nova
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
assignee: nobody → Vish Ishaya (vishvananda)
status: New → In Progress
Changed in nova:
milestone: none → essex-rc1
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/4756
Committed: http://github.com/openstack/nova/commit/094c7695e8e8261c256c862eaa6774742746f3b9
Submitter: Jenkins
Branch: master

commit 094c7695e8e8261c256c862eaa6774742746f3b9
Author: Vishvananda Ishaya <email address hidden>
Date: Thu Mar 1 10:26:22 2012 -0800

    Ensures that we don't exceed iptables chain max

     * Fixes bug 944184

    Change-Id: Ifb25f253ab32c9895aae276e946058eb62e14957

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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