[Yahoo-eng-team] [Bug 1680417] [NEW] There is no validation DVR is enabled before running -neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest tests

[Eran Kuris]

Public bug reported:

When I am running neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest tests 
on non-DVR environment they failed as expected. The problem is those tests 
should not run if the environment did not configure with DVR.
We should add a mechanism that checks if DVR is configured before it runs.


Version Ocata

How reproducible:
always

Steps to Reproduce:
1. run the test neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest on 
non-DVR environment.

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  There is no validation DVR is enabled before running
  -neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest   tests

Status in neutron:
  New

Bug description:
  When I am running neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest 
tests on non-DVR environment they failed as expected. The problem is those 
tests should not run if the environment did not configure with DVR.
  We should add a mechanism that checks if DVR is configured before it runs.

  
  Version Ocata

  How reproducible:
  always

  Steps to Reproduce:
  1. run the test neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest on 
non-DVR environment.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1679816] [NEW] There is no validation for image type in test.neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity

[Eran Kuris]

Public bug reported:

Description of problem:
test.neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity
To run this test we should not use Cirros image.  Before running the test we 
should verify which image is in use.

If the test run with an unsupported image like Cirros image, it will
fail with:

Traceback (most recent call last):
  File 
"/usr/lib/python2.7/site-packages/neutron/tests/tempest/scenario/test_trunk.py",
 line 240, in test_subport_connectivity
server['ssh_client'].exec_command(command)
  File 
"/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", 
line 36, in wrapper
return function(self, *args, **kwargs)
  File 
"/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", 
line 92, in exec_command
return self.ssh_client.exec_command(cmd)
  File "/usr/lib/python2.7/site-packages/tempest/lib/common/ssh.py", line 201, 
in exec_command
stderr=err_data, stdout=out_data)
tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; 
PATH=$PATH:/sbin; IFACE=$(ip l | grep "^[0-9]*: e" | cut -d \: -f 2) && sudo su 
-c "ip l a link $IFACE name $IFACE.10 type vlan id 10 && ip l s up dev 
$IFACE.10 && dhclient $IFACE.10"', exit status: 2, stderr:
ip: RTNETLINK answers: Operation not supported


Version-Release number of selected component (if applicable):
Ocata
How reproducible:
always

Steps to Reproduce:
1. run the test with Cirros image
2.
3.

Actual results:


Expected results:


Additional info:

https://review.openstack.org/#/c/436756/8/neutron/tests/tempest/api/test_trunk.py@242

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  There is no validation for image type in
  
test.neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity

Status in neutron:
  New

Bug description:
  Description of problem:
  
test.neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity
  To run this test we should not use Cirros image.  Before running the test we 
should verify which image is in use.

  If the test run with an unsupported image like Cirros image, it will
  fail with:

  Traceback (most recent call last):
File 
"/usr/lib/python2.7/site-packages/neutron/tests/tempest/scenario/test_trunk.py",
 line 240, in test_subport_connectivity
  server['ssh_client'].exec_command(command)
File 
"/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", 
line 36, in wrapper
  return function(self, *args, **kwargs)
File 
"/usr/lib/python2.7/site-packages/tempest/common/utils/linux/remote_client.py", 
line 92, in exec_command
  return self.ssh_client.exec_command(cmd)
File "/usr/lib/python2.7/site-packages/tempest/lib/common/ssh.py", line 
201, in exec_command
  stderr=err_data, stdout=out_data)
  tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; 
PATH=$PATH:/sbin; IFACE=$(ip l | grep "^[0-9]*: e" | cut -d \: -f 2) && sudo su 
-c "ip l a link $IFACE name $IFACE.10 type vlan id 10 && ip l s up dev 
$IFACE.10 && dhclient $IFACE.10"', exit status: 2, stderr:
  ip: RTNETLINK answers: Operation not supported

  
  Version-Release number of selected component (if applicable):
  Ocata
  How reproducible:
  always

  Steps to Reproduce:
  1. run the test with Cirros image
  2.
  3.

  Actual results:

  
  Expected results:

  
  Additional info:

  
https://review.openstack.org/#/c/436756/8/neutron/tests/tempest/api/test_trunk.py@242

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1679703] [NEW] Unable to boot instance with VF( direct-port ) because the PF is not online

[Eran Kuris]

Public bug reported:

Description of problem:

Booted VM with Direct-physical port (The entire PF is associated to the 
instance).
When I deleted the instance I expected that PF will be available and online.
Actually when I am trying to boot instance with direct port (VF)
I get this error message :

VM in error state- 
fault | {"message": "Exceeded maximum number of retries. Exceeded max 
scheduling attempts 3 for instance 102fde1b-22d3-4b05-8246-0f1af520455a. Last 
exception: internal error: Unable to configure VF 4 of PF 'p1p1' because the PF 
is not online. Please change host network config", "code": 500, "details": "  
File \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 524, 
in build_instances | filter_properties, instances[0].uuid)  

[root@compute-0 ~]# ifconfig |grep p1p1 --->PF is not online
it's impossible to create an instance with a direct port (VF)


version: 
Ocata 
How reproducible:
Always

Steps to Reproduce:
1. Deploy SRIOV setup with PF support 
2. boot instance with Direct-physical port
3. Delete VM that is associated to PF
4. boot instance with Direct port (VF)

Expected results:
VM with direct port should be booted. PF should be released

Additional info:
Workaround - systemctl restart network

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "failure.txt"
   
https://bugs.launchpad.net/bugs/1679703/+attachment/4854330/+files/failure.txt

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

Title:
  Unable to boot instance with VF( direct-port ) because the PF is not
  online

Status in neutron:
  New

Bug description:
  Description of problem:

  Booted VM with Direct-physical port (The entire PF is associated to the 
instance).
  When I deleted the instance I expected that PF will be available and online.
  Actually when I am trying to boot instance with direct port (VF)
  I get this error message :

  VM in error state- 
  fault | {"message": "Exceeded maximum number of retries. Exceeded max 
scheduling attempts 3 for instance 102fde1b-22d3-4b05-8246-0f1af520455a. Last 
exception: internal error: Unable to configure VF 4 of PF 'p1p1' because the PF 
is not online. Please change host network config", "code": 500, "details": "  
File \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 524, 
in build_instances | filter_properties, instances[0].uuid)  

  [root@compute-0 ~]# ifconfig |grep p1p1 --->PF is not online
  it's impossible to create an instance with a direct port (VF)

  
  version: 
  Ocata 
  How reproducible:
  Always

  Steps to Reproduce:
  1. Deploy SRIOV setup with PF support 
  2. boot instance with Direct-physical port
  3. Delete VM that is associated to PF
  4. boot instance with Direct port (VF)

  Expected results:
  VM with direct port should be booted. PF should be released

  Additional info:
  Workaround - systemctl restart network

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1671478] [NEW] Tests in neutron.tests.tempest.api.test_revisions.TestRevisions don't clean up network resources

[Eran Kuris]

Public bug reported:

Tests in  neutron.tests.tempest.api.test_revisions.TestRevisions create 
networks but don't remove them when each test is finished.
Cleanup only occurs after all the tests in RoutersTest finish to run.

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Tests in   neutron.tests.tempest.api.test_revisions.TestRevisions
  don't clean up network resources

Status in neutron:
  New

Bug description:
  Tests in  neutron.tests.tempest.api.test_revisions.TestRevisions create 
networks but don't remove them when each test is finished.
  Cleanup only occurs after all the tests in RoutersTest finish to run.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1616769] Re: Cant revert neutron-port PF to VF because sriov_numvfs parameter get "0" value

[Eran Kuris]

I think it valid case that user will revert from PF to VF port.
When we create vm with  PF port (direct physical ) 
/sys/class/net/enp5s0f1/device/sriov_numvfs parameter gets "0" value  which is 
expected , but when I delete this port I expected that 
/sys/class/net/enp5s0f1/device/sriov_numvfs  will return to previous value so I 
can set VF ports.
the problem still exist on OSP-1o - newton 

** Summary changed:

- When assigning neutron-port to PF sriov_numvfs parameter get "0" value
+ Cant revert neutron-port  PF to VF because sriov_numvfs parameter get "0" 
value

** Summary changed:

- Cant revert neutron-port  PF to VF because sriov_numvfs parameter get "0" 
value
+ Cant revert from neutron-port  PF to VF because sriov_numvfs parameter get 
"0" value

** Changed in: nova
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1616769

Title:
  Cant revert from neutron-port  PF to VF because sriov_numvfs parameter
  get "0" value

Status in OpenStack Compute (nova):
  New

Bug description:
  Description of problem:

  When manage SR-IOV PFs as Neutron ports I can see that
  /sys/class/net/enp5s0f1/device/sriov_numvfs parameter gets "0" value.
  When I delete the PF port  so I can switch to SRIOV - direct port (VF) I 
can't boot vm because sriov_numvfs parameter equal to "0" value

  Version-Release number of selected component (if applicable):

  $ rpm -qa |grep neutron
  python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
  openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
  python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch

  $ rpm -qa |grep nova
  python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
  openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
  openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch

  How reproducible:

  Always

  Steps to Reproduce:

  1.Set SRIOV ENV and PF support : 
https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z0lTzx5itQ6WL0/edit#
  2. BOOT VM that assign to PF (neutron port- direct-physical) -  should boot 
well
  3. check cat /sys/class/net/enp5s0f1/device/sriov_numvfs (= 0)
  4. delete vm  and check again sriov_numvfs (=0)
  5. I expect that numvfs should return to the default value that was configured

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1666864] [NEW] function does not return correct create router timestamp

[Eran Kuris]

Public bug reported:

Version: OSP-10 Newton
Test failed : 
neutron.tests.tempest.api.test_timestamp.TestTimeStampWithL3.test_show_router_attribute_with_timestamp

At creation the timestamp is correct: u'created_at':
u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z'

when "show" function display the timestamp it display it with ~3 sec difference:
u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:26Z'

show function display incorrect timestamp

218 def test_show_router_attribute_with_timestamp(self):
219 router = self.create_router(router_name='test')
220 import ipdb;ipdb.set_trace()
--> 221 body = self.client.show_router(router['id'])
222 show_router = body['router']
223 # verify the timestamp from creation and showed is same
224 import ipdb;ipdb.set_trace()
225 self.assertEqual(router['created_at'],
226  show_router['created_at'])

ipdb> router
{u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [], u'description': u'', 
u'admin_state_up': False, u'tenant_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', 
u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z', 
u'flavor_id': None, u'revision_number': 3, u'routes': [], u'project_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
ipdb> n
2017-02-22 10:47:55.084 6919 INFO tempest.lib.common.rest_client 
[req-eef7ded4-bb01-4401-96cd-325c01b2230b ] Request 
(TestTimeStampWithL3:test_show_router_attribute_with_timestamp): 200 GET 
http://10.0.0.104:9696/v2.0/routers/545e74b0-2f3d-43b8-8678-93bbb3f1f6f3 0.224s
2017-02-22 10:47:55.086 6919 DEBUG tempest.lib.common.rest_client 
[req-eef7ded4-bb01-4401-96cd-325c01b2230b ] Request - Headers: {'Content-Type': 
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', u'content-length': '462', 
'content-location': 
'http://10.0.0.104:9696/v2.0/routers/545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', 
u'date': 'Wed, 22 Feb 2017 10:47:56 GMT', u'content-type': 'application/json', 
u'connection': 'close', u'x-openstack-request-id': 
'req-eef7ded4-bb01-4401-96cd-325c01b2230b'}
Body: {"router": {"status": "ACTIVE", "external_gateway_info": null, 
"availability_zone_hints": [], "availability_zones": ["nova"], "description": 
"", "admin_state_up": false, "tenant_id": "8b9cd1ebd13f4172a0c63789ee9c0de2", 
"created_at": "2017-02-22T10:47:24Z", "updated_at": "2017-02-22T10:47:26Z", 
"flavor_id": null, "revision_number": 8, "routes": [], "project_id": 
"8b9cd1ebd13f4172a0c63789ee9c0de2", "id": 
"545e74b0-2f3d-43b8-8678-93bbb3f1f6f3", "name": "test"}} _log_request_full 
tempest/lib/common/rest_client.py:431
> /home/centos/tempest-upstream/neutron/neutron/tests/tempest/api/test_timestamp.py(222)test_show_router_attribute_with_timestamp()


ipdb> router
{u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [], u'description': u'', 
u'admin_state_up': False, u'tenant_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', 
u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z', 
u'flavor_id': None, u'revision_number': 3, u'routes': [], u'project_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
ipdb> show_router
{u'status': u'ACTIVE', u'external_gateway_info': None, 
u'availability_zone_hints': [], u'availability_zones': [u'nova'], 
u'description': u'', u'admin_state_up': False, u'tenant_id': 
u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'created_at': u'2017-02-22T10:47:24Z', 
u'updated_at': u'2017-02-22T10:47:26Z', u'flavor_id': None, u'revision_number': 
8, u'routes': [], u'project_id': u'8b9cd1ebd13f4172a0c63789ee9c0de2', u'id': 
u'545e74b0-2f3d-43b8-8678-93bbb3f1f6f3', u'name': u'test'}
ipdb>

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  function does not return correct create router timestamp

Status in neutron:
  New

Bug description:
  Version: OSP-10 Newton
  Test failed : 
neutron.tests.tempest.api.test_timestamp.TestTimeStampWithL3.test_show_router_attribute_with_timestamp

  At creation the timestamp is correct: u'created_at':
  u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:24Z'

  when "show" function display the timestamp it display it with ~3 sec 
difference:
  u'created_at': u'2017-02-22T10:47:24Z', u'updated_at': u'2017-02-22T10:47:26Z'

  show function display incorrect timestamp

  218 def test_show_router_attribute_with_timestamp(self):
  219 router = self.create_router(router_name='test')
  220 import ipdb

[Yahoo-eng-team] [Bug 1504941] Re: RBAC-RFE- neutron net-show command should display all tenant that using the network

[Eran Kuris]

** Changed in: neutron
   Status: Expired => New

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

Title:
  RBAC-RFE- neutron net-show command should display all tenant that
  using the network

Status in neutron:
  New

Bug description:
  On rdo- liberty I thested neutron rbac feature .
  when network assigned to more then 1 tenant we still see one tenant in 
neutron net-show 
  [root@cougar16 ~(keystone_admin)]# neutron net-show 
590ca7b9-1682-4c40-8213-02feaa7a96cc
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | id| 590ca7b9-1682-4c40-8213-02feaa7a96cc |
  | mtu   | 0|
  | name  | internal_ipv4_a  |
  | provider:network_type | vxlan|
  | provider:physical_network |  |
  | provider:segmentation_id  | 70   |
  | router:external   | False|
  | shared| False|
  | status| ACTIVE   |
  | subnets   | 9a1a387e-88cf-484a-8b12-5a1834be0233 |
  | tenant_id | fa4add4659704239b771b0bccb8b6829 |
  +---+--+

  this network shared in 2 tenants : 
  [root@cougar16 ~(keystone_admin)]# neutron rbac-list
  
+--+--+
  | id   | object_id
|
  
+--+--+
  | 4f1a9c9d-e820-46e4-b431-b3142c6bb245 | 818dd42f-f627-45d4-a578-dd475b9e19e4 
|
  | 8c995ab1-dea6-411b-854c-a405cf5365fa | 590ca7b9-1682-4c40-8213-02feaa7a96cc 
|
  | abb375b9-95d0-4297-80f1-3f22f0f84a9e | b071a769-0d50-4d25-8730-fed3dea13a2f 
|
  | f3122b92-f47a-4a0f-a422-c9f7ed482341 | 590ca7b9-1682-4c40-8213-02feaa7a96cc 
|

  
  [root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron 
  python-neutronclient-3.1.1-dev1.el7.centos.noarch
  python-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-ml2-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-common-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-openvswitch-7.0.0.0-rc2.dev21.el7.centos.noarch

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1658689] [NEW] unclear error message while booting VM with security group when port_security_enabled=false

[Eran Kuris]

Public bug reported:

When port_security_enabled = False its not possible to boot instance with 
security group.
The instance is in "ERROR" state .
The log display unclear error message : 
 

[root@controller-0 ~]# rpm -qa |grep neutron
openstack-neutron-lbaas-9.1.0-1.el7ost.noarch
openstack-neutron-ml2-9.1.0-8.el7ost.noarch
python-neutronclient-6.0.0-2.el7ost.noarch
python-neutron-lib-0.4.0-1.el7ost.noarch
openstack-neutron-bigswitch-lldp-9.40.0-1.1.el7ost.noarch
openstack-neutron-metering-agent-9.1.0-8.el7ost.noarch
puppet-neutron-9.4.2-1.el7ost.noarch
python-neutron-9.1.0-8.el7ost.noarch
python-neutron-tests-9.1.0-8.el7ost.noarch
python-neutron-lbaas-9.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-9.1.0-8.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.1.0-8.el7ost.noarch
openstack-neutron-common-9.1.0-8.el7ost.noarch
openstack-neutron-9.1.0-8.el7ost.noarch
[root@controller-0 ~]# rpm -qa |grep nova
openstack-nova-cert-14.0.2-8.el7ost.noarch
python-novaclient-6.0.0-1.el7ost.noarch
openstack-nova-common-14.0.2-8.el7ost.noarch
openstack-nova-novncproxy-14.0.2-8.el7ost.noarch
openstack-nova-console-14.0.2-8.el7ost.noarch
openstack-nova-conductor-14.0.2-8.el7ost.noarch
openstack-nova-compute-14.0.2-8.el7ost.noarch
puppet-nova-9.4.0-1.el7ost.noarch
python-nova-14.0.2-8.el7ost.noarch
openstack-nova-scheduler-14.0.2-8.el7ost.noarch
openstack-nova-api-14.0.2-8.el7ost.noarch

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "log bug"
   https://bugs.launchpad.net/bugs/1658689/+attachment/4808071/+files/log%20bug

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

Title:
  unclear error message while booting VM with security group when
  port_security_enabled=false

Status in neutron:
  New

Bug description:
  When port_security_enabled = False its not possible to boot instance with 
security group.
  The instance is in "ERROR" state .
  The log display unclear error message : 
   

  [root@controller-0 ~]# rpm -qa |grep neutron
  openstack-neutron-lbaas-9.1.0-1.el7ost.noarch
  openstack-neutron-ml2-9.1.0-8.el7ost.noarch
  python-neutronclient-6.0.0-2.el7ost.noarch
  python-neutron-lib-0.4.0-1.el7ost.noarch
  openstack-neutron-bigswitch-lldp-9.40.0-1.1.el7ost.noarch
  openstack-neutron-metering-agent-9.1.0-8.el7ost.noarch
  puppet-neutron-9.4.2-1.el7ost.noarch
  python-neutron-9.1.0-8.el7ost.noarch
  python-neutron-tests-9.1.0-8.el7ost.noarch
  python-neutron-lbaas-9.1.0-1.el7ost.noarch
  openstack-neutron-openvswitch-9.1.0-8.el7ost.noarch
  openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
  openstack-neutron-sriov-nic-agent-9.1.0-8.el7ost.noarch
  openstack-neutron-common-9.1.0-8.el7ost.noarch
  openstack-neutron-9.1.0-8.el7ost.noarch
  [root@controller-0 ~]# rpm -qa |grep nova
  openstack-nova-cert-14.0.2-8.el7ost.noarch
  python-novaclient-6.0.0-1.el7ost.noarch
  openstack-nova-common-14.0.2-8.el7ost.noarch
  openstack-nova-novncproxy-14.0.2-8.el7ost.noarch
  openstack-nova-console-14.0.2-8.el7ost.noarch
  openstack-nova-conductor-14.0.2-8.el7ost.noarch
  openstack-nova-compute-14.0.2-8.el7ost.noarch
  puppet-nova-9.4.0-1.el7ost.noarch
  python-nova-14.0.2-8.el7ost.noarch
  openstack-nova-scheduler-14.0.2-8.el7ost.noarch
  openstack-nova-api-14.0.2-8.el7ost.noarch

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1625570] [NEW] fullstack : should add test of ensure traffic is using DSCP marks outbound

[Eran Kuris]

Public bug reported:

https://review.openstack.org/#/c/190285/57/specs/newton/ml2-qos-with-
dscp.rst

we should add in fullstack a test that ensure traffic is using DSCP
marks outbound

** Affects: neutron
 Importance: Medium
 Status: New


** Tags: qos

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

Title:
  fullstack : should add test of ensure traffic is using DSCP marks
  outbound

Status in neutron:
  New

Bug description:
  https://review.openstack.org/#/c/190285/57/specs/newton/ml2-qos-with-
  dscp.rst

  we should add in fullstack a test that ensure traffic is using DSCP
  marks outbound

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1616769] [NEW] When assigning neutron-port to PF sriov_numvfs parameter get "0" value

