tap device added to integration bridge without tag
Bug #1064070 reported by
Gary Kotton
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Gary Kotton | ||
Folsom |
Fix Released
|
Medium
|
Gary Kotton | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
There are cases when a tap device is added to br-int and there is no tag.
Related branches
lp:~gandelman-a/ubuntu/quantal/quantum/2012.2.1
- Openstack Ubuntu Testers: Pending requested
-
Diff: 79 lines (+68/-0)1 file modifieddebian/changelog (+68/-0)
tags: | added: folsom-backport-potential |
Changed in quantum: | |
milestone: | none → grizzly-1 |
tags: | removed: folsom-backport-potential |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
Changed in quantum (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum (Ubuntu Quantal): | |
status: | New → Confirmed |
tags: | removed: in-stable-folsom |
Changed in quantum: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
The problem was as follows:
1. Installed quantum OVS agent
2. Updated configuration file to contain physical bridge
3. Restarted agent
4. Deleted physcial bridge
5. Restarted agent => exited due to having an incomplete configuration
6. Deployed VM
The agent terminated due to the pysical bridge not being configured. The tap devices were not assigned a tag.