from:"Darek Smigiel"

[Yahoo-eng-team] [Bug 1657668] Re: Grammer error in LoadBalancerPluginv2

2017-01-19 Thread Darek Smigiel

*** This bug is a duplicate of bug 1607585 ***
https://bugs.launchpad.net/bugs/1607585

1912294464 you're right. It's a bug, although it's duplicate.

** Project changed: neutron => octavia

** This bug has been marked a duplicate of bug 1607585
   neutron server report error when get loadbalance status

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

Title:
  Grammer error in LoadBalancerPluginv2

Status in octavia:
  New

Bug description:
  Hi
  I use OpenStack Mitaka with Ubuntu 14.04.
  I found a grammar error.

  /usr/lib/python2.7/dist-
  packages/neutron_lbaas/services/loadbalancer/plugin.py   line 1344

  Whether need 'self' when invoke '_set_degraded' function?

  1340 if (pool_status["id"] not in
  1341 [ps["id"] for ps in lb_status["pools"]]):
  1342 lb_status["pools"].append(pool_status)
  1343 if self._is_degraded(curr_listener.default_pool):
  1344 self._set_degraded(self, listener_status, lb_status)
  1345 members = curr_listener.default_pool.members
  1346 for curr_member in members:
  1347 if not curr_member.admin_state_up:

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1657668/+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 1656386] [NEW] Memory leaks on linuxbridge job

2017-01-13 Thread Darek Smigiel

Public bug reported:

Couple examples of recent leakages for linuxbridge job [1], [2]

[1] 
http://logs.openstack.org/73/373973/13/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/295d92f/logs/syslog.txt.gz#_Jan_11_13_56_32
[2] 
http://logs.openstack.org/59/382659/26/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/7de01d0/logs/syslog.txt.gz#_Jan_11_15_54_36

Close to the end of running tests, consumption of swap growths pretty quickly, 
exceeding 2GBs.
I didn't find root cause of that.

** 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/1656386

Title:
  Memory leaks on linuxbridge job

Status in neutron:
  New

Bug description:
  Couple examples of recent leakages for linuxbridge job [1], [2]

  [1] 
http://logs.openstack.org/73/373973/13/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/295d92f/logs/syslog.txt.gz#_Jan_11_13_56_32
  [2] 
http://logs.openstack.org/59/382659/26/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/7de01d0/logs/syslog.txt.gz#_Jan_11_15_54_36

  Close to the end of running tests, consumption of swap growths pretty 
quickly, exceeding 2GBs.
  I didn't find root cause of that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1656386/+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 1650270] Re: Neutron-LBaaS v2: mapping HAproxy process to cpu core

2016-12-15 Thread Darek Smigiel

** Project changed: neutron => octavia

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

Title:
  Neutron-LBaaS v2: mapping HAproxy process to cpu core

Status in octavia:
  New

Bug description:
  HAproxy in default configuration is spawned on one CPU core. This
  could be changed by adding 'nbproc' option which provide possibility
  to chose how many cores should be used by HAproxy and which
  frontend/backend should use more than one core. That kind of
  configuration will provide better performance to load balancer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1650270/+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 1650170] Re: Return error but create successfully when create lbaas pool with a PENDING_UPDATE loadbalancer

2016-12-15 Thread Darek Smigiel

** Project changed: neutron => octavia

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

Title:
  Return error but create successfully when create lbaas pool with a
  PENDING_UPDATE loadbalancer

Status in octavia:
  New

Bug description:
  In my newest devstack encironment with lbaas v2, when I create a lbaas
  pool with a PENDING_UPDATE state loadbalancer , the server return
  error with "Invalid state PENDING_UPDATE of loadbalancer resource
  422c211a-ca32-4def-9681-a80f37375191", but when I do "neutron lbaas-
  pool-list", the failed pool is shown on the screen.


  Before creating:
  [stack@devstack ~]$ neutron lbaas-loadbalancer-list
  
+-++-+-+--+
  | id  | name   | vip_address | provisioning_status | 
provider |
  
+-++-+-+--+
  | 422c211a-   | test-0 | 10.0.0.7| PENDING_UPDATE  | 
haproxy  |
  | ca32-4def-9681-a80f37375191 || | |  
|
  
+-++-+-+--+
  [stack@devstack ~]$ neutron lbaas-pool-list 
  +--++--++
  | id   | name   | protocol | admin_state_up |
  +--++--++
  | 77e03124-4ac3-474c-a52d-5c9c74073e2b | test-1 | TCP  | True   |
  | 898152e0-938e-43a0-83f3-2b93b0b60883 | test-2 | TCP  | True   |
  | 8ff3ed37-b56d-4524-a416-fdba697003ea | test-3 | TCP  | True   |
  +--++--++

  Creating pool:

  [stack@devstack ~]$ neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN 
--protocol TCP --loadb
  alancer test-0 --name test-4
  Invalid state PENDING_UPDATE of loadbalancer resource 
422c211a-ca32-4def-9681-a80f37375191
  Neutron server returns request_ids: 
['req-47f3d03f-b51e-427e-9a9a-38ddbdd581a5']

  After creating:

  [stack@devstack ~]$ neutron lbaas-pool-list   
 
  +--++--++
  | id   | name   | protocol | admin_state_up |
  +--++--++
  | 77e03124-4ac3-474c-a52d-5c9c74073e2b | test-1 | TCP  | True   |
  | 898152e0-938e-43a0-83f3-2b93b0b60883 | test-2 | TCP  | True   |
  | 8ff3ed37-b56d-4524-a416-fdba697003ea | test-3 | TCP  | True   |
  | ffa0acec-9b53-4931-8a52-0c6d10d87f1f | test-4 | TCP  | True   |
  +--++--++

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1650170/+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 1577541] Re: Neutron-LBaaS v2: TLS Listeners Functional Tests

2016-12-13 Thread Darek Smigiel

** Project changed: neutron => octavia

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

Title:
   Neutron-LBaaS v2: TLS Listeners Functional Tests

Status in octavia:
  In Progress

Bug description:
  Create the following tests:

  * A battery of CRUD tests around TLS listeners
  * Dependent on Barbican to generate default_tls_container_ref

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1577541/+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 1646770] Re: lbaas tempest test cases are not executing

2016-12-13 Thread Darek Smigiel

** Project changed: neutron => octavia

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

Title:
  lbaas tempest test cases are not executing

Status in octavia:
  In Progress

Bug description:
  Hitting the error 'TestListenerBasic' object has no attribute
  'tenant_id while executing test_listener_basic.py. Need to make
  changes in base.py file to run the test files successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1646770/+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 1627044] Re: Last chance call to neutron if VIF plugin notification is lost

2016-12-13 Thread Darek Smigiel

** No longer affects: neutron

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

Title:
  Last chance call to neutron if VIF plugin notification is lost

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  While spawning a new VM, Nova waits for event from Neutron that its
  port is configured. In some cases Neutron event is lost (e.g. RabbitMQ
  issue) and if vif_plugging_is_fatal=True (it is by default) the
  instance is set to ERROR state. It happens even if in fact port is
  ACTIVE on Neutron side and all should work fine.

  This workflow could be improved by calling Neutron before failing.
  Nova could check real state of each port in Neutron just before setting the 
instance in ERROR (if at least one port is not ACTIVE).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1627044/+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 1642167] Re: Move neutron.common.utils.wait_until_true to neutron-lib

2016-12-13 Thread Darek Smigiel

** Changed in: neutron
   Status: In Progress => 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/1642167

Title:
  Move neutron.common.utils.wait_until_true to neutron-lib

Status in neutron:
  Invalid