[Eran Kuris]

Public bug reported:

escription of problem:
When manage SR-IOV PFs as Neutron ports I can see that 
/sys/class/net/enp5s0f1/device/sriov_numvfs parameter gets "0" value . 
when I delete the PF port  so I can switch to SRIOV - direct port (VF) I cant 
boot vm because sriov_numvfs parameter equal to "0" value
Version-Release number of selected component (if applicable):
 rpm -qa |grep neutron
python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
[root@controller1 ~(keystone_admin)]# rpm -qa |grep nova
python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch


How reproducible:
always 

Steps to Reproduce:
1.Set SRIOV ENV and PF support : 
https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z0lTzx5itQ6WL0/edit#
2. BOOT VM that assign to PF (neutron port- direct-physical) -  should boot well
3. check cat /sys/class/net/enp5s0f1/device/sriov_numvfs  (=0)
4. delete vm  and check again sriov_numvfs   (=0)
5. I expect that numvfs should return to the default value that was configured

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1616769

Title:
  When assigning neutron-port to PF sriov_numvfs parameter get "0" value

Status in OpenStack Compute (nova):
  New

Bug description:
  escription of problem:
  When manage SR-IOV PFs as Neutron ports I can see that 
  /sys/class/net/enp5s0f1/device/sriov_numvfs parameter gets "0" value . 
  when I delete the PF port  so I can switch to SRIOV - direct port (VF) I cant 
boot vm because sriov_numvfs parameter equal to "0" value
  Version-Release number of selected component (if applicable):
   rpm -qa |grep neutron
  python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
  openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
  python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  [root@controller1 ~(keystone_admin)]# rpm -qa |grep nova
  python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
  openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
  openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch

  
  How reproducible:
  always 

  Steps to Reproduce:
  1.Set SRIOV ENV and PF support : 
https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z

[Yahoo-eng-team] [Bug 1616442] [NEW] SRIOV agent error when VM booted with direct-physical port

[Eran Kuris]

Public bug reported:

When assigning neutron port to PF (neutron port type - direct-physical )
the vm is booted and active but there is errors in sriov agent log 
attached  file with the errors 

Version-Release number of selected component (if applicable):
RHOS-10 
[root@controller1 ~(keystone_admin)]# rpm -qa |grep neutron 
python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
[root@controller1 ~(keystone_admin)]# rpm -qa |grep nova
python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.deploy SRIOV setup and set PF functionality  you can use guide : 
https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z0lTzx5itQ6WL0/edit#
2.boot vm & assign it to PF 
3.check in compute node sriov agent log

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "sriov agent log"
   
https://bugs.launchpad.net/bugs/1616442/+attachment/4727004/+files/sriov%20agent%20log

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

Title:
  SRIOV agent error when VM booted with direct-physical port

Status in neutron:
  New

Bug description:
  When assigning neutron port to PF (neutron port type - direct-physical )
  the vm is booted and active but there is errors in sriov agent log 
  attached  file with the errors 

  Version-Release number of selected component (if applicable):
  RHOS-10 
  [root@controller1 ~(keystone_admin)]# rpm -qa |grep neutron 
  python-neutron-lib-0.3.0-0.20160803002107.405f896.el7ost.noarch
  openstack-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  puppet-neutron-9.1.0-0.20160813031056.7cf5e07.el7ost.noarch
  python-neutron-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  python-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  python-neutron-lbaas-9.0.0-0.20160816191643.4e7301e.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  python-neutronclient-5.0.0-0.20160812094704.ec20f7f.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160817153328.b9169e3.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160817171450.e1ac68f.el7ost.noarch
  [root@controller1 ~(keystone_admin)]# rpm -qa |grep nova
  python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
  openstack-nova-api-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  puppet-nova-9.1.0-0.20160813014843.b94f0a0.el7ost.noarch
  openstack-nova-common-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-novncproxy-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-conductor-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  python-nova-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-scheduler-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-cert-14.0.0-0.20160817225441.04cef3b.el7ost.noarch
  openstack-nova-console-14.0.0-0.20160817225441.04cef3b.el7ost.noarch

  How reproducible:

  
  Steps to Reproduce:
  1.deploy SRIOV setup and set PF functionality  you can use guide : 
  
https://docs.google.com/document/d/1qQbJlLI1hSlE4uwKpmVd0BoGSDBd8Z0lTzx5itQ6WL0/edit#
  2.boot vm & assign it to PF 
  3.check in compute node sriov agent log

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

[Yahoo-eng-team] [Bug 1614092] [NEW] SRIOV - PF / VM that assign to PF does not get vlan tag

[Eran Kuris]

Public bug reported:

During RFE testing Manage SR-IOV PFs as Neutron ports, I found VM booted with 
Neutron port vnic_type  direct-physical  but it does not get access to DHCP 
server. 
The problem is that the PF / VM does not get VLAN tag with the internal vlan.
Workaround : 
Enter to the VM via console and set vlan interface. 


version RHOS 10 
python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
openstack-neutron-metering-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
puppet-neutron-9.1.0-0.20160725142451.4061b39.el7ost.noarch
python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
openstack-neutron-ml2-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  SRIOV - PF / VM that assign to PF  does not get vlan tag

Status in neutron:
  New

Bug description:
  During RFE testing Manage SR-IOV PFs as Neutron ports, I found VM booted with 
Neutron port vnic_type  direct-physical  but it does not get access to DHCP 
server. 
  The problem is that the PF / VM does not get VLAN tag with the internal vlan.
  Workaround : 
  Enter to the VM via console and set vlan interface. 


  version RHOS 10 
  python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  puppet-neutron-9.1.0-0.20160725142451.4061b39.el7ost.noarch
  python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1614086] [NEW] SRIOV- when numvfs=0 SRIOV agent is failed to start

[Eran Kuris]

Public bug reported:

Deployed SRIOV ENV with X VFs (for example 4 ). After that I wanted to move the 
VFs.
When setting SRIOV system with numvfs=0  and restart SRIOV agent it failed to 
start
# echo 0> sys/class/net/enp5s0f1/device/sriov_numvfs 
# systemctl restart neutron-sriov-nic-agent
# systemctl status neutron-sriov-nic-agent

version - RHOS10
python-neutron-lbaas-9.0.0-0.20160722053816.0c73910.el7ost.noarch
python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
openstack-neutron-metering-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
puppet-neutron-9.1.0-0.20160725142451.4061b39.el7ost.noarch
python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
python-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
openstack-neutron-lbaas-9.0.0-0.20160722053816.0c73910.el7ost.noarch
openstack-neutron-ml2-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch


attached the log file

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "sriov log"
   
https://bugs.launchpad.net/bugs/1614086/+attachment/4722621/+files/agent%20fail

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

Title:
  SRIOV- when numvfs=0 SRIOV agent is failed to start

Status in neutron:
  New

Bug description:
  Deployed SRIOV ENV with X VFs (for example 4 ). After that I wanted to move 
the VFs.
  When setting SRIOV system with numvfs=0  and restart SRIOV agent it failed to 
start
  # echo 0> sys/class/net/enp5s0f1/device/sriov_numvfs 
  # systemctl restart neutron-sriov-nic-agent
  # systemctl status neutron-sriov-nic-agent

  version - RHOS10
  python-neutron-lbaas-9.0.0-0.20160722053816.0c73910.el7ost.noarch
  python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
  openstack-neutron-metering-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  puppet-neutron-9.1.0-0.20160725142451.4061b39.el7ost.noarch
  python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
  python-neutron-fwaas-9.0.0-0.20160720211704.c3e491c.el7ost.noarch
  openstack-neutron-lbaas-9.0.0-0.20160722053816.0c73910.el7ost.noarch
  openstack-neutron-ml2-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch


  
  attached the log file

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1613610] [NEW] SRIOV- PFs aren't showing up as available

[Eran Kuris]

Public bug reported:

Description of problem:
PFs aren't showing up as available making it not possible to boot vms with PFs
When I am trying to boot VM with Neutron port with vnic type - direct - 
physical there is an error.
attached the error. 
The ENV is SRIOV  1 compute  & 1 controller 


Version-Release number of selected component (if applicable):
python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch
python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch
openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch
python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch


How reproducible:
always

Steps to Reproduce:
1.Deploy SRIOV ENV 
2.Config the ENV to work with PF  (no VFS configured )
3.Create neutron port  vnic type= direct physical
4.boot vm with neutrn port that created 


Actual results:
VM is in ERROR state

** Affects: nova
 Importance: Undecided
 Status: New

** Attachment added: "pf nova boot"
   
https://bugs.launchpad.net/bugs/1613610/+attachment/4721723/+files/pf%20nova%20boot

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1613610

Title:
  SRIOV- PFs aren't showing up as available

Status in OpenStack Compute (nova):
  New

Bug description:
  Description of problem:
  PFs aren't showing up as available making it not possible to boot vms with PFs
  When I am trying to boot VM with Neutron port with vnic type - direct - 
physical there is an error.
  attached the error. 
  The ENV is SRIOV  1 compute  & 1 controller 
  

  Version-Release number of selected component (if applicable):
  python-nova-14.0.0-0.20160726054215.02421fc.el7ost.noarch
  python-novaclient-5.0.1-0.20160724130722.6b11a1c.el7ost.noarch
  openstack-nova-compute-14.0.0-0.20160726054215.02421fc.el7ost.noarch
  openstack-nova-common-14.0.0-0.20160726054215.02421fc.el7ost.noarch
  python-neutron-lib-0.2.1-0.20160726025313.405f896.el7ost.noarch
  openstack-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-sriov-nic-agent-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  python-neutron-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-openvswitch-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  openstack-neutron-common-9.0.0-0.20160726001729.6a23add.el7ost.noarch
  python-neutronclient-4.2.1-0.20160721230146.3b1c538.el7ost.noarch

  
  How reproducible:
  always

  Steps to Reproduce:
  1.Deploy SRIOV ENV 
  2.Config the ENV to work with PF  (no VFS configured )
  3.Create neutron port  vnic type= direct physical
  4.boot vm with neutrn port that created 

  
  Actual results:
  VM is in ERROR state

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1608176] [NEW] SRIOV-port creation : its possible to create more direct ports than available vif.

[Eran Kuris]

Public bug reported:

When creating sriov ports we can create more ports than vif's are avalible 
for example we have 4 vifs and created more than 4 direct ports . 
[root@compute1 ~(keystone_admin)]# neutron port-list
+--+--+---+-
| id   | name | mac_address   | fixed_ips   
|
| 22e0ae33-1f9e-47f5-9b20-2a3277b15959 |  | fa:16:3e:82:52:ea | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.13"} |
| 2f6c4371-fffe-4834-a6aa-725ae72f4d02 |  | fa:16:3e:9c:e9:bb | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.4"}  |
| 98b62507-e21b-49e6-880e-34fa14f6b986 |  | fa:16:3e:8e:73:40 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.5"}  |
| a9a28d02-4342-4575-9f9a-8ae70ab8bd2a |  | fa:16:3e:7d:3f:04 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.14"} |
| b466da32-fff4-46d8-a134-d861105e966f |  | fa:16:3e:3c:81:a5 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.6"}  |
| d3601592-0133-4c65-ab85-cc142325ce29 |  | fa:16:3e:c1:81:01 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.3"}  |
| d67e2fa6-6805-4baa-882e-9cf54714ba20 |  | fa:16:3e:32:26:f5 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.2"}  |
| e5b5290d-1824-4bd9-aecb-81032b38ac60 |  | fa:16:3e:58:8f:c9 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.7"}  |
+--+--+---+-
[root@compute1 ~(keystone_admin)]# ip link show 
4: enp5s0f1:  mtu 1500 qdisc mq master 
ovs-system state UP mode DEFAULT qlen 1000
link/ether a0:36:9f:7f:28:ba brd ff:ff:ff:ff:ff:ff
vf 0 MAC fa:16:3e:3c:81:a5, vlan 208, spoof checking on, link-state auto
vf 1 MAC fa:16:3e:9c:e9:bb, vlan 208, spoof checking on, link-state auto
vf 2 MAC fa:16:3e:8e:73:40, vlan 208, spoof checking on, link-state auto
vf 3 MAC fa:16:3e:c1:81:01, vlan 208, spoof checking on, link-state auto

[root@controller1 ~]# rpm -qa |grep neutron 
python-neutron-7.0.4-3.el7ost.noarch
openstack-neutron-lbaas-7.0.0-2.el7ost.noarch
openstack-neutron-openvswitch-7.0.4-3.el7ost.noarch
python-neutron-fwaas-7.0.0-1.el7ost.noarch
openstack-neutron-fwaas-7.0.0-1.el7ost.noarch
python-neutron-lbaas-7.0.0-2.el7ost.noarch
openstack-neutron-ml2-7.0.4-3.el7ost.noarch
python-neutronclient-3.1.0-1.el7ost.noarch
openstack-neutron-common-7.0.4-3.el7ost.noarch
openstack-neutron-7.0.4-3.el7ost.noarch
 
