Bug 1275322 - L2 Agent doesn't expose loaded extenstions
Summary: L2 Agent doesn't expose loaded extenstions
Keywords:
Status: CLOSED DUPLICATE of bug 1289994
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Nir Magnezi
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On: 1289994
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-26 14:04 UTC by Itzik Brown
Modified: 2023-02-22 23:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-18 04:45:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1497969 0 None None None Never
OpenStack gerrit 238982 0 None None None Never

Description Itzik Brown 2015-10-26 14:04:32 UTC 
Description of problem:
Using Openvswitch L2 agent and configuring extensions=qos under agent section in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini.

Running
# neutron agent-show <OVS Agent ID>

Should show the loaded extensions

Version-Release number of selected component (if applicable):
openstack-neutron-2015.1.1-7.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Nir Yechiel 2015-10-26 23:02:25 UTC 
Fix proposed to stable/liberty
Comment 4 Assaf Muller 2015-12-01 16:29:25 UTC 
The patch was backported to stable/liberty, but would only be available in OSP 8 GA if we backported it to d/s specifically (This is assuming we *won't* be rebasing before GA). Worst case it will be available in OSP 8's first Y release.
Comment 6 Nir Magnezi 2015-12-17 09:49:44 UTC 
This fix is incorporated in the rebase on upstream stable/liberty (7.0.1).
See Bug 1289994.
Comment 7 Assaf Muller 2015-12-18 04:45:56 UTC 

*** This bug has been marked as a duplicate of bug 1289994 ***
Note You need to log in before you can comment on or make changes to this bug.