Bug description:
  In an effort to move from neutron.common to neutron-lib,
  wait_until_true should be moved from neutron.common.util to neutron-
  lib.

  Seen in: Ocata

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642167/+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 1641813] Re: stable/newton branch creation request for networking-odl

2016-12-13 Thread Darek Smigiel

Branch got created.

** Changed in: neutron
   Status: New => Fix Released

** Changed in: networking-odl
   Status: New => Fix Released

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

Title:
  stable/newton branch creation request for networking-odl

Status in networking-odl:
  Fix Released
Status in neutron:
  Fix Released

Bug description:
  Please create stable/newton branch of networking-odl on
  f313b7f5b3ebba5bd6f7e8e855315e1570c71f54

  the corresponding patch for openstack/release can be found at
  https://review.openstack.org/#/c/395415/

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-odl/+bug/1641813/+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 1637972] Re: VPNaaS: report_state fails by key error 'tenant_id'

2016-11-07 Thread Darek Smigiel

I'm not able to reproduce this issue on master branch.
For VPNaaS I've used this description [1]. To verify correctness of VPN, I've 
run script [2], which is included in config site. There is a small error in 
third line. WEST_SUBNET should be in newline. 

[1] https://wiki.openstack.org/wiki/Neutron/VPNaaS/HowToInstall
[2] http://paste.openstack.org/raw/44702/

Hiroyuki, could you retry this and verify if you still see this error?

** 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/1637972

Title:
  VPNaaS: report_state fails by key error 'tenant_id'

Status in neutron:
  Invalid

Bug description:
  When creating ipsec-site-connection, the error KeyError: 'tenant_id'
  occurred in vpn agent.

  
  Operation:

  $ neutron ipsec-site-connection-create --peer-cidr 192.168.91.0/24 --peer-id 
192.168.7.4 --peer-address 192.168.7.4 --psk ps --vpnservice-id service1 
--ikepolicy-id ike1 --ipsecpolicy-id ipsec1 --name test1 --dpd action=disabled
  Created a new ipsec_site_connection:
  +---++
  | Field | Value  |
  +---++
  | admin_state_up| True   |
  | auth_mode | psk|
  | description   ||
  | dpd   | {"action": "disabled", "interval": 30, "timeout": 120} |
  | id| 298a689b-428b-45fd-a868-2d4738d59eb1   |
  | ikepolicy_id  | be1f92ab-8064-4328-8862-777ae6878691   |
  | initiator | bi-directional |
  | ipsecpolicy_id| 09c67ae8-6ede-47ca-a15b-c52be1d7feaf   |
  | local_ep_group_id ||
  | local_id  ||
  | mtu   | 1500   |
  | name  | test1  |
  | peer_address  | 192.168.7.4|
  | peer_cidrs| 192.168.91.0/24|
  | peer_ep_group_id  ||
  | peer_id   | 192.168.7.4|
  | project_id| 068a47c758ae4b5d9fab059539e57740   |
  | psk   | ps |
  | route_mode| static |
  | status| PENDING_CREATE |
  | tenant_id | 068a47c758ae4b5d9fab059539e57740   |
  | vpnservice_id | 4f82612c-5e3a-4699-aafa-bdfa5ede31fe   |
  +---++

  Error log in vpn agent:

  2016-10-31 19:24:15.591 ERROR oslo_messaging.rpc.server 
[req-169503b5-edbc-46a9-8ded-03b5b5d278ea demo 
068a47c758ae4b5d9fab059539e57740] Exception during message handling
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server Traceback (most 
recent call last):
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
155, in _process_incoming
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server res = 
self.dispatcher.dispatch(message)
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
225, in dispatch
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server return 
self._do_dispatch(endpoint, method, ctxt, args)
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
195, in _do_dispatch
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server result = 
func(ctxt, **new_args)
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File 
"/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py",
 line 884, in vpnservice_updated
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server 
self.sync(context, [router] if router else [])
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 
271, in inner
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server return f(*args, 
**kwargs)
  2016-10-31 19:24:15.591 TRACE oslo_messaging.rpc.server   File

[Yahoo-eng-team] [Bug 1632633] Re: fix some word spelling error

2016-10-13 Thread Darek Smigiel

** Changed in: neutron
   Status: In Progress => 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/1632633

Title:
  fix some word spelling error

Status in neutron:
  Fix Committed

Bug description:
  there are some word spelling error in .py file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1632633/+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 1632633] Re: fix some word spelling error

2016-10-12 Thread Darek Smigiel

It's not even a bug. If there are any spelling errors, they can be fixed
without submitting a bug report.

** Changed in: neutron
   Status: Incomplete => 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/1632633

Title:
  fix some word spelling error

Status in neutron:
  Invalid

Bug description:
  there are some word spelling error in .py file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1632633/+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 1630134] Re: Networking API v2.0 (CURRENT): Update Network Request missing the 'qos-policy-id' parameter.

2016-10-04 Thread Darek Smigiel

** Tags added: doc

** Also affects: openstack-api-site
   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/1630134

Title:
  Networking API v2.0 (CURRENT): Update Network Request missing the
  'qos-policy-id' parameter.

Status in neutron:
  New
Status in openstack-api-site:
  New

Bug description:
  The API reference http://developer.openstack.org/api-
  ref/networking/v2/index.html doesn't reflect the fact a Qos Policy
  linked to an existing network can be updated:

  
  $ curl -s -H "X-Auth-Token: $OS_TOKEN" 
http://${OS_HOST}:9696/v2.0/qos/policies | python -mjson.tool{
  "policies": [
  {
  "description": "This policy limits the ports to 10Mbit max.",
  "id": "c4e80891-5d77-480f-8970-a7223fd72f4b",
  "name": "10Mbit",
  "rules": [],
  "shared": false,
  "tenant_id": "5a23535b5dda4770bccc856d0167e53f"
  }
  ]
  }

  $ curl -s  -H "X-Auth-Token: $OS_TOKEN"  -H "Content-Type: application/json" 
http://${OS_HOST}:9696/v2.0/networks/b18d3079-fcaa-41b7-8aec-0d009789fff8| 
python -mjson.tool
  {
  "network": {
  "admin_state_up": false,
  "id": "b18d3079-fcaa-41b7-8aec-0d009789fff8",
  "mtu": 0,
  "name": "cristalnet",
  "port_security_enabled": true,
  "provider:network_type": "vxlan",
  "provider:physical_network": null,
  "provider:segmentation_id": 39,
  "qos_policy_id": null,
  "router:external": false,
  "shared": true,
  "status": "ACTIVE",
  "subnets": [],
  "tenant_id": "5a23535b5dda4770bccc856d0167e53f",
  "vlan_transparent": null
  }
  }

  $ curl -s \
  >   -X PUT \
  >   -H "X-Auth-Token: $OS_TOKEN" \
  >   -H "Content-Type: application/json" \
  >   -d '{"network": { "qos_policy_id": "c4e80891-5d77-480f-8970-a7223fd72f4b" 
 } }' \
  > http://${OS_HOST}:9696/v2.0/networks/b18d3079-fcaa-41b7-8aec-0d009789fff8 | 