osp 8

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  SRIOV-port creation : its possible to create more direct ports than
  available vif.

Status in neutron:
  New

Bug description:
  When creating sriov ports we can create more ports than vif's are avalible 
  for example we have 4 vifs and created more than 4 direct ports . 
  [root@compute1 ~(keystone_admin)]# neutron port-list
  
+--+--+---+-
  | id   | name | mac_address   | fixed_ips 
  |
  | 22e0ae33-1f9e-47f5-9b20-2a3277b15959 |  | fa:16:3e:82:52:ea | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.13"} |
  | 2f6c4371-fffe-4834-a6aa-725ae72f4d02 |  | fa:16:3e:9c:e9:bb | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.4"}  |
  | 98b62507-e21b-49e6-880e-34fa14f6b986 |  | fa:16:3e:8e:73:40 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.5"}  |
  | a9a28d02-4342-4575-9f9a-8ae70ab8bd2a |  | fa:16:3e:7d:3f:04 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.14"} |
  | b466da32-fff4-46d8-a134-d861105e966f |  | fa:16:3e:3c:81:a5 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.6"}  |
  | d3601592-0133-4c65-ab85-cc142325ce29 |  | fa:16:3e:c1:81:01 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.3"}  |
  | d67e2fa6-6805-4baa-882e-9cf54714ba20 |  | fa:16:3e:32:26:f5 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.2"}  |
  | e5b5290d-1824-4bd9-aecb-81032b38ac60 |  | fa:16:3e:58:8f:c9 | 
{"subnet_id": "212d47a3-93b7-400d-8322-84717c780e21", "ip_address": 
"192.168.1.7"}  |
  
+--+--+---+

[Yahoo-eng-team] [Bug 1571657] [NEW] it's possible to create IPv6 subnet without address & RA mode

[Eran Kuris]

Public bug reported:

We can create IPv6 subnet without address mode  &  Ra_mode parameters  .
When creating this kind of subnet and  attach it to network that have ipv4   
when  booting VM  it  does not get any ip address .
No Meaning produce ipv6 subnet without those parameters 


[root@puma15 ~(keystone_admin)]# rpm -qa |grep neut
openstack-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-ml2-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-openvswitch-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
openstack-neutron-common-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
python-neutronclient-4.1.2-0.20160304195803.5d28651.el7.centos.noarch
python-neutron-lib-0.0.3-0.20160227020344.999828a.el7.centos.noarch
openstack-neutron-metering-agent-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
[root@puma15 ~(keystone_admin)]# 

[root@puma15 ~(keystone_admin)]# neutron net-list
+--+--+-+
| id   | name | 
subnets |
+--+--+-+
| e1af28fe-6725-471f-9dcb-21139dd815af | tempest-network-smoke--922626247 | 
dd3f38b2-ba3d-49cf-b5c5-9fd05af1b207 2003::/64  |
|  |  | 
bdd6fe30-d278-437f-97a1-10a93862a338 10.100.0.0/28  |
| ae26ce01-d0f4-46ac-ac74-f652477b0a4c | external_network | 
1771fd81-9c6c-4f5b-a7e9-246221e28577 10.35.166.0/24 |
+--+--+-+
[root@puma15 ~(keystone_admin)]# neutron subnet-create 
e1af28fe-6725-471f-9dcb-21139dd815af 2001:db1:0::2/64 --name 
dhcpv6_slaac_subnete  --ip-version 6Created a new subnet:
+---+--+
| Field | Value 
   |
+---+--+
| allocation_pools  | {"start": "2001:db1::2", "end": 
"2001:db1:::::"} |
| cidr  | 2001:db1::/64 
   |
| dns_nameservers   |   
   |
| enable_dhcp   | True  
   |
| gateway_ip| 2001:db1::1   
   |
| host_routes   |   
   |
| id| 6d30c5c2-c7a7-4439-aa7b-24c10bd26ec8  
   |
| ip_version| 6 
   |
| ipv6_address_mode |   
   |
| ipv6_ra_mode  |   
   |
| name  | dhcpv6_slaac_subnete  
   |
| network_id| e1af28fe-6725-471f-9dcb-21139dd815af  
   |
| subnetpool_id |   
   |
| tenant_id | 9a0058cf974c47ecb4f778d8e199f7ae  
   |
+---+--+

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  it's  possible to create IPv6 subnet without address & RA mode

Status in neutron:
  New

Bug description:
  We can create IPv6 subnet without address mode  &  Ra_mode parameters  .
  When creating this kind of subnet and  attach it to network that have ipv4   
when  booting VM  it  does not get any ip address .
  No Meaning produce ipv6 subnet without those parameters 

  
  [root@puma15 ~(keystone_admin)]# rpm -qa |grep neut
  openstack-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
  openstack-neutron-ml2-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
  python-neutron-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
  
openstack-neutron-openvswitch-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
  openstack-neutron-common-8.0.0.0b4-0.20160304174813.0ae20a3.el7.centos.noarch
  python-neutronclient-4.1.2-0.20160304195803.5d28651.el7.centos.noarch
  python-neutron-lib-0.0.3-0.20160227020344.999828a.el7.centos.noarch
  
openstack-neutron-metering-agent-8.0.0.0b4-0.20160304174813.0ae20a

[Yahoo-eng-team] [Bug 1570241] Re: ERROR (ClientException): Unexpected API Error during type the command: nova virtual-interface-list

[Eran Kuris]

less /var/log/nova/nova-api.log
2016-04-17 05:19:12.697 24505 WARNING keystonemiddleware.auth_token [-] 
Authorization failed for token
2016-04-17 05:19:12.698 24505 WARNING keystonemiddleware.auth_token [-] 
Identity response: {"error": {"message": "Could not find token: 
058d81b26ee34f36b0e5b4de334ef5be", "code": 404, "title": "Not Found"}}
2016-04-17 05:19:12.700 24505 WARNING keystonemiddleware.auth_token [-] 
Authorization failed for token
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions 
[req-606035da-18cf-4a79-bbf6-657dd4685597 2221c6978efd43df8e634932691fa06f 
6d3b7a1a69cf4bb1ac75224f2cfaa12e - - -] Unexpected exception in API method
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/virtual_interfaces.py",
 line 69, in index
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions 
entity_maker=_translate_vif_summary_view)
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/virtual_interfaces.py",
 line 60, in _items
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions vifs = 
self.network_api.get_vifs_by_instance(context, instance)
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 1451, in 
get_vifs_by_instance
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions raise 
NotImplementedError()
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions 
NotImplementedError
2016-04-17 06:05:49.290 24504 ERROR nova.api.openstack.extensions 


less /var/log/nova/nova-compute.log 
383e04ac, exception: Requested operation is not valid: cpu affinity is not 
supported
2016-04-17 06:07:49.635 19328 WARNING nova.virt.libvirt.driver 
[req-d9c8320c-bfd6-40ed-a8e7-32f5d8bf4ed5 - - - - -] couldn't obtain the vpu 
count from domain id: bae94215-cda7-4307-9425-f491f2be2343, exception: 
Requested operation is not valid: cpu affinity is not supported
2016-04-17 06:08:51.632 19328 WARNING nova.virt.libvirt.driver 
[req-d9c8320c-bfd6-40ed-a8e7-32f5d8bf4ed5 - - - - -] couldn't obtain the vpu 
count from domain id: 37fecbe8-82bf-4b3b-83a9-559e383e04ac, exception: 
Requested operation is not valid: cpu affinity is not supported
2016-04-17 06:08:51.635 19328 WARNING nova.virt.libvirt.driver 
[req-d9c8320c-bfd6-40ed-a8e7-32f5d8bf4ed5 - - - - -] couldn't obtain the vpu 
count from domain id: bae94215-cda7-4307-9425-f491f2be2343, exception: 
Requested operation is not valid: cpu affinity is not supported


** Changed in: nova
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1570241

Title:
  ERROR (ClientException): Unexpected API Error during  type the
  command: nova virtual-interface-list

Status in OpenStack Compute (nova):
  New

Bug description:
  [stack@undercloud ~]$ nova virtual-interface-list 
bae94215-cda7-4307-9425-f491f2be2343
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-2dc1eff6-874c-4a7c-b731-a56a6b9796fb)

  I  run the test with tempest on ospd setup 1 controller  one compute 
  after the test failed and  I got this log : 

  Traceback (most recent call last):
File "/root/tempest-dir/tempest/test.py", line 113, in wrapper
  return f(self, *func_args, **func_kwargs)
File 
"/root/tempest-dir/tempest/api/compute/servers/test_virtual_interfaces.py", 
line 56, in test_list_virtual_interfaces
  self.client.list_virtual_interfaces(self.server_id)
File "/root/tempest-dir/tempest/lib/services/compute/servers_client.py", 
line 478, in list_virtual_interfaces
  'os-virtual-interfaces']))
File "/root/tempest-dir/tempest/lib/common/rest_client.py", line 274, in get
  return self.request('GET', url, extra_headers, headers)
File 
"/root/tempest-dir/tempest/lib/services/compute/base_compute_client.py", line 
53, in request
  method, url, extra_headers, headers, body)
File "/root/tempest-dir/tempest/lib/common/rest_client.py", line 642, in 
request
  resp, resp_body)
File "/root/tempest-dir/tempest/lib/common/rest_client.py", line 761, in 
_error_checker
  message=message)
  ServerFault: Got server fault
  Details: Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the 

[Yahoo-eng-team] [Bug 1570241] [NEW] ERROR (ClientException): Unexpected API Error during type the command: nova virtual-interface-list

[Eran Kuris]

Public bug reported:

[stack@undercloud ~]$ nova virtual-interface-list 
bae94215-cda7-4307-9425-f491f2be2343 
ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: 
req-2dc1eff6-874c-4a7c-b731-a56a6b9796fb)
[stack@undercloud ~]$ rpm -qa |grep -i nova 
openstack-nova-conductor-12.0.2-5.el7ost.noarch
openstack-nova-compute-12.0.2-5.el7ost.noarch
openstack-nova-scheduler-12.0.2-5.el7ost.noarch
openstack-nova-api-12.0.2-5.el7ost.noarch
python-nova-12.0.2-5.el7ost.noarch
openstack-nova-cert-12.0.2-5.el7ost.noarch
openstack-nova-common-12.0.2-5.el7ost.noarch
python-novaclient-3.1.0-2.el7ost.noarch

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1570241

Title:
  ERROR (ClientException): Unexpected API Error during  type the
  command: nova virtual-interface-list

Status in OpenStack Compute (nova):
  New

Bug description:
  [stack@undercloud ~]$ nova virtual-interface-list 
bae94215-cda7-4307-9425-f491f2be2343 
  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-2dc1eff6-874c-4a7c-b731-a56a6b9796fb)
  [stack@undercloud ~]$ rpm -qa |grep -i nova 
  openstack-nova-conductor-12.0.2-5.el7ost.noarch
  openstack-nova-compute-12.0.2-5.el7ost.noarch
  openstack-nova-scheduler-12.0.2-5.el7ost.noarch
  openstack-nova-api-12.0.2-5.el7ost.noarch
  python-nova-12.0.2-5.el7ost.noarch
  openstack-nova-cert-12.0.2-5.el7ost.noarch
  openstack-nova-common-12.0.2-5.el7ost.noarch
  python-novaclient-3.1.0-2.el7ost.noarch

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1421239] Re: LBaaS- overwrite when associate 2 different Vip's to same external IP

[Eran Kuris]

** Changed in: neutron
   Status: Incomplete => Invalid

** Changed in: neutron
   Status: Invalid => New

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

Title:
  LBaaS- overwrite when associate  2 different Vip's  to same external
  IP

Status in neutron:
  New

Bug description:
  Version :
  [root@puma15 ~]# rpm -qa |grep neutron
  openstack-neutron-openvswitch-2014.2.1-6.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  openstack-neutron-2014.2.1-6.el7ost.noarch
  python-neutron-2014.2.1-6.el7ost.noarch
  openstack-neutron-ml2-2014.2.1-6.el7ost.noarch

  
  I created in LBaaS  2  VIP's .
  I  associate one vip (192.168.1.8) to external IP  (10.35.166.4).
  When I try to associate the second vip(192.168.1.9) to same external IP 
10.35.166.4  I success but it overwrite the first vip  , there is no warning 
message.
  We should prevent it as we cannot associate VM to external IP that already 
associated to other VM (we get an error message : Conflict (HTTP 409) 
(Request-ID: req-35eeddc9-d264-4fc5-a336-d201e4a66231 ])

  **If we not prevent it we should send warning message about it .

  How to Reproduce :
  Create in your tenant 2 VM's  with internal network & external network.

  1. Create LB pool on subnet of tenant A
  >

  2. Log into VM1 and VM2, enable httpd
  

  3. Create 2 members into webpool (use VM’s Ips)
   --protocol-port 80 webpool>

  4.Create a Healthmonitor and associated it with the webpool

  

  Run:
  

   webpool

  5.Create a VIP for the webpool
   webpool>

  6.Check HAproxy created (for example)
  

  7. Create a floating IP from external network
  

  8.Check port id of LB VIP
  
  

  9.Associate floating IP with the LB VIP
   

  10.From external network, try to connect the floating IP by curl
  http://IP>

  create for same VM's  VIP  to other service FTP  or SSH  for example
  and try to associate it to same external floating ip that we used
  already.

  see the command I entered :
  __

  [root@puma15 ~(keystone_eran1)]# neutron port-list
  
+--+--+---+-+
  | id   | name 
| mac_address   | fixed_ips 
  |
  
+--+--+---+-+
  | 17552712-9b66-466b-8836-7e09a15f439a |  
| fa:16:3e:6d:93:c3 | {"subnet_id": "cff1967c-dd18-4247-849d-97c363c39b4f", 
"ip_address": "10.35.166.5"}  |
  | 2668a4e8-7ddf-4242-813b-5febe7269d1b |  
| fa:16:3e:9d:d0:cd | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", 
"ip_address": "192.168.1.3"}  |
  | 3f9691df-9e33-4ea2-812a-83d51fdf45a1 |  
| fa:16:3e:12:18:fb | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", 
"ip_address": "192.168.1.6"}  |
  | 4004c3d0-390a-4db6-9c2c-b96b4a920af8 |  
| fa:16:3e:df:08:6f | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", 
"ip_address": "192.168.1.1"}  |
  | 460dafb7-3d05-4494-a83d-416b82b4eace | 
vip-adc9c688-97d2-425b-abd0-29505ac10a76 | fa:16:3e:65:8d:ff | {"subnet_id": 
"c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.56"} |
  | 6eba1c27-d202-470b-b89b-73a569d9da00 |  
| fa:16:3e:4d:b9:18 | {"subnet_id": "c86dbc71-78f8-47a6-9531-fd84a78c5fed", 
"ip_address": "192.168.1.7"}  |
  | 73149116-32e8-4960-a0a5-286bdb117d96 | 
vip-bc9c9025-db2c-40cd-8663-50c687639ff1 | fa:16:3e:75:53:33 | {"subnet_id": 
"c86dbc71-78f8-47a6-9531-fd84a78c5fed", "ip_address": "192.168.1.55"} |
  | 8f6ba5ab-12d8-4b1c-b78f-60bf90210dc9 |  
| fa:16:3e:ee:a7:a3 | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", 
"ip_address": "192.168.2.4"}  |
  | aad2870a-4f18-4471-985f-943911dfaaf3 |  
| fa:16:3e:d9:d7:85 | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", 
"ip_address": "192.168.2.3"}  |
  | b359ba1f-dde1-4576-9904-644acb032c4f |  
| fa:16:3e:92:d9:8c | {"subnet_id": "cff1967c-dd18-4247-849d-97c363c39b4f", 
"ip_address": "10.35.166.4"}  |
  | b471ddb4-d1b8-4df0-b098-60a2a45a1d4f |  
| fa:16:3e:8c:5b:4c | {"subnet_id": "65bfd326-7912-4ce6-91fd-04d81476d20e", 
"ip_address": "192.168.2.1"}  |
  | c0fe10e3-32b8-4373-b848-8d9ba5879a41 |  
| fa:16:

[Yahoo-eng-team] [Bug 1567334] [NEW] RFE: Add ethertype field when creating security group rule

[Eran Kuris]

Public bug reported:

In CLI when creating security group rule there is separation between IPv4 & 
IPv6 type .
I would like to add in Horizon this  option so we have separation between IPv4 
& IPv6  rules . 

In cli: 
neutron security-group-rule-create  --direction ingress --ethertype IPv6

Version: 
Liberty

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1567334

Title:
  RFE: Add ethertype field when creating security group rule

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In CLI when creating security group rule there is separation between IPv4 & 
IPv6 type .
  I would like to add in Horizon this  option so we have separation between 
IPv4 & IPv6  rules . 

  In cli: 
  neutron security-group-rule-create  --direction ingress --ethertype 
IPv6

  Version: 
  Liberty

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1565682] [NEW] OVS-DPDK failed to boot more than 1 instance on OVS-DPDK setup

