[Yahoo-eng-team] [Bug 1436957] Re: assertRaisesRegexp has been deprecated for assertRaisesRegex
** Also affects: python-magnumclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1436957 Title: assertRaisesRegexp has been deprecated for assertRaisesRegex Status in OpenStack Identity (keystone): In Progress Status in python-keystoneclient: Fix Released Status in python-magnumclient: New Status in tacker: In Progress Status in watcher: Fix Released Bug description: I am trying to enable tests using tap format for keystone, once I ran nosetests --with-tap, a warning message was shown for keystoneclient/tests/unit/test_session.py:238: Pending DeprecationWarning: Please use assertRegex instead To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1436957/+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 1629133] Re: New neutron subnet pool support breaks multinode testing.
** Also affects: magnum 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/1629133 Title: New neutron subnet pool support breaks multinode testing. Status in devstack: In Progress Status in Ironic: New Status in Magnum: New Status in Manila: New Status in neutron: Incomplete Bug description: The new subnet pool support in devstack breaks multinode testing bceause it results in the route for 10.0.0.0/8 being set to via br-ex when the host has interfaces that are actually on 10 nets and that is where we need the routes to go out. Multinode testing is affected because it uses these 10 net addresses to run the vxlan overlays between hosts. For many years devstack-gate has set FIXED_RANGE to ensure that the networks devstack uses do not interfere with the underlying test host's networking. However this setting was completely ignored when setting up the subnet pools. I think the correct way to fix this is to use a much smaller subnet pool range to avoid conflicting with every possible 10.0.0.0/8 network in the wild, possibly by defaulting to the existing FIXED_RANGE information. Using the existing information will help ensure that anyone with networks in 10.0.0.0/8 will continue to work if they have specified a range that doesn't conflict using this variable. In addition to this we need to clearly document what this new stuff in devstack does and how people can work around it should they conflict with the new defaults we end up choosing. I have proposed https://review.openstack.org/379543 which mostly works except it fails one tempest test that apparently depends on this new subnet pool stuff. Specifically the V6 range isn't large enough aiui. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1629133/+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 1629726] Re: recompiled pycparser 2.14 breaks Cinder db sync and Nova UTs
** Also affects: magnum Importance: Undecided Status: New ** Changed in: magnum Importance: Undecided => Critical ** Changed in: magnum Status: New => Confirmed -- 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/1629726 Title: recompiled pycparser 2.14 breaks Cinder db sync and Nova UTs Status in Cinder: Confirmed Status in Designate: Confirmed Status in ec2-api: Confirmed Status in gce-api: Confirmed Status in heat: Confirmed Status in Ironic: Confirmed Status in Magnum: Confirmed Status in Manila: Confirmed Status in networking-cisco: New Status in OpenStack Compute (nova): Confirmed Status in Rally: Confirmed Status in OpenStack DBaaS (Trove): Confirmed Bug description: http://logs.openstack.org/76/380876/1/check/gate-grenade-dsvm-ubuntu- xenial/3d5e102/logs/grenade.sh.txt.gz#_2016-10-02_23_32_34_069 2016-10-02 23:32:34.069 | + lib/cinder:init_cinder:421 : /usr/local/bin/cinder-manage --config-file /etc/cinder/cinder.conf db sync 2016-10-02 23:32:34.691 | Traceback (most recent call last): 2016-10-02 23:32:34.691 | File "/usr/local/bin/cinder-manage", line 6, in 2016-10-02 23:32:34.691 | from cinder.cmd.manage import main 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/cmd/manage.py", line 77, in 2016-10-02 23:32:34.691 | from cinder import db 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/db/__init__.py", line 20, in 2016-10-02 23:32:34.691 | from cinder.db.api import * # noqa 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/db/api.py", line 43, in 2016-10-02 23:32:34.691 | from cinder.api import common 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/api/common.py", line 30, in 2016-10-02 23:32:34.691 | from cinder import utils 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/utils.py", line 40, in 2016-10-02 23:32:34.691 | from os_brick import encryptors 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/__init__.py", line 16, in 2016-10-02 23:32:34.691 | from os_brick.encryptors import nop 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/nop.py", line 16, in 2016-10-02 23:32:34.691 | from os_brick.encryptors import base 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/base.py", line 19, in 2016-10-02 23:32:34.691 | from os_brick import executor 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/executor.py", line 21, in 2016-10-02 23:32:34.691 | from os_brick.privileged import rootwrap as priv_rootwrap 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/privileged/__init__.py", line 13, in 2016-10-02 23:32:34.691 | from oslo_privsep import capabilities as c 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/oslo_privsep/capabilities.py", line 73, in 2016-10-02 23:32:34.691 | ffi.cdef(CDEF) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/api.py", line 105, in cdef 2016-10-02 23:32:34.692 | self._cdef(csource, override=override, packed=packed) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/api.py", line 119, in _cdef 2016-10-02 23:32:34.692 | self._parser.parse(csource, override=override, **options) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 299, in parse 2016-10-02 23:32:34.692 | self._internal_parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 304, in _internal_parse 2016-10-02 23:32:34.692 | ast, macros, csource = self._parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 260, in _parse 2016-10-02 23:32:34.692 | ast = _get_parser().parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 40, in _get_parser 2016-10-02 23:32:34.692 | _parser_cache = pycparser.CParser() 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/c_parser.py", line 87, in __init__ 2016-10-02 23:32:34.692 | outputdir=taboutputdir) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/c_lexer.py", line 66, in build 2016-10-02 23:32:34.692 | self.lexer = lex.lex(object=self, **kwargs) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/ply/lex.py", line 911, in lex 2016-10-02 23:32:34.692 | lexobj.readtab(lextab, ldict) 2016-10-02 23:32:34.692 | File
[Yahoo-eng-team] [Bug 1629830] Re: pycparser-2.14 wheel is wrongly built and raises AssertionError
*** This bug is a duplicate of bug 1629726 *** https://bugs.launchpad.net/bugs/1629726 ** Also affects: magnum 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/1629830 Title: pycparser-2.14 wheel is wrongly built and raises AssertionError Status in heat: New Status in Ironic: New Status in Magnum: New Status in OpenStack Compute (nova): Confirmed Bug description: Most of our gate jobs are impacted (Nova UTs, Tempest tests, Grenade checks) by a new respin of pycparser that raises an AssertionError when imported. Note that not only Nova but a lot of OpenStack projects are impacted : http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%20\%22AssertionError:%20sorry,%20but%20this%20version%20only%20supports%20100%20named%20groups\%22=24h The issue has been logged upstream https://github.com/eliben/pycparser/issues/147 but we somehow need to downgrade pycparser first in order to stabilize our gates. To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1629830/+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 1498130] Re: LBaaSv2: Can't delete the Load balancer and also dependant entities if the load balancer provisioning_status is in PENDING_UPDATE
Any advice for that? I even modified the db and didn't work.
So for the use case:
In openstack/magnum we have an option to use lbaas for our clusters. Two lbaas'
are created one for etcd and one for api. These lbaas' are created with heat.
If for any reason (unrelated to lbaas) the heat creation fails we want to
delete the stack, but it is impossible because we can't delete the load
balancers.
One more thing I tried and failed:
I tried to use an even smaller flavor than m1.amphora with 512mb RAM and the
lbaas creation as stack.
** 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/1498130
Title:
LBaaSv2: Can't delete the Load balancer and also dependant entities
if the load balancer provisioning_status is in PENDING_UPDATE
Status in neutron:
New
Bug description:
If the Load balancer provisioning_status is in PENDING_UPDATE
cannot delete the Loadbalancer and also dependent entities like
listener or pool
neutron -v lbaas-listener-delete 6f9fdf3a-4578-4e3e-8b0b-f2699608b7e6
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://9.197.47.200:5000/v2.0 -H "Accept: application/json" -H "User-Agent:
python-keystoneclient"
DEBUG: keystoneclient.session RESP: [200] content-length: 338 vary:
X-Auth-Token connection: keep-alive date: Mon, 21 Sep 2015 18:35:55 GMT
content-type: application/json x-openstack-request-id:
req-952f21b0-81bf-4e0f-a6c8-b3fc13ac4cd2
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "http://9.197.47.200:5000/v2.0/;, "rel": "self"}, {"href":
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}
DEBUG: neutronclient.neutron.v2_0.lb.v2.listener.DeleteListener
run(Namespace(id=u'6f9fdf3a-4578-4e3e-8b0b-f2699608b7e6',
request_format='json'))
DEBUG: keystoneclient.auth.identity.v2 Making authentication request to
http://9.197.47.200:5000/v2.0/tokens
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://9.197.47.200:9696/v2.0/lbaas/listeners.json?fields=id=6f9fdf3a-4578-4e3e-8b0b-f2699608b7e6
-H "User-Agent: python-neutronclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}9ea944020f06fa79f4b6db851dbd9e69aca65d58"
DEBUG: keystoneclient.session RESP: [200] date: Mon, 21 Sep 2015 18:35:56 GMT
connection: keep-alive content-type: application/json; charset=UTF-8
content-length: 346 x-openstack-request-id:
req-fd7ee22b-f776-4ebd-94c6-7548a5aff362
RESP BODY: {"listeners": [{"protocol_port": 100, "protocol": "TCP",
"description": "", "sni_container_ids": [], "admin_state_up": true,
"loadbalancers": [{"id": "ab8f76ec-236f-4f4c-b28e-cd7bfee48cd2"}],
"default_tls_container_id": null, "connection_limit": 100, "default_pool_id":
null, "id": "6f9fdf3a-4578-4e3e-8b0b-f2699608b7e6", "name": "listener100"}]}
DEBUG: keystoneclient.session REQ: curl -g -i -X DELETE
http://9.197.47.200:9696/v2.0/lbaas/listeners/6f9fdf3a-4578-4e3e-8b0b-f2699608b7e6.json
-H "User-Agent: python-neutronclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}9ea944020f06fa79f4b6db851dbd9e69aca65d58"
DEBUG: keystoneclient.session RESP:
DEBUG: neutronclient.v2_0.client Error message: {"NeutronError": {"message":
"Invalid state PENDING_UPDATE of loadbalancer resource
ab8f76ec-236f-4f4c-b28e-cd7bfee48cd2", "type": "StateInvalid", "detail": ""}}
ERROR: neutronclient.shell Invalid state PENDING_UPDATE of loadbalancer
resource ab8f76ec-236f-4f4c-b28e-cd7bfee48cd2
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/neutronclient/shell.py", line 766,
in run_subcommand
return run_command(cmd, cmd_parser, sub_argv)
File "/usr/lib/python2.7/site-packages/neutronclient/shell.py", line 101,
in run_command
return cmd.run(known_args)
File
"/usr/lib/python2.7/site-packages/neutronclient/neutron/v2_0/__init__.py", line
581, in run
obj_deleter(_id)
File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line
102, in with_params
ret = self.function(instance, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line
932, in delete_listener
return self.delete(self.lbaas_listener_path % (lbaas_listener))
File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line
289, in delete
headers=headers, params=params)
File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line
270, in retry_request
headers=headers, params=params)
File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line
211, in do_request
self._handle_fault_response(status_code, replybody)
File