python -mjson.tool
  {
  "network": {
  "admin_state_up": false,
  "id": "b18d3079-fcaa-41b7-8aec-0d009789fff8",
  "mtu": 0,
  "name": "cristalnet",
  "port_security_enabled": true,
  "provider:network_type": "vxlan",
  "provider:physical_network": null,
  "provider:segmentation_id": 39,
  "qos_policy_id": "c4e80891-5d77-480f-8970-a7223fd72f4b",
  "router:external": false,
  "shared": true,
  "status": "ACTIVE",
  "subnets": [],
  "tenant_id": "5a23535b5dda4770bccc856d0167e53f",
  "vlan_transparent": null
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1630134/+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 1624103] Re: Neutron accepting multiple networks/subnets to be created with same name, network address

2016-09-15 Thread Darek Smigiel

It's not a bug.

** 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/1624103

Title:
  Neutron accepting multiple networks/subnets to be created with same
  name, network address

Status in neutron:
  Invalid

Bug description:
  Description:
  
  I am able to create multiple networks/subnets with the same name and network 
address. This behaviour can result in confusion.

  Expected Behaviour:
  --
  Enforcing uniqueness in network/subnet names

  Environment:
  ---
  OpenStack Mitaka on Ubuntu 14.04 server

  Reproduction Steps:
  ---

  Steps from horizon:
  1. Create multiple networks/subnets with same name and same addresses

  Result:
  ---
  neutron net-list
  
+--++---+
  | id   | name   | subnets 
  |
  
+--++---+
  | e7d3c477-4c37-4871-af51-0567b3d4a03b | intnet | 
f9ef42c7-f190-4f6b-b7a3-eb85d55c8c1a 2.2.2.0/24   |
  | 182434dc-0c5b-4ba9-9dee-dfefbdf81d23 | intnet | 
0d2e21a1-df8a-4d0a-a11d-9b0646a158e3 2.2.2.0/24   |
  | 258095ac-e04d-485e-9e83-956499208da9 | intnet | 
dfc87017-06dd-4449-a898-9a3c30eb1d81 2.2.2.0/24   |
  | 134aa0b6-dc03-4b82-9e17-150ec5aa5471 | extnet | 
f25d0a78-033c-4434-9b5d-5779dd72b8f4 10.10.0.0/16 |
  
+--++---+

  neutron subnet-list
  
+--++--++
  | id   | name   | cidr | 
allocation_pools   |
  
+--++--++
  | f9ef42c7-f190-4f6b-b7a3-eb85d55c8c1a | intsub | 2.2.2.0/24   | {"start": 
"2.2.2.2", "end": "2.2.2.254"}   |
  | 0d2e21a1-df8a-4d0a-a11d-9b0646a158e3 | intsub | 2.2.2.0/24   | {"start": 
"2.2.2.2", "end": "2.2.2.254"}   |
  | dfc87017-06dd-4449-a898-9a3c30eb1d81 || 2.2.2.0/24   | {"start": 
"2.2.2.2", "end": "2.2.2.254"}   |
  | f25d0a78-033c-4434-9b5d-5779dd72b8f4 | extsub | 10.10.0.0/16 | {"start": 
"10.10.70.30", "end": "10.10.70.40"} |
  
+--++--++

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1624103/+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 1620835] Re: Add timestamp fields for neutron ext resources

2016-09-07 Thread Darek Smigiel

** Also affects: openstack-manuals
   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/1620835

Title:
  Add timestamp fields for neutron ext resources

Status in neutron:
  New
Status in openstack-manuals:
  New

Bug description:
  https://review.openstack.org/312873
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 17b88cd4539cd5fa096115b76fd4a21036395360
  Author: ZhaoBo 
  Date:   Thu May 5 17:16:23 2016 +0800

  Add timestamp fields for neutron ext resources
  
  Propose a new extension named "timestamp_ext" to add timestamp to
  neutron ext resources like 
router/floatingip/security_group/security_group_rule.
  
  APIImpact
  DocImpact: Neutron ext resources now contain 'timestamp' fields like
 'created_at' and 'updated_at'
  Implements: blueprint add-neutron-extension-resource-timestamp
  
  Change-Id: I78b00516e31ce83376d37f57299b2229b6fb8fcf

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1620835/+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 1618691] Re: LBaaS v2 and Keystone v3 in Devstack

2016-08-31 Thread Darek Smigiel

** Project changed: neutron => octavia

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

Title:
  LBaaS v2 and Keystone v3 in Devstack

Status in octavia:
  New

Bug description:
  I had some issues bringing up a devstack environment with LBaaS v2
  (Octavia) and Keystone v3.

  I was able to get it working with the following post-config settings:

  [[post-config|$OCTAVIA_CONF]]
  [keystone_authtoken]
  auth_uri = http://localhost:5000/v3
  auth_url = http://localhost:35357/v3
  user_domain_id = default
  project_name = default
  auth_type = password
  [keystone_authtoken_v3]
  admin_user_domain = default
  admin_project_domain = default

  [[post-config|$NEUTRON_CONF]]
  [service_auth]
  auth_version = 3
  auth_uri = http://localhost:5000/v3
  auth_url = http://localhost:35357/v3
  admin_user_domain = default
  admin_project_domain = default

  [[post-config|$NEUTRON_LBAAS_CONF]]
  [service_auth]
  auth_version = 3
  auth_uri = http://localhost:5000/v3
  auth_url = http://localhost:35357/v3
  admin_user_domain = default
  admin_project_domain = default

  
  I'm not exactly sure how to configure the underlying devstack plugins to 
account for these changes, though.

  For reference, here's the entire local.conf:
  https://gist.github.com/jtopjian/60cfd903260b88d9101b07c43b30532e

To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1618691/+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 1616745] Re: IP allocation with Service Subnets

2016-08-25 Thread Darek Smigiel

** Also affects: neutron
   Importance: Undecided
   Status: New

** 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/1616745

Title:
  IP allocation with Service Subnets

Status in neutron:
  Invalid
Status in openstack-manuals:
  In Progress

Bug description:
  https://review.openstack.org/350613
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit de3a3cda740dfa22152c8224c39aeb9e51642d93
  Author: John Davidge 
  Date:   Mon Aug 1 14:04:08 2016 +0100

  IP allocation with Service Subnets
  
  This changes the way that IPAM decides which subnets to use when
  assigning IPs to newly created ports. If the port has a defined
  device_owner, this is used to filter available subnets to choose
  from only those with a matching service_type or no service_type
  at all.
  
  If the given network has no service subnets, then the existing
  behaviour is used.
  
  A new IPAM exception is introduced to handle the following scenarios:
  1. A port is created with a device_owner and only non-matching service
 subnets exist.
  2. A port is created without a device owner, and no subnets exist
 without a service_type.
  
  With this patch, service subnets are now usable.
  
  Implements: blueprint service-subnets
  APIImpact: subnet-create and subnet-update with service_types
  DocImpact: IPs assigned to new ports will now come from a service subnet
  matching the port device_owner, if one exists.
  
  Closes-Bug: 1544768
  Change-Id: If3dd94a46bdee24c13d1f17c4f2e69af0cb8af63

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616745/+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 1595574] Re: VXLan fails to be created between dhcp and compute node

2016-07-07 Thread Darek Smigiel

Bug is invalid. Reassigning back to kolla, to look at this issue.

** Also affects: kolla
   Importance: Undecided
   Status: New

** Changed in: neutron
   Status: In Progress => 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/1595574

Title:
  VXLan fails to be created between dhcp and compute node

Status in kolla:
  New
Status in neutron:
  Invalid

Bug description:
  I have strange issue. VXLan fails to connect dhcp agent and compute
  node. VXLan compute-compute builds successfully. No log ERROR or even
  WARNING.

  compute node:

   Bridge br-tun
  fail_mode: secure
  Port br-tun
  Interface br-tun
  type: internal
  Port "vxlan-c0a86424"
  Interface "vxlan-c0a86424"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.29", out_key=flow, remote_ip="192.168.100.36"}
  Port patch-int
  Interface patch-int
  type: patch
  options: {peer=patch-tun}

  DHCP agent node:
  Bridge br-tun
  fail_mode: secure
  Port patch-int
  Interface patch-int
  type: patch
  options: {peer=patch-tun}
  Port "vxlan-c0a8641d"
  Interface "vxlan-c0a8641d"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.29"}
  Port "vxlan-c0a86424"
  Interface "vxlan-c0a86424"
  type: vxlan
  options: {df_default="true", in_key=flow, 
local_ip="192.168.100.31", out_key=flow, remote_ip="192.168.100.36"}
  Port br-tun
  Interface br-tun
  type: internal

  
  I have 2 vms, at compute .36 and .29. As you can see, compute doesn't have 