[Eran Kuris]

Public bug reported:

vm failed

Description of problem:
On OVS-DPDK setup 1 controller & 1 compute with data tenant/network type vlan I 
failed to boot instances. When create 1 VM it success. From the second vm all 
vm's failed .When I created multiplae VM's - Instance Count 4 for example 
few of the instances will boot as active and few will be failed.
When using DPDK we should boot vm with flavor that use hugepages - :
$ nova flavor-create  m1.medium_dpdk 6 2048 20 2
$ nova flavor-key m1.medium_dpdk set "hw:mem_page_size=large" 
attached all log 
nic type: Ethernet controller: Intel Corporation Ethernet 10G 2P X520 Adapter 
driver: ixgbe
Version-Release number of selected component (if applicable):
[root@puma48 ~]# rpm -qa |grep neutro
openstack-neutron-openvswitch-7.0.1-6.el7ost.noarch
python-neutron-7.0.1-6.el7ost.noarch
openstack-neutron-common-7.0.1-6.el7ost.noarch
python-neutronclient-3.1.0-1.el7ost.noarch
openstack-neutron-7.0.1-6.el7ost.noarch
[root@puma48 ~]# rpm -qa |grep dpd
openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
dpdk-2.1.0-5.el7.x86_64

How reproducible:
always 

Steps to Reproduce:
1.https://docs.google.com/document/d/1K_ku6_08ooq46dFLiE7fAJ0ByFdPCb0W_q6kKqF3Y0o/edit
2.
3.

Actual results:


Expected results:


Additional info:

** Affects: nova
 Importance: Undecided
 Status: New

** Attachment added: "nova dpdk"
   
https://bugs.launchpad.net/bugs/1565682/+attachment/4622775/+files/nova%20dpdk

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1565682

Title:
  OVS-DPDK failed to boot more than 1 instance on OVS-DPDK setup

Status in OpenStack Compute (nova):
  New

Bug description:
  vm failed

  Description of problem:
  On OVS-DPDK setup 1 controller & 1 compute with data tenant/network type vlan 
I failed to boot instances. When create 1 VM it success. From the second vm all 
vm's failed .When I created multiplae VM's - Instance Count 4 for example 
  few of the instances will boot as active and few will be failed.
  When using DPDK we should boot vm with flavor that use hugepages - :
  $ nova flavor-create  m1.medium_dpdk 6 2048 20 2
  $ nova flavor-key m1.medium_dpdk set "hw:mem_page_size=large" 
  attached all log 
  nic type: Ethernet controller: Intel Corporation Ethernet 10G 2P X520 Adapter 
  driver: ixgbe
  Version-Release number of selected component (if applicable):
  [root@puma48 ~]# rpm -qa |grep neutro
  openstack-neutron-openvswitch-7.0.1-6.el7ost.noarch
  python-neutron-7.0.1-6.el7ost.noarch
  openstack-neutron-common-7.0.1-6.el7ost.noarch
  python-neutronclient-3.1.0-1.el7ost.noarch
  openstack-neutron-7.0.1-6.el7ost.noarch
  [root@puma48 ~]# rpm -qa |grep dpd
  openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
  dpdk-2.1.0-5.el7.x86_64

  How reproducible:
  always 

  Steps to Reproduce:
  
1.https://docs.google.com/document/d/1K_ku6_08ooq46dFLiE7fAJ0ByFdPCb0W_q6kKqF3Y0o/edit
  2.
  3.

  Actual results:

  
  Expected results:

  
  Additional info:

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1530038] [NEW] when external_network_bridge is set to br-ex ovs does not create flow to EXT access

[Eran Kuris]

Public bug reported:

Under  /etc/neutron/l3_agent.ini  when configuring external_network_bridge = 
br-ex 
OVS does not create dump-flow for this vlan so we get external access. 

version : # rpm -qa |grep neutron 
openstack-neutron-7.0.1-2.el7ost.noarch
python-neutronclient-3.1.0-1.el7ost.noarch
python-neutron-7.0.1-2.el7ost.noarch
openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
openstack-neutron-common-7.0.1-2.el7ost.noarch
openstack-neutron-ml2-7.0.1-2.el7ost.noarch
[root@puma06 ~(keystone_admin)]# rpm -qa |grep openvswitch 
python-openvswitch-2.4.0-1.el7.noarch
openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
openvswitch-2.4.0-1.el7.x86_64

Installed by packstack OSP-8

step to reproduce : 
1. Deploy with packstack OSP-8 , set ETX bridge parameter -->  
CONFIG_NEUTRON_L3_EXT_BRIDGE= br-ex 
2. setup ENV : 
# neutron net-create external_network --provider:network_type=vlan  
--provider:segmentation_id=181 --provider:physical_network physnet 
--router:external
# neutron subnet-create external_network 10.35.166.0/24 --disable-dhcp 
--gateway 10.35.166.254  --allocation-pool start=10.35.166.1,end=10.35.166.100 
# neutron net-create int_net 
# neutron subnet-create int_net 192.168.1.0/24 --dns_nameservers list=true 
10.35.28.28 --name int_sub
# neutron router-create Router_eNet
# neutron router-interface-add Router_eNet subnet=int_sub
# neutron router-gateway-set Router_eNet external_network

3. ovs-ofctl dump-flows br-ex
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=57707.344s, table=0, n_packets=21, n_bytes=1638, 
idle_age=60, priority=2,in_port=2 actions=drop
 cookie=0x0, duration=57707.394s, table=0, n_packets=1233857, n_bytes=85172234, 
idle_age=0, priority=0 actions=NORMAL

try to ping EXT network (8.8.8.8)  -- no connectivity
4. When we change external_network_bridge = provider and creating the ENV again 
(new router & new routr ports )
I get EXT access and the flow created : 
# ovs-ofctl dump-flows br-ex
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=105.955s, table=0, n_packets=5, n_bytes=402, idle_age=97, 
priority=4,in_port=2,dl_vlan=2 actions=mod_vlan_vid:181,NORMAL
 cookie=0x0, duration=58222.490s, table=0, n_packets=39, n_bytes=3174, 
idle_age=105, priority=2,in_port=2 actions=drop
 cookie=0x0, duration=58222.540s, table=0, n_packets=1244856, n_bytes=85931346, 
idle_age=0, priority=0 actions=NORMAL

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  when external_network_bridge is set to  br-ex ovs does not create flow
  to EXT access

Status in neutron:
  New

Bug description:
  Under  /etc/neutron/l3_agent.ini  when configuring external_network_bridge = 
br-ex 
  OVS does not create dump-flow for this vlan so we get external access. 

  version : # rpm -qa |grep neutron 
  openstack-neutron-7.0.1-2.el7ost.noarch
  python-neutronclient-3.1.0-1.el7ost.noarch
  python-neutron-7.0.1-2.el7ost.noarch
  openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
  openstack-neutron-common-7.0.1-2.el7ost.noarch
  openstack-neutron-ml2-7.0.1-2.el7ost.noarch
  [root@puma06 ~(keystone_admin)]# rpm -qa |grep openvswitch 
  python-openvswitch-2.4.0-1.el7.noarch
  openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch
  openvswitch-2.4.0-1.el7.x86_64

  Installed by packstack OSP-8

  step to reproduce : 
  1. Deploy with packstack OSP-8 , set ETX bridge parameter -->  
CONFIG_NEUTRON_L3_EXT_BRIDGE= br-ex 
  2. setup ENV : 
  # neutron net-create external_network --provider:network_type=vlan  
--provider:segmentation_id=181 --provider:physical_network physnet 
--router:external
  # neutron subnet-create external_network 10.35.166.0/24 --disable-dhcp 
--gateway 10.35.166.254  --allocation-pool start=10.35.166.1,end=10.35.166.100 
  # neutron net-create int_net 
  # neutron subnet-create int_net 192.168.1.0/24 --dns_nameservers list=true 
10.35.28.28 --name int_sub
  # neutron router-create Router_eNet
  # neutron router-interface-add Router_eNet subnet=int_sub
  # neutron router-gateway-set Router_eNet external_network

  3. ovs-ofctl dump-flows br-ex
  NXST_FLOW reply (xid=0x4):
   cookie=0x0, duration=57707.344s, table=0, n_packets=21, n_bytes=1638, 
idle_age=60, priority=2,in_port=2 actions=drop
   cookie=0x0, duration=57707.394s, table=0, n_packets=1233857, 
n_bytes=85172234, idle_age=0, priority=0 actions=NORMAL

  try to ping EXT network (8.8.8.8)  -- no connectivity
  4. When we change external_network_bridge = provider and creating the ENV 
again (new router & new routr ports )
  I get EXT access and the flow created : 
  # ovs-ofctl dump-flows br-ex
  NXST_FLOW reply (xid=0x4):
   cookie=0x0, duration=105.955s, table=0, n_packets=5, n_bytes=402, 
idle_age=97, priority=4,in_port=2,dl_vlan=2 actions=mod_vlan_vid:181,NORMAL
   cookie=0x0, duration=58222.490s, table=0, n_packets=39, n_bytes=3174, 
idle_age=105, p

[Yahoo-eng-team] [Bug 1525796] Re: After OVS-DPDK package installation host responds very slowly

[Eran Kuris]

** Changed in: neutron
   Status: New => Invalid

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

Title:
  After OVS-DPDK package installation host responds very slowly

Status in neutron:
  Invalid

Bug description:
  Description of problem:
  Install OVS-DPDK packages 
  dpdk-tools-2.1.0-5.el7.x86_64
  openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
  dpdk-2.1.0-5.el7.x86_64

  After that every command or action taking too long. THe host response
  very slowly.

  Version-Release number of selected component (if applicable):
  dpdk-tools-2.1.0-5.el7.x86_64
  openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
  dpdk-2.1.0-5.el7.x86_64
  [root@puma06 ~]# rpm -qa |grep neutron
  python-neutronclient-3.1.0-1.el7ost.noarch
  python-neutron-7.0.0-5.el7ost.noarch
  openstack-neutron-common-7.0.0-5.el7ost.noarch
  openstack-neutron-7.0.0-5.el7ost.noarch
  openstack-neutron-ml2-7.0.0-5.el7ost.noarch
  openstack-neutron-openvswitch-7.0.0-5.el7ost.noarch

  
  How reproducible:
  always 
  Steps to Reproduce:
  1.Install OSP-8 ENV with packstack {AIO ENV}
  2.install ovs-DPDK packages 
  3.your user experience now is very slow

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1525796] [NEW] After OVS-DPDK package installation host responds very slowly

[Eran Kuris]

Public bug reported:

Description of problem:
Install OVS-DPDK packages 
dpdk-tools-2.1.0-5.el7.x86_64
openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
dpdk-2.1.0-5.el7.x86_64

After that every command or action taking too long. THe host response
very slowly.

Version-Release number of selected component (if applicable):
dpdk-tools-2.1.0-5.el7.x86_64
openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
dpdk-2.1.0-5.el7.x86_64
[root@puma06 ~]# rpm -qa |grep neutron
python-neutronclient-3.1.0-1.el7ost.noarch
python-neutron-7.0.0-5.el7ost.noarch
openstack-neutron-common-7.0.0-5.el7ost.noarch
openstack-neutron-7.0.0-5.el7ost.noarch
openstack-neutron-ml2-7.0.0-5.el7ost.noarch
openstack-neutron-openvswitch-7.0.0-5.el7ost.noarch


How reproducible:
always 
Steps to Reproduce:
1.Install OSP-8 ENV with packstack {AIO ENV}
2.install ovs-DPDK packages 
3.your user experience now is very slow

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "DPDK resourches"
   
https://bugs.launchpad.net/bugs/1525796/+attachment/4534439/+files/DPDK%20resourches

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

Title:
  After OVS-DPDK package installation host responds very slowly

Status in neutron:
  New

Bug description:
  Description of problem:
  Install OVS-DPDK packages 
  dpdk-tools-2.1.0-5.el7.x86_64
  openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
  dpdk-2.1.0-5.el7.x86_64

  After that every command or action taking too long. THe host response
  very slowly.

  Version-Release number of selected component (if applicable):
  dpdk-tools-2.1.0-5.el7.x86_64
  openvswitch-dpdk-2.4.0-0.10346.git97bab959.2.el7.x86_64
  dpdk-2.1.0-5.el7.x86_64
  [root@puma06 ~]# rpm -qa |grep neutron
  python-neutronclient-3.1.0-1.el7ost.noarch
  python-neutron-7.0.0-5.el7ost.noarch
  openstack-neutron-common-7.0.0-5.el7ost.noarch
  openstack-neutron-7.0.0-5.el7ost.noarch
  openstack-neutron-ml2-7.0.0-5.el7ost.noarch
  openstack-neutron-openvswitch-7.0.0-5.el7ost.noarch

  
  How reproducible:
  always 
  Steps to Reproduce:
  1.Install OSP-8 ENV with packstack {AIO ENV}
  2.install ovs-DPDK packages 
  3.your user experience now is very slow

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1515597] [NEW] OSP-8- neutron-server service in failed status after reboot

[Eran Kuris]

Public bug reported:

In OSP-8-liberty I deployed environment with 2 nodes controller & compute 
all services was active . when I reboot the controller  neutron-server & 
l3-agent  services upload with "failed" status.
The bug found in version : 
# rpm -qa |grep neutron 
openstack-neutron-ml2-7.0.0-2.el7ost.noarch
python-neutronclient-3.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-7.0.0-2.el7ost.noarch
python-neutron-7.0.0-2.el7ost.noarch
openstack-neutron-common-7.0.0-2.el7ost.noarch
openstack-neutron-7.0.0-2.el7ost.noarch
[root@puma06 ~]# rpm -qa |grep sql
python-sqlalchemy-1.0.8-1.el7ost.x86_64
python-sqlparse-0.1.16-1.1.el7ost.noarch
sqlite-3.7.17-8.el7.x86_64
^[[A[root@puma06 ~]# rpm -qa |grep packstack
openstack-packstack-puppet-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch
openstack-packstack-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch

try to check if it is SeLinux issue but its not .
attached all relevant logs

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "neutron serverlog"
   
https://bugs.launchpad.net/bugs/1515597/+attachment/4517522/+files/neutron%20serverlog

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

Title:
  OSP-8- neutron-server service in failed status after reboot

Status in neutron:
  New

Bug description:
  In OSP-8-liberty I deployed environment with 2 nodes controller & compute 
  all services was active . when I reboot the controller  neutron-server & 
l3-agent  services upload with "failed" status.
  The bug found in version : 
  # rpm -qa |grep neutron 
  openstack-neutron-ml2-7.0.0-2.el7ost.noarch
  python-neutronclient-3.1.0-1.el7ost.noarch
  openstack-neutron-openvswitch-7.0.0-2.el7ost.noarch
  python-neutron-7.0.0-2.el7ost.noarch
  openstack-neutron-common-7.0.0-2.el7ost.noarch
  openstack-neutron-7.0.0-2.el7ost.noarch
  [root@puma06 ~]# rpm -qa |grep sql
  python-sqlalchemy-1.0.8-1.el7ost.x86_64
  python-sqlparse-0.1.16-1.1.el7ost.noarch
  sqlite-3.7.17-8.el7.x86_64
  ^[[A[root@puma06 ~]# rpm -qa |grep packstack
  openstack-packstack-puppet-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch
  openstack-packstack-7.0.0-0.7.dev1661.gaf13b7e.el7ost.noarch

  try to check if it is SeLinux issue but its not .
  attached all relevant logs

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1512969] [NEW] DHCP-HA-RFE- there is no command that show us with network node is the DHCP proviider

[Eran Kuris]

Public bug reported:

version : 
[root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron
python-neutronclient-3.1.1-dev1.el7.centos.noarch
python-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-ml2-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-common-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-openvswitch-7.0.0.0-rc2.dev21.el7.centos.noarch

When deploying HA environment we have HA of DHCP  service . 
There is no command that gave us information about which network node is 
provide the DHCP service.
The only way to get this info is by search in /var/log/messages  which network 
node sent ack for DHCP request.

I think that we need to add neutron command that show  which network node is 
providing DHCP services.
for example 
$ neutron dhcp-show

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  DHCP-HA-RFE- there is no command that show us with network node is the
  DHCP proviider

Status in neutron:
  New

Bug description:
  version : 
  [root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron
  python-neutronclient-3.1.1-dev1.el7.centos.noarch
  python-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-ml2-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-common-7.0.0.0-rc2.dev21.el7.centos.noarch
  openstack-neutron-openvswitch-7.0.0.0-rc2.dev21.el7.centos.noarch

  When deploying HA environment we have HA of DHCP  service . 
  There is no command that gave us information about which network node is 
provide the DHCP service.
  The only way to get this info is by search in /var/log/messages  which 
network node sent ack for DHCP request.

  I think that we need to add neutron command that show  which network node is 
providing DHCP services.
  for example 
  $ neutron dhcp-show

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1504942] [NEW] no support for rbac in horizon

[Eran Kuris]

Public bug reported:

we need to add support for  rbac feature support in horizon- GUI
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html


bug in version :
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1504942

Title:
  no support for rbac in horizon

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  we need to add support for  rbac feature support in horizon- GUI
  
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html

  
  bug in version :
  
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1504941] [NEW] RBAC-RFE- neutron net-show command should display all tenant that using the network

[Eran Kuris]

Public bug reported:

On rdo- liberty I thested neutron rbac feature .
when network assigned to more then 1 tenant we still see one tenant in neutron 
net-show 
[root@cougar16 ~(keystone_admin)]# neutron net-show 
590ca7b9-1682-4c40-8213-02feaa7a96cc
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| 590ca7b9-1682-4c40-8213-02feaa7a96cc |
| mtu   | 0|
| name  | internal_ipv4_a  |
| provider:network_type | vxlan|
| provider:physical_network |  |
| provider:segmentation_id  | 70   |
| router:external   | False|
| shared| False|
| status| ACTIVE   |
| subnets   | 9a1a387e-88cf-484a-8b12-5a1834be0233 |
| tenant_id | fa4add4659704239b771b0bccb8b6829 |
+---+--+

this network shared in 2 tenants : 
[root@cougar16 ~(keystone_admin)]# neutron rbac-list
+--+--+
| id   | object_id|
+--+--+
| 4f1a9c9d-e820-46e4-b431-b3142c6bb245 | 818dd42f-f627-45d4-a578-dd475b9e19e4 |
| 8c995ab1-dea6-411b-854c-a405cf5365fa | 590ca7b9-1682-4c40-8213-02feaa7a96cc |
| abb375b9-95d0-4297-80f1-3f22f0f84a9e | b071a769-0d50-4d25-8730-fed3dea13a2f |
| f3122b92-f47a-4a0f-a422-c9f7ed482341 | 590ca7b9-1682-4c40-8213-02feaa7a96cc |


[root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron 
python-neutronclient-3.1.1-dev1.el7.centos.noarch
python-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-ml2-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-common-7.0.0.0-rc2.dev21.el7.centos.noarch
openstack-neutron-openvswitch-7.0.0.0-rc2.dev21.el7.centos.noarch

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  RBAC-RFE- neutron net-show command should display all tenant that
  using the network

Status in neutron:
  New

Bug description:
  On rdo- liberty I thested neutron rbac feature .
  when network assigned to more then 1 tenant we still see one tenant in 
neutron net-show 
  [root@cougar16 ~(keystone_admin)]# neutron net-show 
590ca7b9-1682-4c40-8213-02feaa7a96cc
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | id| 590ca7b9-1682-4c40-8213-02feaa7a96cc |
  | mtu   | 0|
  | name  | internal_ipv4_a  |
  | provider:network_type | vxlan|
  | provider:physical_network |  |
  | provider:segmentation_id  | 70   |
  | router:external   | False|
  | shared| False|
  | status| ACTIVE   |
  | subnets   | 9a1a387e-88cf-484a-8b12-5a1834be0233 |
  | tenant_id | fa4add4659704239b771b0bccb8b6829 |
  +---+--+

  this network shared in 2 tenants : 
  [root@cougar16 ~(keystone_admin)]# neutron rbac-list
  
+--+--+
  | id   | object_id
|
  
+--+--+
  | 4f1a9c9d-e820-46e4-b431-b3142c6bb245 | 818dd42f-f627-45d4-a578-dd475b9e19e4 
|
  | 8c995ab1-dea6-411b-854c-a405cf5365fa | 590ca7b9-1682-4c40-8213-02feaa7a96cc 
|
  | abb375b9-95d0-4297-80f1-3f22f0f84a9e | b071a769-0d50-4d25-8730-fed3dea13a2f 
|
  | f3122b92-f47a-4a0f-a422-c9f7ed482341 | 590ca7b9-1682-4c40-8213-02feaa7a96cc 
|

  
  [root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron 
  python-neutronclient-3.1.1-dev1.el7.centos.noarch
  python-neutron-7.0.0.0-rc2.dev21.el7.centos.noarch
  ope

[Yahoo-eng-team] [Bug 1490985] [NEW] Inconsistent between subnet-create & subnet-update command

[Eran Kuris]

Public bug reported:

Description of problem:
When creating subnet with allocation pool we using flag that calls :  " 
--allocation-pool"

the full command : 
$ neutron subnet-create external_network 10.35.166.0/24 --disable-dhcp 
--gateway 10.35.166.254  --allocation-pool start=10.35.166.1,end=10.35.166.100

When we want to update the subnet we need to use this flags : 
--allocation-pools type=dict list=true start=10.35.166.1,end=10.35.166.55

the full command is : 
[root@cougar16 ~(keystone_admin)]# neutron  subnet-update 
c609b9ce-18d7-4b44-b8e0-5354a7b92caa --allocation-pools type=dict list=true 
start=10.35.166.1,end=10.35.166.55
Updated subnet: c609b9ce-18d7-4b44-b8e0-5354a7b92caa


Version-Release number of selected component (if applicable):

[root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron 
openstack-neutron-2014.1.5-2.el7ost.noarch
python-neutronclient-2.3.4-3.el7ost.noarch
python-neutron-2014.1.5-2.el7ost.noarch
openstack-neutron-ml2-2014.1.5-2.el7ost.noarch
openstack-neutron-openvswitch-2014.1.5-2.el7ost.noarch
How reproducible:


Steps to Reproduce:
1.Install OSP 5 on  RHEL 7.1 
2.run the command : neutron net-create external_network 
--provider:network_type=vlan  --provider:segmentation_id=181 
--provider:physical_network physnet --router:external

3.run the command : neutron subnet-create external_network
10.35.166.0/24 --disable-dhcp --gateway 10.35.166.254  --allocation-pool
start=10.35.166.1,end=10.35.166.100

4. neutron subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa --allocation-pool 
start=10.35.166.1,end=10.35.166.90
Unrecognized attribute(s) 'allocation_pool'
Actual results:

5.neutron subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa --allocation-pools 
start=10.35.166.1,end=10.35.166.90
Invalid input for allocation_pools. Reason: Invalid data format for IP pool: 
'start=10.35.166.1,end=10.35.166.90'.


Expected results:
the command in step 4 should work.

Additional info:
the command that work is : 
neutron  subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa --allocation-pools 
type=dict list=true start=10.35.166.1,end=10.35.166.55
Updated subnet: c609b9ce-18d7-4b44-b8e0-5354a7b92caa

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Inconsistent between subnet-create & subnet-update command

Status in neutron:
  New

Bug description:
  Description of problem:
  When creating subnet with allocation pool we using flag that calls :  " 
--allocation-pool"

  the full command : 
  $ neutron subnet-create external_network 10.35.166.0/24 --disable-dhcp 
--gateway 10.35.166.254  --allocation-pool start=10.35.166.1,end=10.35.166.100

  When we want to update the subnet we need to use this flags : 
  --allocation-pools type=dict list=true start=10.35.166.1,end=10.35.166.55

  the full command is : 
  [root@cougar16 ~(keystone_admin)]# neutron  subnet-update 
c609b9ce-18d7-4b44-b8e0-5354a7b92caa --allocation-pools type=dict list=true 
start=10.35.166.1,end=10.35.166.55
  Updated subnet: c609b9ce-18d7-4b44-b8e0-5354a7b92caa


  Version-Release number of selected component (if applicable):

  [root@cougar16 ~(keystone_admin)]# rpm -qa |grep neutron 
  openstack-neutron-2014.1.5-2.el7ost.noarch
  python-neutronclient-2.3.4-3.el7ost.noarch
  python-neutron-2014.1.5-2.el7ost.noarch
  openstack-neutron-ml2-2014.1.5-2.el7ost.noarch
  openstack-neutron-openvswitch-2014.1.5-2.el7ost.noarch
  How reproducible:

  
  Steps to Reproduce:
  1.Install OSP 5 on  RHEL 7.1 
  2.run the command : neutron net-create external_network 
--provider:network_type=vlan  --provider:segmentation_id=181 
--provider:physical_network physnet --router:external

  3.run the command : neutron subnet-create external_network
  10.35.166.0/24 --disable-dhcp --gateway 10.35.166.254  --allocation-
  pool start=10.35.166.1,end=10.35.166.100

  4. neutron subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa 
--allocation-pool start=10.35.166.1,end=10.35.166.90
  Unrecognized attribute(s) 'allocation_pool'
  Actual results:

  5.neutron subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa 
--allocation-pools start=10.35.166.1,end=10.35.166.90
  Invalid input for allocation_pools. Reason: Invalid data format for IP pool: 
'start=10.35.166.1,end=10.35.166.90'.

  
  Expected results:
  the command in step 4 should work.

  Additional info:
  the command that work is : 
  neutron  subnet-update c609b9ce-18d7-4b44-b8e0-5354a7b92caa 
--allocation-pools type=dict list=true start=10.35.166.1,end=10.35.166.55
  Updated subnet: c609b9ce-18d7-4b44-b8e0-5354a7b92caa

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : htt

[Yahoo-eng-team] [Bug 1477097] [NEW] fwaas: firewall in error status after update firewall-rule

[Eran Kuris]

Public bug reported:

[root@puma16 ~(keystone_admin)]# neutron firewall-show 
c9478714-20e3-4163-97ad-212cdac04434
++--+
| Field  | Value|
++--+
| admin_state_up | True |
| description|  |
| firewall_policy_id | 48f5dba2-a252-4783-858e-b5ea61f8eb6e |
| id | c9478714-20e3-4163-97ad-212cdac04434 |
| name   |  |
| router_ids | 9143a9b9-d5ff-4555-8961-6d6649f95226 |
| status | ACTIVE   |
| tenant_id  | ffa0f8d8d51849a4ab67651e4bebcbba |
++--+
[root@puma16 ~(keystone_admin)]#  neutron firewall-rule-update
usage: neutron firewall-rule-update [-h] [--request-format {json,xml}]
[--protocol {tcp,udp,icmp,any}]
FIREWALL_RULE
neutron firewall-rule-update: error: too few arguments
[root@puma16 ~(keystone_admin)]#  neutron firewall-rule-update 
28767fca-cdcc-4bff-bcde-025b7d5c2411--action deny
Invalid values_specs deny
[root@puma16 ~(keystone_admin)]#  neutron firewall-rule-update 
28767fca-cdcc-4bff-bcde-025b7d5c2411 --action deny
Updated firewall_rule: 28767fca-cdcc-4bff-bcde-025b7d5c2411
[root@puma16 ~(keystone_admin)]# neutron firewall-show 
c9478714-20e3-4163-97ad-212cdac04434
++--+
| Field  | Value|
++--+
| admin_state_up | True |
| description|  |
| firewall_policy_id | 48f5dba2-a252-4783-858e-b5ea61f8eb6e |
| id | c9478714-20e3-4163-97ad-212cdac04434 |
| name   |  |
| router_ids | 9143a9b9-d5ff-4555-8961-6d6649f95226 |
| status | ERROR|
| tenant_id  | ffa0f8d8d51849a4ab67651e4bebcbba |
++--+

[root@puma16 ~(keystone_admin)]# 
[root@puma16 ~(keystone_admin)]# rpm -qa |grep openstack-packstack
openstack-packstack-puppet-2015.1-0.11.dev1589.g1d6372f.el7ost.noarch
openstack-packstack-2015.1-0.11.dev1589.g1d6372f.el7ost.noarch
[root@puma16 ~(keystone_admin)]# rpm -qa |grep openstack-puppet-modules
openstack-puppet-modules-2015.1.8-8.el7ost.noarch
[root@puma16 ~(keystone_admin)]# rpm -qa |grep neutron
openstack-neutron-2015.1.0-12.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-12.el7ost.noarch
python-neutron-2015.1.0-12.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-common-2015.1.0-12.el7ost.noarch
openstack-neutron-ml2-2015.1.0-12.el7ost.noarch


l3-agent log :
2015-07-22 13:42:01.804 8908 INFO neutron.callbacks.manager 
[req-e57bf79f-416f-48b6-9a23-ed01bf6b2846 ] Notify callbacks for router, 
after_create
2015-07-22 13:42:01.805 8908 INFO neutron.callbacks.manager 
[req-e57bf79f-416f-48b6-9a23-ed01bf6b2846 ] Calling callback 
neutron.agent.metadata.driver.after_router_added
2015-07-22 13:42:03.025 8908 INFO neutron.callbacks.manager 
[req-e57bf79f-416f-48b6-9a23-ed01bf6b2846 ] Notify callbacks for router, 
before_update
2015-07-22 13:42:03.593 8908 INFO neutron.callbacks.manager 
[req-e57bf79f-416f-48b6-9a23-ed01bf6b2846 ] Notify callbacks for router, 
after_update
2015-07-22 13:48:50.478 8908 INFO neutron.callbacks.manager [-] Notify 
callbacks for router, before_update
2015-07-22 13:48:50.941 8908 INFO neutron.callbacks.manager [-] Notify 
callbacks for router, after_update


neutron-server.log : 
2015-07-22 14:22:05.834 9105 INFO neutron.wsgi [-] (9105) accepted 
('10.35.160.41', 49128)
2015-07-22 14:22:05.918 9105 INFO neutron.wsgi 
[req-cf14cbb2-4c81-4e4f-93e1-3b8f0c829241 ] 10.35.160.41 - - [22/Jul/2015 
14:22:05] "GET 
/v2.0/fw/firewall_rules.json?fields=id&id=28767fca-cdcc-4bff-bcde-025b7d5c2411 
HTTP/1.1" 200 281 0.082675
2015-07-22 14:22:06.002 9116 INFO neutron.wsgi 
[req-2d500a7a-79d8-4915-8c16-58f681ac0dad ] 10.35.160.41 - - [22/Jul/2015 
14:22:06] "GET 
/v2.0/ports.json?device_id=22306c02-13e9-44cb-a69a-790f2797e380&device_id=047af1bb-07a8-4720-ac7b-dcf5ff9ca049
 HTTP/1.1" 200 1714 0.102604
2015-07-22 14:22:06.008 9105 INFO neutron.wsgi 
[req-1129feb4-ebb7-48fe-8e5d-99bd4b6aedd7 ] 10.35.160.41 - - [22/Jul/2015 
14:22:06] "PUT 
/v2.0/fw/firewall_rules/28767fca-cdcc-4bff-bcde-025b7d5c2411.json HTTP/1.1" 200 
632 0.086929
2015-07-22 14:22:06.026 9116 INFO neutron.wsgi 
[req-180227d6-8160-48dd-ad3d-e48d0e4d4049 ] 10.35.160.41 - - [22/Jul/2015 
14:22:06] "GET 
/v2.0/security-groups.json?id

[Yahoo-eng-team] [Bug 1476674] [NEW] During image update metadata Danger: There was an error submitting the form. Please try again.

[Eran Kuris]

Public bug reported:

Log in to horizon as  Admin user  Navigate to image in admin Tab 
create image and then type on " update metadata" 

we get error : Danger: There was an error submitting the form. Please
try again.

In log file  of horizon : 
2015-07-21 13:35:14,607 28006 ERROR django.request Internal Server Error: 
/dashboard/admin/images/06b7c500-768c-4c17-abbe-7a5258674cd2/update_metadata/
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 
132, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec
return view_func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 52, in dec
return view_func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec
return view_func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 
71, in view
return self.dispatch(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 
89, in dispatch
return handler(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/django/views/generic/edit.py", line 
215, in post
return self.form_valid(form)
  File "/usr/lib/python2.7/site-packages/horizon/forms/views.py", line 173, in 
form_valid
exceptions.handle(self.request)
  File "/usr/lib/python2.7/site-packages/horizon/exceptions.py", line 364, in 
handle
six.reraise(exc_type, exc_value, exc_traceback)
  File "/usr/lib/python2.7/site-packages/horizon/forms/views.py", line 170, in 
form_valid
handled = form.handle(self.request, form.cleaned_data)
  File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/images/forms.py",
 line 65, in handle
_('Unable to update the image metadata.'))
  File "/usr/lib/python2.7/site-packages/horizon/exceptions.py", line 364, in 
handle
six.reraise(exc_type, exc_value, exc_traceback)
  File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/images/forms.py",
 line 48, in handle
new_metadata = json.loads(self.data['metadata'])
  File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
return _default_decoder.decode(s)
  File "/usr/lib64/python2.7/json/decoder.py", line 365, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python2.7/json/decoder.py", line 383, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded


version : 
[root@puma16 ~(keystone_admin)]# rpm -qa |grep horizon 
python-django-horizon-2015.1.0-10.el7ost.noarch

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1476674

Title:
  During image update metadata Danger: There was an error submitting the
  form. Please try again.

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Log in to horizon as  Admin user  Navigate to image in admin Tab 
  create image and then type on " update metadata" 

  we get error : Danger: There was an error submitting the form. Please
  try again.

  In log file  of horizon : 
  2015-07-21 13:35:14,607 28006 ERROR django.request Internal Server Error: 
/dashboard/admin/images/06b7c500-768c-4c17-abbe-7a5258674cd2/update_metadata/
  Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 
132, in get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in 
dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in 
dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 52, in 
dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in 
dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in 
dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 
71, in view
  return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packa

[Yahoo-eng-team] [Bug 1465513] [NEW] VM get incorrect default gateway when attached port DG manually to router

[Eran Kuris]

Public bug reported:

When I create neutron port and attach it to router as "default gateway"
and  launch  VM I can see that VM get ip address of default gateway that
not match to ip address of neutron router port. It  get the ip gateway
from subnet configuration which is  x.y.z.1

Version: OSP 7 on rhel 7.1
# rpm -qa |grep dnsmasq
dnsmasq-utils-2.67-1.fc20.x86_64
dnsmasq-2.67-1.fc20.x86_64
[root@puma15 ~(keystone_admin)]# rpm -qa |grep neutron
python-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-2015.1.0-1.el7ost.noarch
python-neutron-lbaas-2015.1.0-3.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-3.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-common-2015.1.0-1.el7ost.noarch

step to reproduce : 
1. Create a neutron tenant network. 
2. Create an IPv4 subnet for the network (say 192.168.1.0/24 with  gateway_ip 
as 192.168.1.1) 
3. Create a neutron router (say router1). 
4. Create a port on the tenant network (without specifying any  fixed_ip). The 
port would be allocated a free IP from the allocation  pool (i.e., say 
192.168.1.3). 
5. Now attach this port to the neutron router (i.e., neutron  
router-interface-add  ) 
6. Spawn some VMs with the above network. 
Observations: 
VMs would acquire IP address (something like 192.168.1.4) with a default  
gateway as 192.168.1.1 and not the ip 192.168.1.3 (i.e., ip of the port  which 
is attached to the neutron router)

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  VM get incorrect default gateway when attached port DG manually to
  router

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When I create neutron port and attach it to router as "default
  gateway"  and  launch  VM I can see that VM get ip address of default
  gateway that not match to ip address of neutron router port. It  get
  the ip gateway  from subnet configuration which is  x.y.z.1

  Version: OSP 7 on rhel 7.1
  # rpm -qa |grep dnsmasq
  dnsmasq-utils-2.67-1.fc20.x86_64
  dnsmasq-2.67-1.fc20.x86_64
  [root@puma15 ~(keystone_admin)]# rpm -qa |grep neutron
  python-neutron-2015.1.0-1.el7ost.noarch
  openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
  openstack-neutron-2015.1.0-1.el7ost.noarch
  python-neutron-lbaas-2015.1.0-3.el7ost.noarch
  python-neutronclient-2.4.0-1.el7ost.noarch
  openstack-neutron-lbaas-2015.1.0-3.el7ost.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch
  python-neutron-fwaas-2015.1.0-3.el7ost.noarch
  openstack-neutron-common-2015.1.0-1.el7ost.noarch

  step to reproduce : 
  1. Create a neutron tenant network. 
  2. Create an IPv4 subnet for the network (say 192.168.1.0/24 with  gateway_ip 
as 192.168.1.1) 
  3. Create a neutron router (say router1). 
  4. Create a port on the tenant network (without specifying any  fixed_ip). 
The port would be allocated a free IP from the allocation  pool (i.e., say 
192.168.1.3). 
  5. Now attach this port to the neutron router (i.e., neutron  
router-interface-add  ) 
  6. Spawn some VMs with the above network. 
  Observations: 
  VMs would acquire IP address (something like 192.168.1.4) with a default  
gateway as 192.168.1.1 and not the ip 192.168.1.3 (i.e., ip of the port  which 
is attached to the neutron router)

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1456206] [NEW] Instance is not assigned with an IP address (Version 4 or 6) when the network attached to it have two subnets - IPv4 and IPv6 (IPv6 can be stateful or stateless)

[Eran Kuris]

Public bug reported:

When create network with multiple  subnets  one IPv4 subnet &  second 
IPv6-stateful or IPv6 stateless
Instances that assign to this network does not  get 2 IP address  (IPv4&6).
Reproduce all the time , sometime instance get only one IP address IPv4 or  
IPv6 .

version :
OSP 7 on rhel 7.1
# rpm -qa |grep neutron 
openstack-neutron-fwaas-2015.1.0-2.el7ost.noarch
openstack-neutron-common-2015.1.0-1.el7ost.noarch
openstack-neutron-2015.1.0-1.el7ost.noarch
python-neutron-lbaas-2015.1.0-1.el7ost.noarch
openstack-neutron-ml2-2015.1.0-1.el7ost.noarch
python-neutronclient-2.3.11-1.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-1.el7ost.noarch
python-neutron-fwaas-2015.1.0-2.el7ost.noarch
python-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch
[root@puma15 ~(keystone_redhatadmin)]# rpm -qa |grep dnsmasq
dnsmasq-2.66-13.el7_1.x86_64
dnsmasq-utils-2.66-13.el7_1.x86_64

step to reproduce : 
1.Create network
   #neutron net-create internal_ipv4_6 --shared
2.. Create 2 subnets  and assign to the network 
# neutron subnet-create < internal_ipv4_6_id> 192.168.1.0/24 --name 
internal_ipv4_subnet 
   # neutron subnet-create < internal_ipv4_6_id> 2001:db2:0::2/64 --name 
dhcpv6_stateless_subnet --ipv6-ra-mode dhcpv6-stateless --ipv6-address-mode 
dhcpv6-stateless --ip-version 6 
3. Router creation
# neutron router-create router
# neutron router-interface-add Router 
# neutron router-interface-add Router 
 4.  launce VM with network that you created .  
   #nova boot --flavor 3 --image  VM1 --nic net-id=

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Instance is not assigned with an IP address (Version 4 or 6) when the
  network attached to it have two subnets  - IPv4 and IPv6 (IPv6 can be
  stateful or stateless)

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When create network with multiple  subnets  one IPv4 subnet &  second 
IPv6-stateful or IPv6 stateless
  Instances that assign to this network does not  get 2 IP address  (IPv4&6).
  Reproduce all the time , sometime instance get only one IP address IPv4 or  
IPv6 .

  version :
  OSP 7 on rhel 7.1
  # rpm -qa |grep neutron 
  openstack-neutron-fwaas-2015.1.0-2.el7ost.noarch
  openstack-neutron-common-2015.1.0-1.el7ost.noarch
  openstack-neutron-2015.1.0-1.el7ost.noarch
  python-neutron-lbaas-2015.1.0-1.el7ost.noarch
  openstack-neutron-ml2-2015.1.0-1.el7ost.noarch
  python-neutronclient-2.3.11-1.el7ost.noarch
  openstack-neutron-lbaas-2015.1.0-1.el7ost.noarch
  python-neutron-fwaas-2015.1.0-2.el7ost.noarch
  python-neutron-2015.1.0-1.el7ost.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch
  [root@puma15 ~(keystone_redhatadmin)]# rpm -qa |grep dnsmasq
  dnsmasq-2.66-13.el7_1.x86_64
  dnsmasq-utils-2.66-13.el7_1.x86_64

  step to reproduce : 
  1.Create network
 #neutron net-create internal_ipv4_6 --shared
  2.. Create 2 subnets  and assign to the network 
  # neutron subnet-create < internal_ipv4_6_id> 192.168.1.0/24 --name 
internal_ipv4_subnet 
 # neutron subnet-create < internal_ipv4_6_id> 2001:db2:0::2/64 --name 
dhcpv6_stateless_subnet --ipv6-ra-mode dhcpv6-stateless --ipv6-address-mode 
dhcpv6-stateless --ip-version 6 
  3. Router creation
  # neutron router-create router
  # neutron router-interface-add Router 
  # neutron router-interface-add Router 
   4.  launce VM with network that you created .  
 #nova boot --flavor 3 --image  VM1 --nic net-id=

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1453671] Re: --port_security_enabled flag does not exist in neutron net/port-create/update help

[Eran Kuris]

** Project changed: neutron => python-neutronclient

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

Title:
  --port_security_enabled flag  does not exist in neutron net/port-
  create/update help

Status in Python client library for Neutron:
  New

Bug description:
  When printing  help of  neutron net-create  / neutron net-update / neutron 
port-create / neutron port-update 
  there is no explanation of new flag : --port_security_enabled.

  version:

  # rpm -qa |grep neutron
  python-neutronclient-2.3.11-1.el7.noarch
  openstack-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-ml2-2015.1.0-1.el7.noarch
  openstack-neutron-lbaas-2015.1.0-1.el7.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7.noarch
  python-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-common-2015.1.0-1.el7.noarch
  python-neutron-lbaas-2015.1.0-1.el7.noarch

  
  example of help output(It is relevant to all the commands I mentioned up) : 
  # neutron help net-create 
  usage: neutron net-create [-h] [-f {shell,table,value}] [-c COLUMN]
[--max-width ] [--prefix PREFIX]
[--request-format {json,xml}]
[--tenant-id TENANT_ID] [--admin-state-down]
[--shared] [--router:external]
[--provider:network_type ]
[--provider:physical_network 
]
[--provider:segmentation_id ]
NAME

  Create a network for a given tenant.

  positional arguments:
NAME  Name of network to create.

  optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
  The XML or JSON request format.
--tenant-id TENANT_ID
  The owner tenant ID.
--admin-state-downSet admin state up to false.
--shared  Set the network as shared.
--router:external Set network as external, it is only available for
  admin
--provider:network_type 
  The physical mechanism by which the virtual network is
  implemented.
--provider:physical_network 
  Name of the physical network over which the virtual
  network is implemented.
--provider:segmentation_id 
  VLAN ID for VLAN networks or tunnel-id for GRE/VXLAN
  networks.

  output formatters:
output formatter options

-f {shell,table,value}, --format {shell,table,value}
  the output format, defaults to table
-c COLUMN, --column COLUMN
  specify the column(s) to include, can be repeated

  table formatter:
--max-width 
  Maximum display width, 0 to disable

  shell formatter:
a format a UNIX shell can parse (variable="value")

--prefix PREFIX   add a prefix to all variable names

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1453671/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1454148] [NEW] Request Failed after enabled extension_drivers=port_security and network already exist

[Eran Kuris]

Public bug reported:

When I have environment that already  exist  (VM , network, routers) and  after 
that I enabling extension_drivers=port_security
in /etc/neutron/plugin.ini  after I restart neutron services  I get " Request 
Failed: internal server error while processing your request. "
when I typing neutron command.

in neutron server.log I have those  error : 
attached log file 


If I  remove all environment  and that restart neutron service  there is no 
error . 
when enabling  extension_drivers=port_security  it  should propagate to exist 
setup.

version : 
]# rpm -qa |grep neutron
openstack-neutron-fwaas-2015.1.0-2.el7ost.noarch
openstack-neutron-common-2015.1.0-1.el7ost.noarch
openstack-neutron-2015.1.0-1.el7ost.noarch
python-neutron-lbaas-2015.1.0-1.el7ost.noarch
openstack-neutron-ml2-2015.1.0-1.el7ost.noarch
python-neutronclient-2.3.11-1.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-1.el7ost.noarch
python-neutron-fwaas-2015.1.0-2.el7ost.noarch
python-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "port_Sec"
   https://bugs.launchpad.net/bugs/1454148/+attachment/4396086/+files/port_Sec

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

Title:
  Request Failed after enabled extension_drivers=port_security and
  network already exist

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When I have environment that already  exist  (VM , network, routers) and  
after that I enabling extension_drivers=port_security
  in /etc/neutron/plugin.ini  after I restart neutron services  I get " Request 
Failed: internal server error while processing your request. "
  when I typing neutron command.

  in neutron server.log I have those  error : 
  attached log file 

  
  If I  remove all environment  and that restart neutron service  there is no 
error . 
  when enabling  extension_drivers=port_security  it  should propagate to exist 
setup.

  version : 
  ]# rpm -qa |grep neutron
  openstack-neutron-fwaas-2015.1.0-2.el7ost.noarch
  openstack-neutron-common-2015.1.0-1.el7ost.noarch
  openstack-neutron-2015.1.0-1.el7ost.noarch
  python-neutron-lbaas-2015.1.0-1.el7ost.noarch
  openstack-neutron-ml2-2015.1.0-1.el7ost.noarch
  python-neutronclient-2.3.11-1.el7ost.noarch
  openstack-neutron-lbaas-2015.1.0-1.el7ost.noarch
  python-neutron-fwaas-2015.1.0-2.el7ost.noarch
  python-neutron-2015.1.0-1.el7ost.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1453676] [NEW] --port-security-enabled=False/True option does not exist in network creation / update

[Eran Kuris]

Public bug reported:

According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
We need to add support of port-security-enabled=False/True when creating and 
updating network.
version :
]# rpm -qa |grep horizon
python-django-horizon-2015.1.0-2.el7.noarch