tunnel exit from dhcp agent node.
  This was deployed by latest master kolla, which translates to latest master 
neutron.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1595574/+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 1597168] Re: There's no way to update '--shared' argument of qos-policy to False by using qos-policy-update command.

2016-06-30 Thread Darek Smigiel

*** This bug is a duplicate of bug 1590942 ***
https://bugs.launchpad.net/bugs/1590942

Xiewj you were right. It is a duplicate. Maybe it's worth to backport
this change to neutron.

** This bug has been marked a duplicate of bug 1590942
   Missing option to set qos-policy as not shared during upgrade

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

Title:
  There's no way to update '--shared' argument of qos-policy to False by
  using qos-policy-update command.

Status in neutron:
  New

Bug description:
  In Mitaka,
  There's no way to update '--shared' argument of qos-policy to False by using 
qos-policy-update command.
  Actually,we may need to update --shared to False in qos-policy-update command,
  Such as in the qos-policy rbac scenario, we may need to change the rbac 
policy  
  by updating ‘--shared’ parameters to False,so that we can cancel sharing the 
qos-policy to all tenants

  [root@localhost devstack]# neutron qos-policy-create qos-policy-01
  Created a new policy:
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | id  | 53e278d6-ad97-4875-9eb3-374e46d5fe9c |
  | name| qos-policy-01|
  | rules   |  |
  | shared  | False|
  | tenant_id   | aced7a29bb134dec82307a880d1cc542 |
  +-+--+
  [root@localhost devstack]# neutron qos-policy-update qos-policy-01 --shared   
  
  Updated policy: qos-policy-01
  [root@localhost devstack]# neutron qos-policy-show qos-policy-01
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | id  | 53e278d6-ad97-4875-9eb3-374e46d5fe9c |
  | name| qos-policy-01|
  | rules   |  |
  | shared  | True |
  | tenant_id   | aced7a29bb134dec82307a880d1cc542 |
  +-+--+
  [root@localhost devstack]# neutron qos-policy-update qos-policy-01 
--shared=False
  usage: neutron qos-policy-update [-h] [--request-format {json}] [--name NAME]
   [--description DESCRIPTION] [--shared]
   POLICY
  neutron qos-policy-update: error: argument --shared: ignored explicit 
argument u'False'
  Try 'neutron help qos-policy-update' for more information.
  [root@localhost devstack]# 

  [root@localhost devstack]# neutron help qos-policy-update
  usage: neutron qos-policy-update [-h] [--request-format {json}] [--name NAME]
   [--description DESCRIPTION] [--shared]
   POLICY

  Update a given qos policy.

  positional arguments:
POLICYID or name of policy to update.

  optional arguments:
-h, --helpshow this help message and exit
--request-format {json}
  DEPRECATED! Only JSON request format is supported.
--name NAME   Name of QoS policy.
--description DESCRIPTION
  Description of the QoS policy.
--shared  Accessible by other tenants. Set shared to True
  (default is False).
  [root@localhost devstack]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1597168/+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 1597168] Re: There's no way to update '--shared' argument of qos-policy to False by using qos-policy-update command.

2016-06-29 Thread Darek Smigiel

Lack of '--shared' parameter means that qos-policy won't be shared.

** 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/1597168

Title:
  There's no way to update '--shared' argument of qos-policy to False by
  using qos-policy-update command.

Status in neutron:
  Invalid

Bug description:
  In Mitaka,
  There's no way to update '--shared' argument of qos-policy to False by using 
qos-policy-update command.
  Actually,we may need to update --shared to False in qos-policy-update command,
  Such as in the qos-policy rbac scenario, we may need to change the rbac 
policy  
  by updating ‘--shared’ parameters to False,so that we can cancel sharing the 
qos-policy to all tenants

  [root@localhost devstack]# neutron qos-policy-create qos-policy-01
  Created a new policy:
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | id  | 53e278d6-ad97-4875-9eb3-374e46d5fe9c |
  | name| qos-policy-01|
  | rules   |  |
  | shared  | False|
  | tenant_id   | aced7a29bb134dec82307a880d1cc542 |
  +-+--+
  [root@localhost devstack]# neutron qos-policy-update qos-policy-01 --shared   
  
  Updated policy: qos-policy-01
  [root@localhost devstack]# neutron qos-policy-show qos-policy-01
  +-+--+
  | Field   | Value|
  +-+--+
  | description |  |
  | id  | 53e278d6-ad97-4875-9eb3-374e46d5fe9c |
  | name| qos-policy-01|
  | rules   |  |
  | shared  | True |
  | tenant_id   | aced7a29bb134dec82307a880d1cc542 |
  +-+--+
  [root@localhost devstack]# neutron qos-policy-update qos-policy-01 
--shared=False
  usage: neutron qos-policy-update [-h] [--request-format {json}] [--name NAME]
   [--description DESCRIPTION] [--shared]
   POLICY
  neutron qos-policy-update: error: argument --shared: ignored explicit 
argument u'False'
  Try 'neutron help qos-policy-update' for more information.
  [root@localhost devstack]# 

  [root@localhost devstack]# neutron help qos-policy-update
  usage: neutron qos-policy-update [-h] [--request-format {json}] [--name NAME]
   [--description DESCRIPTION] [--shared]
   POLICY

  Update a given qos policy.

  positional arguments:
POLICYID or name of policy to update.

  optional arguments:
-h, --helpshow this help message and exit
--request-format {json}
  DEPRECATED! Only JSON request format is supported.
--name NAME   Name of QoS policy.
--description DESCRIPTION
  Description of the QoS policy.
--shared  Accessible by other tenants. Set shared to True
  (default is False).
  [root@localhost devstack]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1597168/+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 1594405] Re: test_secure_client fails

2016-06-20 Thread Darek Smigiel

*** This bug is a duplicate of bug 1593647 ***
https://bugs.launchpad.net/bugs/1593647

** This bug has been marked a duplicate of bug 1593647
   TestDesignateClient.test_secure_client fails with  AssertionError: Expected 
call: mock(verify='...')

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

Title:
  test_secure_client fails

Status in neutron:
  New

Bug description:
  This test is failing in ubuntu package builds.  It was added via:
  https://review.openstack.org/#/c/330817/

  ==
  Failed 1 tests - output below:
  ==

  
neutron.tests.unit.plugins.ml2.extensions.test_dns_integration.TestDesignateClient.test_secure_client
  
-

  Captured traceback:
  ~~~
  Traceback (most recent call last):
File 
"/��PKGBUILDDIR��/neutron/tests/unit/plugins/ml2/extensions/test_dns_integration.py",
 line 522, in test_secure_client
  driver.session.Session.assert_called_with(verify=self.TEST_CA_CERT)
File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 925, in 
assert_called_with
  raise AssertionError('Expected call: %s\nNot called' % (expected,))
  AssertionError: Expected call: 
mock(verify='8e8f09ecf81e4e898a41a2153e7b6a0d')
  Not called

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1594405/+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 1593967] Re: neutron command need filtering

2016-06-18 Thread Darek Smigiel

Transition to OSC is in progress: http://docs.openstack.org/developer
/python-neutronclient/devref/transition_to_osc.html

** 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/1593967

Title:
  neutron command need filtering

Status in neutron:
  Invalid