this flag relevant to port creation  but it related to this bug :
https://bugs.launchpad.net/horizon/+bug/1432373

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1453676

Title:
  --port-security-enabled=False/True option does not exist in network
  creation / update

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
  We need to add support of port-security-enabled=False/True when creating and 
updating network.
  version :
  ]# rpm -qa |grep horizon
  python-django-horizon-2015.1.0-2.el7.noarch


  this flag relevant to port creation  but it related to this bug :
  https://bugs.launchpad.net/horizon/+bug/1432373

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1453671] [NEW] --port_security_enabled flag does not exist in neutron net/port-create/update help

[Eran Kuris]

Public bug reported:

When printing  help of  neutron net-create  / neutron net-update / neutron 
port-create / neutron port-update 
there is no explanation of new flag : --port_security_enabled.

version:

# rpm -qa |grep neutron
python-neutronclient-2.3.11-1.el7.noarch
openstack-neutron-2015.1.0-1.el7.noarch
openstack-neutron-ml2-2015.1.0-1.el7.noarch
openstack-neutron-lbaas-2015.1.0-1.el7.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7.noarch
python-neutron-2015.1.0-1.el7.noarch
openstack-neutron-common-2015.1.0-1.el7.noarch
python-neutron-lbaas-2015.1.0-1.el7.noarch


example of help output(It is relevant to all the commands I mentioned up) : 
# neutron help net-create 
usage: neutron net-create [-h] [-f {shell,table,value}] [-c COLUMN]
  [--max-width ] [--prefix PREFIX]
  [--request-format {json,xml}]
  [--tenant-id TENANT_ID] [--admin-state-down]
  [--shared] [--router:external]
  [--provider:network_type ]
  [--provider:physical_network ]
  [--provider:segmentation_id ]
  NAME

Create a network for a given tenant.

positional arguments:
  NAME  Name of network to create.

optional arguments:
  -h, --helpshow this help message and exit
  --request-format {json,xml}
The XML or JSON request format.
  --tenant-id TENANT_ID
The owner tenant ID.
  --admin-state-downSet admin state up to false.
  --shared  Set the network as shared.
  --router:external Set network as external, it is only available for
admin
  --provider:network_type 
The physical mechanism by which the virtual network is
implemented.
  --provider:physical_network 
Name of the physical network over which the virtual
network is implemented.
  --provider:segmentation_id 
VLAN ID for VLAN networks or tunnel-id for GRE/VXLAN
networks.

output formatters:
  output formatter options

  -f {shell,table,value}, --format {shell,table,value}
the output format, defaults to table
  -c COLUMN, --column COLUMN
specify the column(s) to include, can be repeated

table formatter:
  --max-width 
Maximum display width, 0 to disable

shell formatter:
  a format a UNIX shell can parse (variable="value")

  --prefix PREFIX   add a prefix to all variable names

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  --port_security_enabled flag  does not exist in neutron net/port-
  create/update help

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When printing  help of  neutron net-create  / neutron net-update / neutron 
port-create / neutron port-update 
  there is no explanation of new flag : --port_security_enabled.

  version:

  # rpm -qa |grep neutron
  python-neutronclient-2.3.11-1.el7.noarch
  openstack-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-ml2-2015.1.0-1.el7.noarch
  openstack-neutron-lbaas-2015.1.0-1.el7.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7.noarch
  python-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-common-2015.1.0-1.el7.noarch
  python-neutron-lbaas-2015.1.0-1.el7.noarch

  
  example of help output(It is relevant to all the commands I mentioned up) : 
  # neutron help net-create 
  usage: neutron net-create [-h] [-f {shell,table,value}] [-c COLUMN]
[--max-width ] [--prefix PREFIX]
[--request-format {json,xml}]
[--tenant-id TENANT_ID] [--admin-state-down]
[--shared] [--router:external]
[--provider:network_type ]
[--provider:physical_network 
]
[--provider:segmentation_id ]
NAME

  Create a network for a given tenant.

  positional arguments:
NAME  Name of network to create.

  optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
  The XML or JSON request format.
--tenant-id TENANT_ID
  The owner tenant ID.
--admin-state-downSet admin state up to false.
--shared  Set the network as shared.
--router:external Set network as external, it is only available for
  admin
--provider:network_type 
  The physical mechanism by which the virtual network is
 

[Yahoo-eng-team] [Bug 1453667] [NEW] Changing --port_security_enabled=False in network does not propagated to already existing ports

[Eran Kuris]

Public bug reported:

According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496 
Port that already created from network with --port_security_enabled=True  will 
not updated to False when we update network to --port_security_enabled=False.
Version:
# rpm -qa |grep neutron
python-neutronclient-2.3.11-1.el7.noarch
openstack-neutron-2015.1.0-1.el7.noarch
openstack-neutron-ml2-2015.1.0-1.el7.noarch
openstack-neutron-lbaas-2015.1.0-1.el7.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7.noarch
python-neutron-2015.1.0-1.el7.noarch
openstack-neutron-common-2015.1.0-1.el7.noarch
python-neutron-lbaas-2015.1.0-1.el7.noarch

enter to plugin.ini and enable port-security extension:
[root@puma15]# vi /etc/neutron/plugin.ini extension_drivers=port_security
* you have to restart neutron server service : 
#openstack-service restart neutron-server
1. Create internal network & subnet 
# neutron net-create int_net
# neutron net-show int_net | grep port_security_enabled
# neutron subnet-create  192.168.1.0/24 --name ipv4_subnet --ip-version 
4 --dns_nameservers list=true 10.35.28.28 
2. create neutron router 
#neutron router-create Router_eNet
3. create interface for internal network in the router 
#neutron router-interface-add Router_eNet 
4. create gateway for the router
#neutron router-gateway-set Router_eNet  
5. Launch 2 instances 
6.#neutron net-update int_net --port-security-enabled=False 
7. check the port of exist VM  its still in True .

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Changing --port_security_enabled=False in network does not propagated
  to already existing ports

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496 
  Port that already created from network with --port_security_enabled=True  
will not updated to False when we update network to 
--port_security_enabled=False.
  Version:
  # rpm -qa |grep neutron
  python-neutronclient-2.3.11-1.el7.noarch
  openstack-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-ml2-2015.1.0-1.el7.noarch
  openstack-neutron-lbaas-2015.1.0-1.el7.noarch
  openstack-neutron-openvswitch-2015.1.0-1.el7.noarch
  python-neutron-2015.1.0-1.el7.noarch
  openstack-neutron-common-2015.1.0-1.el7.noarch
  python-neutron-lbaas-2015.1.0-1.el7.noarch

  enter to plugin.ini and enable port-security extension:
  [root@puma15]# vi /etc/neutron/plugin.ini extension_drivers=port_security
  * you have to restart neutron server service : 
  #openstack-service restart neutron-server
  1. Create internal network & subnet 
  # neutron net-create int_net
  # neutron net-show int_net | grep port_security_enabled
  # neutron subnet-create  192.168.1.0/24 --name ipv4_subnet 
--ip-version 4 --dns_nameservers list=true 10.35.28.28 
  2. create neutron router 
  #neutron router-create Router_eNet
  3. create interface for internal network in the router 
  #neutron router-interface-add Router_eNet 
  4. create gateway for the router
  #neutron router-gateway-set Router_eNet  
  5. Launch 2 instances 
  6.#neutron net-update int_net --port-security-enabled=False 
  7. check the port of exist VM  its still in True .

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1447004] [NEW] LBaaS- Unclear error message when edit Healthmonitor "delay" value to be smaller than "Timeout"

[Eran Kuris]

Public bug reported:

When I trying to edit an exist "Healthmonitor"   with Delay value to be
smailler than timeout value I get unclear error message .

reproduce :
1.neutron lb-healthmonitor-create --delay 3 --type HTTP --max-retries 3 
--timeout 3
2. try to edit it with delay value  lower than  timeout value
# neutron lb-healthmonitor-list 
+--+--++
| id   | type | admin_state_up |
+--+--++
| 6b52d5f0-a1a2-4a37-a3dd-df740277f3a2 | HTTP | True   |
+--+--++

# neutron lb-healthmonitor-show  6b52d5f0-a1a2-4a37-a3dd-df740277f3a2
++-+
| Field  | Value
   |
++-+
| admin_state_up | True 
   |
| delay  | 3
   |
| expected_codes | 200  
   |
| http_method| GET  
   |
| id | 6b52d5f0-a1a2-4a37-a3dd-df740277f3a2 
   |
| max_retries| 3
   |
| pools  | {"status": "ACTIVE", "status_description": null, "pool_id": 
"8c576c3a-75a0-4579-b908-7060df1ee01c"} |
| tenant_id  | 597cc04c77ee44eeb7b878f63a24eac9 
   |
| timeout| 3
   |
| type   | HTTP 
   |
| url_path   | /
   |
++-+

# neutron lb-healthmonitor-update   6b52d5f0-a1a2-4a37-a3dd-df740277f3a2 
--delay 1
Bad Request (HTTP 400) (Request-ID: req-34ddb573-b0ef-43de-ba92-dc446f612add)

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  LBaaS- Unclear error message when edit Healthmonitor "delay" value to
  be smaller than "Timeout"

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When I trying to edit an exist "Healthmonitor"   with Delay value to
  be smailler than timeout value I get unclear error message .

  reproduce :
  1.neutron lb-healthmonitor-create --delay 3 --type HTTP --max-retries 3 
--timeout 3
  2. try to edit it with delay value  lower than  timeout value
  # neutron lb-healthmonitor-list 
  +--+--++
  | id   | type | admin_state_up |
  +--+--++
  | 6b52d5f0-a1a2-4a37-a3dd-df740277f3a2 | HTTP | True   |
  +--+--++

  # neutron lb-healthmonitor-show  6b52d5f0-a1a2-4a37-a3dd-df740277f3a2
  
++-+
  | Field  | Value  
 |
  
++-+
  | admin_state_up | True   
 |
  | delay  | 3  
 |
  | expected_codes | 200
 |
  | http_method| GET
 |
  | id | 6b52d5f0-a1a2-4a37-a3dd-df740277f3a2   
 |
  | max_retries| 3  
  

[Yahoo-eng-team] [Bug 1446997] [NEW] LBaaS-Healthmonitor -Unclear

[Eran Kuris]

Public bug reported:

In Horizon under  "Load- Balance" --> "Monitors"  
When I trying to edit an exist "Healthmonitor" there is no  clear legend  that 
explain  that "Delay"=>"Timeout"
When I trying to config Delay to be smailler then timeout value I get  unclear 
error message .
1. Should add legend to explain that "Delay"= >"Timeout"  (equal or grater then)
2. Should fix error message when edit "delay" value to be smaller then 
"Timeout"  to be clear 

attached screen shot

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: "lbaas.tar"
   https://bugs.launchpad.net/bugs/1446997/+attachment/4381095/+files/lbaas.tar

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1446997

Title:
  LBaaS-Healthmonitor -Unclear

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Horizon under  "Load- Balance" --> "Monitors"  
  When I trying to edit an exist "Healthmonitor" there is no  clear legend  
that explain  that "Delay"=>"Timeout"
  When I trying to config Delay to be smailler then timeout value I get  
unclear error message .
  1. Should add legend to explain that "Delay"= >"Timeout"  (equal or grater 
then)
  2. Should fix error message when edit "delay" value to be smaller then 
"Timeout"  to be clear 

  attached screen shot

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1445004] [NEW] Horizon- there is no option to edit instance for hotplug NIC

[Eran Kuris]

Public bug reported:

It is not possible in  Horizon to edit instances that  already launched
for  adding  hotplug NIC .

version : openstack Juno , OS rhel 7.1
libreport-rhel-2.1.11-21.el7.x86_64
# rpm -qa |grep horizon
python-django-horizon-2014.2.2-2.el7ost.noarch
step to reproduce :
1. Connect to OSP via Horizon 
2. Create 2 network
3. Launch instance   with one hotplug NIC 
4. After the instance is running  try to edit it to add hotplug NIC --- it is 
not possible .  

in Nova it is supported : 
# nova interface-attach

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1445004

Title:
  Horizon- there is no option to edit instance for hotplug NIC

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  It is not possible in  Horizon to edit instances that  already
  launched for  adding  hotplug NIC .

  version : openstack Juno , OS rhel 7.1
  libreport-rhel-2.1.11-21.el7.x86_64
  # rpm -qa |grep horizon
  python-django-horizon-2014.2.2-2.el7ost.noarch
  step to reproduce :
  1. Connect to OSP via Horizon 
  2. Create 2 network
  3. Launch instance   with one hotplug NIC 
  4. After the instance is running  try to edit it to add hotplug NIC --- it is 
not possible .  

  in Nova it is supported : 
  # nova interface-attach

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1429866] [NEW] Horizon does not display ID of Security Group

[Eran Kuris]

Public bug reported:

Horizon does not display UUID of security group.
When I create security group via CLI or Horizon  and I want to check the UUID 
of the security group via Horizon 
I can see that it does not display . It display only the name of security group 
.
The problem is bigger when I create few security groups with same name (this 
option is valid) .


version :

[root@puma15 ~(keystone_tenant_a)]# rpm -qa | grep  horizon
python-django-horizon-2014.2.2-2.el7ost.noarch
[root@puma15 ~(keystone_tenant_a)]# rpm -qa | grep  rhel
libreport-rhel-2.1.11-21.el7.x86_64
[root@puma15 yum.repos.d(keystone_tenant_a)]# cat rhos-release-6-rhel-7.1.repo 
#
# Release Engineering Builds
#
[rhelosp-6.0]
name=RHOS-6.0
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/$basearch/os
gpgcheck=0
enabled=1

[rhelosp-6.0-debug]
name=RHOS-6.0 Debuginfo
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/$basearch/debuginfo
gpgcheck=0
enabled=0

[rhelosp-6.0-sources]
name=RHOS-6.0 Sources
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/source
gpgcheck=0
enabled=0

#
# Development builds (poodles)
#
[rhelosp-6.0-poodle]
name=RHOS-6.0
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/latest/RHOS-6/$basearch/os
gpgcheck=0
enabled=0

[rhelosp-6.0-poodle-debug]
name=RHOS-6.0 Debuginfo
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/latest/RHOS-6/$basearch/debuginfo
gpgcheck=0
enabled=0

[rhelosp-6.0-poodle-sources]
name=RHOS-6.0 Sources
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/latest/RHOS-6/source
gpgcheck=0
enabled=0

# Flea repo for RHEL-OSP 6
[rhelosp-6.0-flea]
name=RHOS-6.0 Flea
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/fleas/latest
enabled=0
skip_if_unavailable=1
gpgcheck=0

# end substitution #

#
# Other dependencies
#
[rhelosp-rhel-7-common]
name=RHEL 7 Common
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhel-7-common/7.0/latest/RHEL-7-COMMON/$basearch/os/
enabled=1
gpgcheck=0


[rhelosp-rhel-7-server]
name=Red Hat Enterprise Linux $releasever - $basearch - Server
baseurl=http://download.lab.bos.redhat.com/composes/latest-RHEL7/compose/Server/$basearch/os/
enabled=1
gpgcheck=0

[rhelosp-rhel-7-server-opt]
name=Red Hat Enterprise Linux $releasever - $basearch - Server Optional
baseurl=http://download.lab.bos.redhat.com/composes/latest-RHEL7/compose/Server-optional/$basearch/os/
enabled=0
gpgcheck=0

[rhelosp-rhel-7-ha]
name=Red Hat Enterprise Linux $releasever - $basearch - HA
baseurl=http://download.eng.bos.redhat.com/composes/latest-RHEL7/compose/Server/$basearch/os/addons/HighAvailability/
enabled=1
gpgcheck=0

[rhelosp-rhel-7-z]
name=Red Hat Enterprise Linux $releasever - $basearch - Z-Stream
baseurl=http://download.lab.bos.redhat.com/rel-eng/repos/rhel-7.1-z/$basearch
enabled=0
gpgcheck=0

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1429866

Title:
  Horizon does not display  ID of Security Group

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Horizon does not display UUID of security group.
  When I create security group via CLI or Horizon  and I want to check the UUID 
of the security group via Horizon 
  I can see that it does not display . It display only the name of security 
group .
  The problem is bigger when I create few security groups with same name (this 
option is valid) .


  version :

  [root@puma15 ~(keystone_tenant_a)]# rpm -qa | grep  horizon
  python-django-horizon-2014.2.2-2.el7ost.noarch
  [root@puma15 ~(keystone_tenant_a)]# rpm -qa | grep  rhel
  libreport-rhel-2.1.11-21.el7.x86_64
  [root@puma15 yum.repos.d(keystone_tenant_a)]# cat 
rhos-release-6-rhel-7.1.repo 
  #
  # Release Engineering Builds
  #
  [rhelosp-6.0]
  name=RHOS-6.0
  
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/$basearch/os
  gpgcheck=0
  enabled=1

  [rhelosp-6.0-debug]
  name=RHOS-6.0 Debuginfo
  
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/$basearch/debuginfo
  gpgcheck=0
  enabled=0

  [rhelosp-6.0-sources]
  name=RHOS-6.0 Sources
  
baseurl=http://download.lab.bos.redhat.com/rel-eng/OpenStack/6.0-RHEL-7/latest/RH7-RHOS-6.0/source
  gpgcheck=0
  enabled=0

  #
  # Development builds (poodles)
  #
  [rhelosp-6.0-poodle]
  name=RHOS-6.0
  
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/latest/RHOS-6/$basearch/os
  gpgcheck=0
  enabled=0

  [rhelosp-6.0-poodle-debug]
  name=RHOS-6.0 Debuginfo
  