Bug description:
  When existing many neutron ports, it will cost much time to list port. We 
need filtering this ports by host_id/device_owner/security_groups and so on.
  Now when using nova command it could filtering name/host and many more. 
Neutron lack this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1593967/+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 1593436] Re: Fix designate dns driver for SSL based endpoints

2016-06-16 Thread Darek Smigiel

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** 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/1593436

Title:
  Fix designate dns driver for SSL based endpoints

Status in neutron:
  Invalid
Status in openstack-manuals:
  New

Bug description:
  https://review.openstack.org/326958
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 9cd95366a035b29001ce75515d291cf72d07d0c3
  Author: imran malik 
  Date:   Wed Jun 8 02:45:32 2016 -0700

  Fix designate dns driver for SSL based endpoints
  
  Allow setting options in designate section to specify if want
  to skip SSL cert check. This makes it possible to work with HTTPS
  based endpoints, the default behavior of keystoneclient is to always
  set verify=True however in current code, one cannot either provide
  a valid CA cert or skip the verification.
  
  DocImpact: Introduce two additional options for `[designate]` section
  in neutron.conf
  CONF.designate.insecure to allow insecure connections over SSL.
  CONF.designate.ca_cert for a valid cert when connecting over SSL
  
  Change-Id: Ic371cc11d783618c38ee40a18206b0c2a197bb3e
  Closes-Bug: #1588067

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1593436/+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 1592594] Re: DHCP: delete config option dnsmasq_dns_server

2016-06-15 Thread Darek Smigiel

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

** 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/1592594

Title:
  DHCP: delete config option dnsmasq_dns_server

Status in neutron:
  Invalid
Status in openstack-manuals:
  Invalid

Bug description:
  https://review.openstack.org/329306
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit eb965f99ded8a46db220d540bcaea5d67f5b2d08
  Author: Gary Kotton 
  Date:   Tue Jun 14 00:47:14 2016 -0700

  DHCP: delete config option dnsmasq_dns_server
  
  This field was marked as deprecated In commit
  a269541c603f8923b35b7e722f1b8c0ebd42c95a. That was in Kilo
  which has provided enough time for admins to addjust to this.
  
  In addition to this the patch sets the default value as [].
  If a value is not specified this is None and that should not be
  the default list.
  
  DocImpact
  UpgradeImpact
  
  Change-Id: Ieaf18ffc9baf7e1caebe9de47017338bebd92c84

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592594/+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 1592564] [NEW] gate-neutron-lbaasv2-dsvm-minimal is failing

2016-06-14 Thread Darek Smigiel

Public bug reported:

https://review.openstack.org/#/c/329481/
https://review.openstack.org/#/c/219215/

2016-06-14 17:05:38.571 | 2016-06-14 17:05:38.528 | + 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/post_test_hook.sh 
tempest lbaasv2 minimal
2016-06-14 17:05:38.573 | 2016-06-14 17:05:38.530 | + 
NEUTRON_LBAAS_DIR=/opt/stack/new/neutron-lbaas
2016-06-14 17:05:38.587 | 2016-06-14 17:05:38.532 | + 
TEMPEST_CONFIG_DIR=/opt/stack/new/tempest/etc
2016-06-14 17:05:38.587 | 2016-06-14 17:05:38.534 | + 
SCRIPTS_DIR=/usr/os-testr-env/bin
2016-06-14 17:05:38.588 | 2016-06-14 17:05:38.535 | + 
OCTAVIA_DIR=/opt/stack/new/octavia
2016-06-14 17:05:38.588 | 2016-06-14 17:05:38.539 | ++ dirname 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/post_test_hook.sh
2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.541 | + . 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/decode_args.sh
2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.543 | ++ lbaasversion=tempest
2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.544 | ++ lbaastest=lbaasv2
2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.546 | +++ echo lbaasv2
2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.548 | +++ perl -ne 
'/^(.*)-([^-]+)$/ && print "$1";'
2016-06-14 17:05:38.590 | 2016-06-14 17:05:38.550 | ++ lbaasenv=
2016-06-14 17:05:38.590 | 2016-06-14 17:05:38.552 | ++ '[' -z '' ']'
2016-06-14 17:05:38.590 | 2016-06-14 17:05:38.554 | ++ lbaasenv=lbaasv2
2016-06-14 17:05:38.590 | 2016-06-14 17:05:38.556 | +++ echo lbaasv2
2016-06-14 17:05:38.601 | 2016-06-14 17:05:38.557 | +++ perl -ne 
'/^(.*)-([^-]+)$/ && print "$2";'
2016-06-14 17:05:38.601 | 2016-06-14 17:05:38.559 | ++ lbaasdriver=
2016-06-14 17:05:38.602 | 2016-06-14 17:05:38.561 | ++ '[' -z '' ']'
2016-06-14 17:05:38.602 | 2016-06-14 17:05:38.563 | ++ lbaasdriver=octavia
2016-06-14 17:05:38.602 | 2016-06-14 17:05:38.564 | + LBAAS_VERSION=tempest
2016-06-14 17:05:38.603 | 2016-06-14 17:05:38.566 | + LBAAS_TEST=lbaasv2
2016-06-14 17:05:38.603 | 2016-06-14 17:05:38.568 | + LBAAS_DRIVER=octavia
2016-06-14 17:05:38.603 | 2016-06-14 17:05:38.569 | + '[' tempest = lbaasv1 ']'
2016-06-14 17:05:38.604 | 2016-06-14 17:05:38.571 | + testenv=apiv2
2016-06-14 17:05:38.606 | 2016-06-14 17:05:38.573 | + case "$LBAAS_TEST" in
2016-06-14 17:05:38.609 | 2016-06-14 17:05:38.575 | + testenv=lbaasv2
2016-06-14 17:05:38.611 | 2016-06-14 17:05:38.578 | + owner=tempest
2016-06-14 17:05:38.613 | 2016-06-14 17:05:38.581 | + cd 
/opt/stack/new/neutron-lbaas
2016-06-14 17:05:38.634 | 2016-06-14 17:05:38.583 | + sudo chown -R 
tempest:stack /opt/stack/new/neutron-lbaas
2016-06-14 17:05:38.634 | 2016-06-14 17:05:38.585 | + '[' octavia = octavia ']'
2016-06-14 17:05:38.634 | 2016-06-14 17:05:38.588 | + sudo chown -R 
tempest:stack /opt/stack/new/octavia
2016-06-14 17:05:38.634 | 2016-06-14 17:05:38.590 | + sudo_env=' 
OS_TESTR_CONCURRENCY=1'
2016-06-14 17:05:38.635 | 2016-06-14 17:05:38.591 | + sudo_env+=' 
TEMPEST_CONFIG_DIR=/opt/stack/new/tempest/etc'
2016-06-14 17:05:38.635 | 2016-06-14 17:05:38.594 | + '[' lbaasv2 = apiv2 ']'
2016-06-14 17:05:38.635 | 2016-06-14 17:05:38.596 | + '[' lbaasv2 = apiv1 ']'
2016-06-14 17:05:38.635 | 2016-06-14 17:05:38.598 | + '[' lbaasv2 = scenario ']'
2016-06-14 17:05:38.635 | 2016-06-14 17:05:38.600 | + echo 'ERROR: unsupported 
testenv: lbaasv2'
2016-06-14 17:05:38.636 | 2016-06-14 17:05:38.602 | ERROR: unsupported testenv: 
lbaasv2
2016-06-14 17:05:38.637 | 2016-06-14 17:05:38.604 | + exit 1
2016-06-14 17:05:38.637 | + return 1

** Affects: neutron
 Importance: Critical
 Assignee: Elena Ezhova (eezhova)
 Status: Confirmed

** Changed in: neutron
   Importance: Undecided => Critical

** Changed in: neutron
 Assignee: (unassigned) => Elena Ezhova (eezhova)

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

Title:
  gate-neutron-lbaasv2-dsvm-minimal is failing

Status in neutron:
  Confirmed

Bug description:
  https://review.openstack.org/#/c/329481/
  https://review.openstack.org/#/c/219215/

  2016-06-14 17:05:38.571 | 2016-06-14 17:05:38.528 | + 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/post_test_hook.sh 
tempest lbaasv2 minimal
  2016-06-14 17:05:38.573 | 2016-06-14 17:05:38.530 | + 
NEUTRON_LBAAS_DIR=/opt/stack/new/neutron-lbaas
  2016-06-14 17:05:38.587 | 2016-06-14 17:05:38.532 | + 
TEMPEST_CONFIG_DIR=/opt/stack/new/tempest/etc
  2016-06-14 17:05:38.587 | 2016-06-14 17:05:38.534 | + 
SCRIPTS_DIR=/usr/os-testr-env/bin
  2016-06-14 17:05:38.588 | 2016-06-14 17:05:38.535 | + 
OCTAVIA_DIR=/opt/stack/new/octavia
  2016-06-14 17:05:38.588 | 2016-06-14 17:05:38.539 | ++ dirname 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/post_test_hook.sh
  2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.541 | + . 
/opt/stack/new/neutron-lbaas/neutron_lbaas/tests/contrib/decode_args.sh
  2016-06-14 17:05:38.589 | 2016-06-14 17:05:38.543 | ++

[Yahoo-eng-team] [Bug 1526964] Re: Can delete lbaas-pool with lbaas-hm attached

2016-06-10 Thread Darek Smigiel

*** This bug is a duplicate of bug 1571097 ***
https://bugs.launchpad.net/bugs/1571097

** This bug is no longer a duplicate of bug 1450375
   cannot delete v2 healthmonitor if the hm-associated-pool was deleted first
** This bug has been marked a duplicate of bug 1571097
   unable to delete lbaasv2 health monitor if its listener deleted

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

Title:
  Can delete lbaas-pool with lbaas-hm attached

Status in neutron:
  Confirmed

Bug description:
  Using the lbaas v2 resources, I created a loadbalancer, listener,
  pool, and healthmonitor, all attached to each other as expected. Next
  I deleted the pool, which I wouldn't expect to work since there is a
  healthmonitor attached to it, yet it worked successfully. Now I am
  unable to do anything with the healthmonitor that is remaining.

  I tried deleting the healthmonitor, only to get this error:
  $ neutron lbaas-healthmonitor-delete d7257837-7b76-4f70-836d-97dbfa7d5a4a
  Request Failed: internal server error while processing your request.
  $

  Looking through the logs I grabbed this stack trace 
http://paste.openstack.org/show/482123/
  The healthmonitor is unable to locate the pool it was attached to, since it 
has been deleted.

  Looking through the v1 code, it seems there was a check to make sure the pool 
was able to be deleted: 
https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_db.py#L619
  This check does not exist in the v2 code however:
  
https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/db/loadbalancer/loadbalancer_dbv2.py#L468

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1526964/+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 1450375] Re: cannot delete v2 healthmonitor if the hm-associated-pool was deleted first

2016-06-10 Thread Darek Smigiel

*** This bug is a duplicate of bug 1571097 ***
https://bugs.launchpad.net/bugs/1571097

Marked this bug as duplicate, even thou it was created earlier, but fix
is assigned to other one.

** This bug has been marked a duplicate of bug 1571097
   unable to delete lbaasv2 health monitor if its listener deleted

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

Title:
  cannot delete v2 healthmonitor if the hm-associated-pool was deleted
  first

Status in neutron:
  Fix Released

Bug description:
  Steps:
  1. create lb
  2. create listener
  3. create pool  (pool-1)
  4. add a healthmonitor (healthmonitor-1) to pool-1
  5. delete the pool-1

  Then, you cannot delete healthmonitor-1 if the pool-1 was deleted
  first.

  
  Log:

  2015-04-30 16:51:23.422 6369 INFO neutron.wsgi 
[req-2876374c-03c3-49b6-825c-83116108cbed cf6a52a3be734e4cad457d5283148882 
356b4d225c7e44de961d888086948f7c - - -] 172.16.2.10 - - [30/Apr/2015 16:51:23] 
"GET /v2.0/lbaas/healthmonitors.json?tenant_id=356b4d225c7e44de961d888086948f7c 
HTTP/1.1" 200 754 0.280336
  2015-04-30 16:51:23.430 6369 INFO neutron.wsgi [-] (6369) accepted 
('172.16.2.10', 17115)
  2015-04-30 16:51:23.532 6369 ERROR neutron.api.v2.resource 
[req-88a2316d-805a-4bad-a52b-b270325008e7 cf6a52a3be734e4cad457d5283148882 
356b4d225c7e44de961d888086948f7c - - -] delete failed
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource Traceback (most 
recent call last):
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py", line 83, in 
resource
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource result = 
method(request=request, **args)
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.6/site-packages/neutron/api/v2/base.py", line 490, in delete
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource 
obj_deleter(request.context, id, **kwargs)
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.6/site-packages/neutron_lbaas/services/loadbalancer/plugin.py",
 line 887, in delete_healthmonitor
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource 
constants.PENDING_DELETE)
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.6/site-packages/neutron_lbaas/db/loadbalancer/loadbalancer_dbv2.py",
 line 159, in test_and_set_status
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource 
db_lb_child.root_loadbalancer.id)
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.6/site-packages/neutron_lbaas/db/loadbalancer/models.py", 
line 115, in root_loadbalancer
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource return 
self.pool.listener.loadbalancer
  2015-04-30 16:51:23.532 6369 TRACE neutron.api.v2.resource AttributeError: 
'NoneType' object has no attribute 'listener'

  
  Code:

  class HealthMonitorV2(model_base.BASEV2, models_v2.HasId,
  models_v2.HasTenant):

  ...

  @property
  def root_loadbalancer(self):
  return self.pool.listener.loadbalancer

  
  Potential Solution:
  1. Check pool whether binding a healthmonitor before delete
  2. Add loadbalancer attr to HealthMonitorV2

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1450375/+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 1566178] Re: Lbaasv2 healthmonitor is not deleted

2016-06-10 Thread Darek Smigiel

*** This bug is a duplicate of bug 1571097 ***
https://bugs.launchpad.net/bugs/1571097

** This bug is no longer a duplicate of bug 1450375
   cannot delete v2 healthmonitor if the hm-associated-pool was deleted first
** This bug has been marked a duplicate of bug 1571097
   unable to delete lbaasv2 health monitor if its listener deleted

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

Title:
  Lbaasv2 healthmonitor is not deleted

Status in neutron:
  Incomplete

Bug description:
  I was running neutron_lbaas tempest automation tests, In this case test which 
tests basic HealthMonitor test. 
  The test configures LB,Listener, pool, members. Then configures the HM.
  In the end of the test all automatically created objects are removed ( in the 
opposite order of the creation) 
  I stopped the test when all objects created in order to manually check LB.
  I created and attached new healtmonitor to the pool ( PING hm).
  After validation I continued the test run , which should delete all related 
to the test object. I saw that   the newly created HM is not deleted.

  I have 3 controllers which are also neutron servers and 2 compute nodes 
(VIRTUAL ENV)
  The loadbalncer objects are created only one one of the controllers.
  the objects are created by admin user on non-admin tenant. 

  Reproduction steps:
  1.Create Lbaas,listener,pool,members
  2. Create HM and attach it to the pool.
  3. delete pool
  4. Try to delete HM .

  
  logs:
  http://pastebin.com/KdZ6mY4X
  http://pastebin.com/hgqv8T3Q
  The steps:

  1.Create Lbaas,listener,pool,members
  2. Create HM and attach it to the pool.
  3. delete pool, Delete listener' delete LB 
  4. Try to delete HM .

  I wanted result should be that the HM will be deleted.

  The HM was not removed - "internal server error" (see logs in pastebin
  links)

  Liberty
  RHEL 7.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1566178/+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 1571097] Re: unable to delete lbaasv2 health monitor if its listener deleted

2016-06-10 Thread Darek Smigiel

** This bug is no longer a duplicate of bug 1450375
   cannot delete v2 healthmonitor if the hm-associated-pool was deleted first

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

Title:
  unable to delete lbaasv2 health monitor if its listener deleted

Status in neutron:
  Fix Released

Bug description:
  problem is in Kilo neutron-lbaas branch.

  monitor is attached a pool.
  When pool and listener were deleted, not error reported that there is a 
health-monitor associated to pool.

  If all lbaas resoruces except health-monitor were deleted, health
  monitor can not be deleted.

  See the following procedure to reproduce this issue:

  $ neutron lbaas-loadbalancer-create --name=v-lb2 lb2-v-1574810802
  $ neutron lbaas-listener-create --protocol=HTTP --protocol-port=80 
--name=v-lb2-1 --loadbalancer=v-lb2
  $ neutron lbaas-pool-create --lb-algorithm=ROUND_ROBIN --protocol=HTTP 
--name=v-lb2-pool  --listener=v-lb2-1
  $ neutron lbaas-member-create --subnet lb2-v-1574810802 --address 10.199.88.3 
--protocol-port=80 v-lb2-pool
  $ neutron lbaas-member-create --subnet lb2-v-1574810802 --address 10.199.88.4 
--protocol-port=80 v-lb2-pool
  $ neutron lbaas-healthmonitor-create --max-retries=3 --delay=3 --timeout=10 
--type=HTTP --pool=v-lb2-pool
  $ neutron lbaas-member-delete 4d2977fc-5600-4dbf-8af2-35c017c8f4a0 v-lb2-pool 
  $ neutron lbaas-member-delete 2f60a49b-add1-43d6-97d8-4e53a925b25f  
v-lb2-pool 
  $ neutron lbaas-pool-delete v-lb2-pool
  $ neutron lbaas-listener-delete v-lb2-1
  $ neutron lbaashealthmonitor-delete 044f98a5-755d-498d-a38e-18eb8ca13884

  neutron log seems point to lbaas resources were gone.
  In this specific issue, we should just remove the health monitor from system.

  2016-04-10 16:57:38.220 INFO neutron.wsgi 
[req-7e697943-e70d-4ac8-a840-b1edf441806a Venus Venus] 10.34.57.68 - - 
[10/Apr/2016 16:57:38] "GET 
/v2.0/lbaas/healthmonitors.json?fields=id=044f98a5-755d-498d-a38e-18eb8ca13884
 HTTP/1.1" 200 444 0.112257
  2016-04-10 16:57:38.252 ERROR neutron.api.v2.resource 
[req-aaeae392-33b2-427c-96a0-918782882c9a Venus Venus] delete failed
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource Traceback (most 
recent call last):
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/resource.py", line 83, in resource
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource result = 
method(request=request, **args)
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/base.py", line 490, in delete
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource 
obj_deleter(request.context, id, **kwargs)
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron-lbaas/neutron_lbaas/services/loadbalancer/plugin.py", line 
906, in delete_healthmonitor
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource 
constants.PENDING_DELETE)
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron-lbaas/neutron_lbaas/db/loadbalancer/loadbalancer_dbv2.py", 
line 163, in test_and_set_status
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource 
db_lb_child.root_loadbalancer.id)
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron-lbaas/neutron_lbaas/db/loadbalancer/models.py", line 115, 
in root_loadbalancer
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource return 
self.pool.listener.loadbalancer
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource AttributeError: 
'NoneType' object has no attribute 'listener'
  2016-04-10 16:57:38.252 4158 TRACE neutron.api.v2.resource 
  2016-04-10 16:57:38.253 INFO neutron.wsgi 
[req-aaeae392-33b2-427c-96a0-918782882c9a Venus Venus] 10.34.57.68 - - 
[10/Apr/2016 16:57:38] "DELETE 
/v2.0/lbaas/healthmonitors/044f98a5-755d-498d-a38e-18eb8ca13884.json HTTP/1.1" 
500 383 0.030720

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1571097/+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 1588472] Re: tox -e genconfig - maximum recursion depth exceeded

2016-06-02 Thread Darek Smigiel

s/PIP/tox

** 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/1588472

Title:
  tox -e genconfig - maximum recursion depth exceeded

Status in neutron:
  Invalid

Bug description:
  When running 'tox -e genconfig' on stable/mitaka of neutron, I get the
  following (running on Ubuntu 14.04):

File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 989, in 
_replace_match
  return handler(match)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 913, in 
_replace_env
  env_list = self.getdict('setenv')
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 839, in 
getdict
  s = self.getstring(name, None)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 893, in 
getstring
  x = self._replace(x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 993, in 
_replace
  return RE_ITEM_REF.sub(self._replace_match, x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 989, in 
_replace_match
  return handler(match)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 913, in 
_replace_env
  env_list = self.getdict('setenv')
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 839, in 
getdict
  s = self.getstring(name, None)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 893, in 
getstring
  x = self._replace(x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 993, in 
_replace
  return RE_ITEM_REF.sub(self._replace_match, x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 989, in 
_replace_match
  return handler(match)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 913, in 
_replace_env
  env_list = self.getdict('setenv')
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 839, in 
getdict
  s = self.getstring(name, None)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 893, in 
getstring
  x = self._replace(x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 993, in 
_replace
  return RE_ITEM_REF.sub(self._replace_match, x)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 989, in 
_replace_match
  return handler(match)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 959, in 
_replace_substitution
  val = self._substitute_from_other_section(sub_key)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 941, in 
_substitute_from_other_section
  if section in self._cfg and item in self._cfg[section]:
File "/usr/lib/python2.7/dist-packages/py/_iniconfig.py", line 151, in 
__getitem__
  return SectionWrapper(self, name)
  RuntimeError: maximum recursion depth exceeded while calling a Python object

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1588472/+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 1585031] Re: osprofiler change broke out-of-tree unit tests

2016-05-24 Thread Darek Smigiel

*** This bug is a duplicate of bug 1585075 ***
https://bugs.launchpad.net/bugs/1585075

@Yamamoto, I'm sorry for inconvenience with changing duplicates, but 
"duplicate" was already merged.
This will allow to track place, where initial fix was done.

** This bug has been marked a duplicate of bug 1585075
   OSProfiler break decomposed unit tests

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

Title:
  osprofiler change broke out-of-tree unit tests

Status in neutron:
  In Progress

Bug description:
  the recently merged ofprofiler change [1] broke out-of-tree code.

  [1] I7fa2ad57dc5763ce72cba6945ebcadef2188e8bd

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%20%5C%22no%20such%20option%20in%20group%20DEFAULT%3A%20profiler%5C%22

  eg.
  
http://logs.openstack.org/81/320181/2/check/gate-tap-as-a-service-python27/60fc1d1/testr_results.html.gz

  Traceback (most recent call last):
File 
"/home/jenkins/workspace/gate-tap-as-a-service-python27/.tox/py27/local/lib/python2.7/site-packages/fixtures/fixture.py",
 line 197, in setUp
  self._setUp()
File 
"/home/jenkins/workspace/gate-tap-as-a-service-python27/.tox/py27/src/neutron/neutron/tests/unit/testlib_api.py",
 line 67, in _setUp
  engine = db_api.get_engine()
File 
"/home/jenkins/workspace/gate-tap-as-a-service-python27/.tox/py27/src/neutron/neutron/db/api.py",
 line 73, in get_engine
  facade = _create_facade_lazily()
File 
"/home/jenkins/workspace/gate-tap-as-a-service-python27/.tox/py27/src/neutron/neutron/db/api.py",
 line 63, in _create_facade_lazily
  if cfg.CONF.profiler.enabled and cfg.CONF.profiler.trace_sqlalchemy:
File 
"/home/jenkins/workspace/gate-tap-as-a-service-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_config/cfg.py",
 line 2183, in __getattr__
  raise NoSuchOptError(name)
  oslo_config.cfg.NoSuchOptError: no such option in group DEFAULT: profiler

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1585031/+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 1558205] [NEW] neutron-lbaas plugin installation breaks on gates

2016-03-20 Thread Darek Smigiel

Public bug reported:

Because of latest changes for neutron-lbaas devstack configuration, all
gates are broken.

VM with devstack doesn't have `add-apt-repository` command. added in
this commit https://github.com/openstack/neutron-
lbaas/commit/eb2a61b4e9082f97d3bc5c8ec9d02d29914e68a7


2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L10:
   [[ False == False ]]
2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L11:
   BACKPORT='deb http://archive.ubuntu.com/ubuntu trusty-backports main 
restricted universe multiverse'
2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep '^' /etc/apt/sources.list '/etc/apt/sources.list.d/*'
2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep 'deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted 
universe multiverse'
2016-03-16 17:40:42.788 | grep: /etc/apt/sources.list.d/*: No such file or 
directory
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   BACKPORT_EXISTS=
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   true
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L13:
   [[ -z '' ]]
2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L14:
   sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu 
trusty-backports main restricted universe multiverse' -y
2016-03-16 17:40:42.792 | sudo: add-apt-repository: command not found
2016-03-16 17:40:42.793 | + 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L1:
   exit_trap
2016-03-16 17:40:42.793 | + ./stack.sh:exit_trap:L474:   local r=1

** Affects: neutron
 Importance: Critical
 Assignee: Brandon Logan (brandon-logan)
 Status: New


** Tags: lbaas

** Changed in: neutron
   Importance: Undecided => Critical

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

Title:
  neutron-lbaas plugin installation breaks on gates

Status in neutron:
  New

Bug description:
  Because of latest changes for neutron-lbaas devstack configuration,
  all gates are broken.

  VM with devstack doesn't have `add-apt-repository` command. added in
  this commit https://github.com/openstack/neutron-
  lbaas/commit/eb2a61b4e9082f97d3bc5c8ec9d02d29914e68a7

  
  2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L10:
   [[ False == False ]]
  2016-03-16 17:40:42.787 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L11:
   BACKPORT='deb http://archive.ubuntu.com/ubuntu trusty-backports main 
restricted universe multiverse'
  2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep '^' /etc/apt/sources.list '/etc/apt/sources.list.d/*'
  2016-03-16 17:40:42.787 | +++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   grep 'deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted 
universe multiverse'
  2016-03-16 17:40:42.788 | grep: /etc/apt/sources.list.d/*: No such file or 
directory
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   BACKPORT_EXISTS=
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L12:
   true
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L13:
   [[ -z '' ]]
  2016-03-16 17:40:42.789 | ++ 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L14:
   sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu 
trusty-backports main restricted universe multiverse' -y
  2016-03-16 17:40:42.792 | sudo: add-apt-repository: command not found
  2016-03-16 17:40:42.793 | + 
/opt/stack/new/neutron-lbaas/devstack/plugin.sh:neutron_agent_lbaas_install_agent_packages:L1:
   exit_trap
  2016-03-16 17:40:42.793 | + ./stack.sh:exit_trap:L474:   local r=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1558205/+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   :

[Yahoo-eng-team] [Bug 1657668] Re: Grammer error in LoadBalancerPluginv2

[Yahoo-eng-team] [Bug 1656386] [NEW] Memory leaks on linuxbridge job

[Yahoo-eng-team] [Bug 1650270] Re: Neutron-LBaaS v2: mapping HAproxy process to cpu core

[Yahoo-eng-team] [Bug 1650170] Re: Return error but create successfully when create lbaas pool with a PENDING_UPDATE loadbalancer

[Yahoo-eng-team] [Bug 1577541] Re: Neutron-LBaaS v2: TLS Listeners Functional Tests

[Yahoo-eng-team] [Bug 1646770] Re: lbaas tempest test cases are not executing

[Yahoo-eng-team] [Bug 1627044] Re: Last chance call to neutron if VIF plugin notification is lost

[Yahoo-eng-team] [Bug 1642167] Re: Move neutron.common.utils.wait_until_true to neutron-lib

[Yahoo-eng-team] [Bug 1641813] Re: stable/newton branch creation request for networking-odl

[Yahoo-eng-team] [Bug 1637972] Re: VPNaaS: report_state fails by key error 'tenant_id'

[Yahoo-eng-team] [Bug 1632633] Re: fix some word spelling error

[Yahoo-eng-team] [Bug 1632633] Re: fix some word spelling error

[Yahoo-eng-team] [Bug 1630134] Re: Networking API v2.0 (CURRENT): Update Network Request missing the 'qos-policy-id' parameter.

[Yahoo-eng-team] [Bug 1624103] Re: Neutron accepting multiple networks/subnets to be created with same name, network address

[Yahoo-eng-team] [Bug 1620835] Re: Add timestamp fields for neutron ext resources

[Yahoo-eng-team] [Bug 1618691] Re: LBaaS v2 and Keystone v3 in Devstack

[Yahoo-eng-team] [Bug 1616745] Re: IP allocation with Service Subnets

[Yahoo-eng-team] [Bug 1595574] Re: VXLan fails to be created between dhcp and compute node

[Yahoo-eng-team] [Bug 1597168] Re: There's no way to update '--shared' argument of qos-policy to False by using qos-policy-update command.

[Yahoo-eng-team] [Bug 1597168] Re: There's no way to update '--shared' argument of qos-policy to False by using qos-policy-update command.

[Yahoo-eng-team] [Bug 1594405] Re: test_secure_client fails

[Yahoo-eng-team] [Bug 1593967] Re: neutron command need filtering

[Yahoo-eng-team] [Bug 1593436] Re: Fix designate dns driver for SSL based endpoints

[Yahoo-eng-team] [Bug 1592594] Re: DHCP: delete config option dnsmasq_dns_server

[Yahoo-eng-team] [Bug 1592564] [NEW] gate-neutron-lbaasv2-dsvm-minimal is failing

[Yahoo-eng-team] [Bug 1526964] Re: Can delete lbaas-pool with lbaas-hm attached

[Yahoo-eng-team] [Bug 1450375] Re: cannot delete v2 healthmonitor if the hm-associated-pool was deleted first

[Yahoo-eng-team] [Bug 1566178] Re: Lbaasv2 healthmonitor is not deleted

[Yahoo-eng-team] [Bug 1571097] Re: unable to delete lbaasv2 health monitor if its listener deleted

[Yahoo-eng-team] [Bug 1588472] Re: tox -e genconfig - maximum recursion depth exceeded

[Yahoo-eng-team] [Bug 1585031] Re: osprofiler change broke out-of-tree unit tests

[Yahoo-eng-team] [Bug 1558205] [NEW] neutron-lbaas plugin installation breaks on gates

32 matches

Site Navigation

Mail list logo

Footer information