baseurl=http://ayanami.boston.devel.redhat.com/poodles/rhos-devel-ci/6.0/latest/RHOS-6/$basearch/debuginfo
  gpgcheck=0
  enabled=0

  [rhelosp-6.0-pood

[Yahoo-eng-team] [Bug 1423475] [NEW] It is possible to delete default security group via neutron client

[Eran Kuris]

Public bug reported:

When I enter to horizon (WebUI) with user admin and trying to delete default 
security group I get an error message that I cannot do this action.
When I run same scenario from neutron client by using this commands :
[root@puma15 ~(keystone_admin)]# neutron security-group-list 
+--+-+-+
| id   | name| description |
+--+-+-+
| 8f7a6756-60e4-45e2-a35a-673bcd9508aa | default | default |
+--+-+-+
[root@puma15 ~(keystone_admin)]# neutron security-group-delete 
8f7a6756-60e4-45e2-a35a-673bcd9508aa
Deleted security_group: 8f7a6756-60e4-45e2-a35a-673bcd9508aa

I can see that the action successful when it should not . After few seconds 
from delete action I type the command :
[root@puma15 ~(keystone_admin)]# neutron security-group-list 
+--+-+-+
| id   | name| description |
+--+-+-+
| e56b4c51-5324-405e-bc54-0044247b6b5b | default | default |
+--+-+-+


As we can see it generate a new default security group with new ID . 

Version : 
[root@puma15 ~(keystone_admin)]# rpm -qa | grep neut
python-neutron-2014.2.2-2.el7ost.noarch
openstack-neutron-openvswitch-2014.2.2-2.el7ost.noarch
openstack-neutron-2014.2.2-2.el7ost.noarch
openstack-neutron-ml2-2014.2.2-2.el7ost.noarch
python-neutronclient-2.3.9-1.el7ost.noarch
[root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel
libreport-rhel-2.1.11-21.el7.x86_64
[root@puma15 ~(keystone_admin)]# ll /etc/yum.repos.d/
total 48
-rw-r--r--. 1 root root   252 Feb 16 10:13 epel.repo
-rw---. 1 root root 24221 Feb 16 10:03 Eran_answer_file.txt
-rw-r--r--. 1 root root   358 Feb 16 09:34 redhat.repo
-rw-r--r--. 1 root root   165 Feb 16 09:34 rhel-optional.repo
-rw-r--r--. 1 root root   153 Feb 16 09:34 rhel-server.repo
-rw-r--r--. 1 root root  2316 Feb 16 09:44 rhos-release-6-rhel-7.1.repo
-rw-r--r--. 1 root root   122 Feb 13 01:06 rhos-release.repo

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  It is possible to delete default security group via neutron client

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When I enter to horizon (WebUI) with user admin and trying to delete default 
security group I get an error message that I cannot do this action.
  When I run same scenario from neutron client by using this commands :
  [root@puma15 ~(keystone_admin)]# neutron security-group-list 
  +--+-+-+
  | id   | name| description |
  +--+-+-+
  | 8f7a6756-60e4-45e2-a35a-673bcd9508aa | default | default |
  +--+-+-+
  [root@puma15 ~(keystone_admin)]# neutron security-group-delete 
8f7a6756-60e4-45e2-a35a-673bcd9508aa
  Deleted security_group: 8f7a6756-60e4-45e2-a35a-673bcd9508aa

  I can see that the action successful when it should not . After few seconds 
from delete action I type the command :
  [root@puma15 ~(keystone_admin)]# neutron security-group-list 
  +--+-+-+
  | id   | name| description |
  +--+-+-+
  | e56b4c51-5324-405e-bc54-0044247b6b5b | default | default |
  +--+-+-+

  
  As we can see it generate a new default security group with new ID . 

  Version : 
  [root@puma15 ~(keystone_admin)]# rpm -qa | grep neut
  python-neutron-2014.2.2-2.el7ost.noarch
  openstack-neutron-openvswitch-2014.2.2-2.el7ost.noarch
  openstack-neutron-2014.2.2-2.el7ost.noarch
  openstack-neutron-ml2-2014.2.2-2.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  [root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel
  libreport-rhel-2.1.11-21.el7.x86_64
  [root@puma15 ~(keystone_admin)]# ll /etc/yum.repos.d/
  total 48
  -rw-r--r--. 1 root root   252 Feb 16 10:13 epel.repo
  -rw---. 1 root root 24221 Feb 16 10:03 Eran_answer_file.txt
  -rw-r--r--. 1 root root   358 Feb 16 09:34 redhat.repo
  -rw-r--r--. 1 root root   165 Feb 16 09:34 rhel-optional.repo
  -rw-r--r--. 1 root root   153 Feb 16 09:34 rhel-server.repo
  -rw-r--r--. 1 root root  2316 Feb 16 09:44 rhos-release-6-rhel-7.1.repo
  -rw-r--r--. 1 root root   122 Feb 13 01:06 rhos-release.repo

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

[Yahoo-eng-team] [Bug 1423168] [NEW] no error when adding an already-associated security group to a running instance

[Eran Kuris]

Public bug reported:

I don't get any error message when I try to associate VM to security
group when it already assigned to this  security group .

version : 
[root@puma15 ~(keystone_admin)]# rpm -qa | grep neu
python-neutron-2014.2.2-2.el7ost.noarch
openstack-neutron-openvswitch-2014.2.2-2.el7ost.noarch
openstack-neutron-2014.2.2-2.el7ost.noarch
openstack-neutron-ml2-2014.2.2-2.el7ost.noarch
python-neutronclient-2.3.9-1.el7ost.noarch
[root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel 
libreport-rhel-2.1.11-21.el7.x86_64
 rhos-release-6-rhel-7.1.repo

1. List the security groups associated with your running instance
 
[root@puma15 neutron(keystone_admin)]# neutron security-group-list 
+--+--+--+
| id   | name | description 
 |
+--+--+--+
| 09600aa9-e220-4a4c-a905-6db9c91d968b | sec_test | will associate to testing 
VM |
| 19dfccd3-2c47-41a7-9227-d0fdc4a7284f | default  | default 
 |
| ef948932-65e8-4939-b485-6c80bd0b7b9c | default  | default 
 |
+--+--+--+
 
[root@puma15 neutron(keystone_admin)]# nova show 
29eeb6ab-55d9-421f-b530-a9a2d5f6dc75 |grep security_group 
| security_groups  | default  
  |
 
2. Create a new security group
$ neutron security-group-create test3 --description "will be associated to a 
testing instance twice"
[root@puma15 neutron(keystone_admin)]# neutron security-group-list 
+--+-++
| id   | name| description  
  |
+--+-++
| 19dfccd3-2c47-41a7-9227-d0fdc4a7284f | default | default  
  |
| ca017993-79f2-4091-88c5-4b48bf09adaa | test3   | will be associated to a 
testing instance twice |
| ef948932-65e8-4939-b485-6c80bd0b7b9c | default | default  
  |
+--+-++


3. Associate the newly-created security group to the running instance
[root@puma15 neutron(keystone_admin)]# nova add-secgroup 
29eeb6ab-55d9-421f-b530-a9a2d5f6dc75 test3
 
4. Try to associate again the same security group to the same instance
[root@puma15 neutron(keystone_admin)]# nova add-secgroup 
29eeb6ab-55d9-421f-b530-a9a2d5f6dc75 test3

Expected error :
ERROR: Security group 16 is already associated with the instance 
29fe826e-7ff2-488f-9452-5b2e9bfda8b8 (HTTP 400) (Request-ID: 
req-7a216931-c7ec-47b6-a784-ac4b57c648b7)

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  no error when adding an already-associated security group to a running
  instance

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I don't get any error message when I try to associate VM to security
  group when it already assigned to this  security group .

  version : 
  [root@puma15 ~(keystone_admin)]# rpm -qa | grep neu
  python-neutron-2014.2.2-2.el7ost.noarch
  openstack-neutron-openvswitch-2014.2.2-2.el7ost.noarch
  openstack-neutron-2014.2.2-2.el7ost.noarch
  openstack-neutron-ml2-2014.2.2-2.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  [root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel 
  libreport-rhel-2.1.11-21.el7.x86_64
   rhos-release-6-rhel-7.1.repo

  1. List the security groups associated with your running instance
   
  [root@puma15 neutron(keystone_admin)]# neutron security-group-list 
  
+--+--+--+
  | id   | name | description   
   |
  
+--+--+--+
  | 09600aa9-e220-4a4c-a905-6db9c91d968b | sec_test | will associate to testing 
VM |
  | 19dfccd3-2c47-41a7-9227-d0fdc4a7284f | default  | default   
   |
  | ef948932-65e8-4939-b485-6c80bd0b7b9c | default  | default   
   |
  
+--+--+--+
   
  [root@puma15 neutron(keystone_admin)]# nova show 
29eeb6ab-55d9-421f-b530-a9a2d5f6dc75 |grep security_group 
  | security_groups  | default  
|
   
  2. Create a new security group
  $ neutron security-group-create test3 --description "will be associated to a 
testing instance twice"
  [root@puma15 neutron(ke

[Yahoo-eng-team] [Bug 1423075] [NEW] LBaaS|cannot assign 2 pools of service to same VIP

[Eran Kuris]

Public bug reported:

Version :
[root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel
libreport-rhel-2.1.11-10.el7.x86_64
[root@puma15 ~]# rpm -qa |grep neutron
openstack-neutron-openvswitch-2014.2.1-6.el7ost.noarch
python-neutronclient-2.3.9-1.el7ost.noarch
openstack-neutron-2014.2.1-6.el7ost.noarch
python-neutron-2014.2.1-6.el7ost.noarch
openstack-neutron-ml2-2014.2.1-6.el7ost.noarch


When I  created 2 pools with 2 different protocol = 1.HTTP & 2. TCP(SSH) 
 I tried to associate it via neutron client (CLI) to same VIP but it not 
 possible. There is no option to create load balancer that make balance between 
2 server for 2 different services.
To Reproduce : 
1.  configure 2 different pools  1 for HTTP  and second to SSH and assign them 
to 1 single VIP .

As its see I need to create Vip per a service .
This behevie is not as I expected LB should be work. we can take for example 
Alteon- Radware LB  or F5 LB .

attached setup description .

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: lbaas neutron-core

** Attachment added: "LB-2services.jpg"
   
https://bugs.launchpad.net/bugs/1423075/+attachment/4321561/+files/LB-2services.jpg

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

Title:
  LBaaS|cannot assign 2 pools of service to same VIP

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Version :
  [root@puma15 ~(keystone_admin)]# rpm -qa | grep rhel
  libreport-rhel-2.1.11-10.el7.x86_64
  [root@puma15 ~]# rpm -qa |grep neutron
  openstack-neutron-openvswitch-2014.2.1-6.el7ost.noarch
  python-neutronclient-2.3.9-1.el7ost.noarch
  openstack-neutron-2014.2.1-6.el7ost.noarch
  python-neutron-2014.2.1-6.el7ost.noarch
  openstack-neutron-ml2-2014.2.1-6.el7ost.noarch

  
  When I  created 2 pools with 2 different protocol = 1.HTTP & 2. TCP(SSH) 
   I tried to associate it via neutron client (CLI) to same VIP but it not 
   possible. There is no option to create load balancer that make balance 
between 2 server for 2 different services.
  To Reproduce : 
  1.  configure 2 different pools  1 for HTTP  and second to SSH and assign 
them to 1 single VIP .

  As its see I need to create Vip per a service .
  This behevie is not as I expected LB should be work. we can take for example 
Alteon- Radware LB  or F5 LB .

  attached setup description .

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1421239] [NEW] LBaaS- overwrite when associate 2 different Vip's to same external IP

[Eran Kuris]

Public bug reported:

I created in LBaaS  2  VIP's .
I  associate one vip (192.168.1.8) to external IP  (10.35.166.4).
When I try to associate the second vip(192.168.1.9) to same external IP 
10.35.166.4  I success but it overwrite the first vip  , there is no warning 
message. 
We should prevent it as we cannot associate VM to external IP that already 
associated to other VM (we get an error message : Conflict (HTTP 409) 
(Request-ID: req-35eeddc9-d264-4fc5-a336-d201e4a66231 ])

**If we not prevent it we should send warning message about it .


How to Reproduce : 
Create in your tenant 2 VM's  with internal network & external network.

1. Create LB pool on subnet of tenant A
>

2. Log into VM1 and VM2, enable httpd


3. Create 2 members into webpool (use VM’s Ips)
 --protocol-port 80 webpool>

4.Create a Healthmonitor and associated it with the webpool



Run:


 webpool

5.Create a VIP for the webpool
 webpool>

6.Check HAproxy created (for example)


7. Create a floating IP from external network


8.Check port id of LB VIP



9.Associate floating IP with the LB VIP
 

10.From external network, try to connect the floating IP by curl 
http://IP>


create for same VM's  VIP  to other service FTP  or SSH  for example  and try 
to associate it to same external floating ip that we used already.

** Affects: neutron
 Importance: Undecided
 Status: New

** Attachment added: "LBaaS floating IP .odt"
   
https://bugs.launchpad.net/bugs/1421239/+attachment/4317992/+files/LBaaS%20floating%20IP%20.odt

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

Title:
  LBaaS- overwrite when associate  2 different Vip's  to same external
  IP

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I created in LBaaS  2  VIP's .
  I  associate one vip (192.168.1.8) to external IP  (10.35.166.4).
  When I try to associate the second vip(192.168.1.9) to same external IP 
10.35.166.4  I success but it overwrite the first vip  , there is no warning 
message. 
  We should prevent it as we cannot associate VM to external IP that already 
associated to other VM (we get an error message : Conflict (HTTP 409) 
(Request-ID: req-35eeddc9-d264-4fc5-a336-d201e4a66231 ])

  **If we not prevent it we should send warning message about it .


  How to Reproduce : 
  Create in your tenant 2 VM's  with internal network & external network.

  1. Create LB pool on subnet of tenant A
  >

  2. Log into VM1 and VM2, enable httpd
  

  3. Create 2 members into webpool (use VM’s Ips)
   --protocol-port 80 webpool>

  4.Create a Healthmonitor and associated it with the webpool

  

  Run:
  

   webpool

  5.Create a VIP for the webpool
   webpool>

  6.Check HAproxy created (for example)
  

  7. Create a floating IP from external network
  

  8.Check port id of LB VIP
  
  

  9.Associate floating IP with the LB VIP
   

  10.From external network, try to connect the floating IP by curl 
  http://IP>

  
  create for same VM's  VIP  to other service FTP  or SSH  for example  and try 
to associate it to same external floating ip that we used already.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1420809] Re: Inconsistent beween Horizon & Glance image-create help

[Eran Kuris]

** Summary changed:

- Glance image-create  help in CLI  is not correct
+ Inconsistent beween Horizon & Glance image-create  help

** Tags added: horizon

** Project changed: glance => horizon

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1420809

Title:
  Inconsistent beween Horizon & Glance image-create  help

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  In Glance CLI help we can see parameter that are written as "optional" when 
they are mandatory.
  I compare it with horizon WebUI dashboard and I saw which fields are 
mandatory .
  to reproduce the bug in CLI run the command : 
  #glance help image-create

  compare it with WebUI

  Version 
  [root@puma15 ~(keystone_eran1)]# rpm -qa |grep glance 
  python-glanceclient-0.14.2-1.el7ost.noarch
  openstack-glance-2014.2.1-3.el7ost.noarch
  python-glance-2014.2.1-3.el7ost.noarch
  python-glance-store-0.1.10-2.el7ost.noarch

  [root@puma15 ~(keystone_eran1)]# rpm -qa |grep rhel
  libreport-rhel-2.1.11-10.el7.x86_64

  
  **Attatched screenshot - describe compare between CLI & WebUI

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1420809] [NEW] Glance image-create help in CLI is not correct

[Eran Kuris]

Public bug reported:

In Glance CLI help we can see parameter that are written as "optional" when 
they are mandatory.
I compare it with horizon WebUI dashboard and I saw which fields are mandatory .
to reproduce the bug in CLI run the command : 
#glance help image-create

compare it with WebUI

Version 
[root@puma15 ~(keystone_eran1)]# rpm -qa |grep glance 
python-glanceclient-0.14.2-1.el7ost.noarch
openstack-glance-2014.2.1-3.el7ost.noarch
python-glance-2014.2.1-3.el7ost.noarch
python-glance-store-0.1.10-2.el7ost.noarch

[root@puma15 ~(keystone_eran1)]# rpm -qa |grep rhel
libreport-rhel-2.1.11-10.el7.x86_64


**Attatched screenshot - describe compare between CLI & WebUI

** Affects: glance
 Importance: Undecided
 Status: New

** Attachment added: "glance_help.jpg"
   
https://bugs.launchpad.net/bugs/1420809/+attachment/4317165/+files/glance_help.jpg

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

Title:
  Glance image-create  help in CLI  is not correct

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  In Glance CLI help we can see parameter that are written as "optional" when 
they are mandatory.
  I compare it with horizon WebUI dashboard and I saw which fields are 
mandatory .
  to reproduce the bug in CLI run the command : 
  #glance help image-create

  compare it with WebUI

  Version 
  [root@puma15 ~(keystone_eran1)]# rpm -qa |grep glance 
  python-glanceclient-0.14.2-1.el7ost.noarch
  openstack-glance-2014.2.1-3.el7ost.noarch
  python-glance-2014.2.1-3.el7ost.noarch
  python-glance-store-0.1.10-2.el7ost.noarch

  [root@puma15 ~(keystone_eran1)]# rpm -qa |grep rhel
  libreport-rhel-2.1.11-10.el7.x86_64

  
  **Attatched screenshot - describe compare between CLI & WebUI

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1419411] [NEW] WishList: add drop-down to filter image & flavor ID

[Eran Kuris]

Public bug reported:

Version : python-django-horizon-2014.2.1-5.el7ost.noarch

Under instances we can filter instances by Image ID / Flavor ID . 
I think we should add option of drop-down with all image ID & flavor ID  
instead  to go images and check the image ID .

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: "filter.png"
   https://bugs.launchpad.net/bugs/1419411/+attachment/4314673/+files/filter.png

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1419411

Title:
  WishList: add drop-down to filter image & flavor ID

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Version : python-django-horizon-2014.2.1-5.el7ost.noarch

  Under instances we can filter instances by Image ID / Flavor ID . 
  I think we should add option of drop-down with all image ID & flavor ID  
instead  to go images and check the image ID .

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418452] [NEW] Unnecessary eye icon In Dashboard Horizon Admin --> change password

[Eran Kuris]

Public bug reported:

When you sign in to dashboard  under : 
Admin --> change password  
you can see near  "Description"   - eye icon which is unnecessary , it should 
be removed . 

Suggestion: add  legend for the blue mark  *  = which means mandatory
field

attached screenshot

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: "eye icon.jpg"
   
https://bugs.launchpad.net/bugs/1418452/+attachment/4313047/+files/eye%20icon.jpg

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1418452

Title:
  Unnecessary eye icon In Dashboard Horizon  Admin --> change password

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When you sign in to dashboard  under : 
  Admin --> change password  
  you can see near  "Description"   - eye icon which is unnecessary , it should 
be removed . 

  Suggestion: add  legend for the blue mark  *  = which means mandatory
  field

  attached screenshot

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1418430] [NEW] Admin-->Setting -->Tool tip of "Item per page" does not include value of max number (1000)

[Eran Kuris]

Public bug reported:

In Dashboard Horizon  go to Admin --> setting 
Then type on tool tip of  "Item per page" 
You can see it does not include value of the max number which is 1000 items per 
page.

attached video

** Affects: horizon
 Importance: Undecided
 Status: New

** Attachment added: "Horizon tool tip.webm"
   
https://bugs.launchpad.net/bugs/1418430/+attachment/4313022/+files/Horizon%20tool%20tip.webm

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1418430

Title:
  Admin-->Setting -->Tool tip of "Item per page" does not include value
  of max number (1000)

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Dashboard Horizon  go to Admin --> setting 
  Then type on tool tip of  "Item per page" 
  You can see it does not include value of the max number which is 1000 items 
per page.

  attached video

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp