[Yahoo-eng-team] [Bug 1641433] Re: Deprecate SR-IOV 'physical_device_mappings' config option
** 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/1641433 Title: Deprecate SR-IOV 'physical_device_mappings' config option Status in neutron: Invalid Status in openstack-manuals: New Bug description: https://review.openstack.org/395044 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 03b84bc920b5499e1fef23c646268fffa1d859d7 Author: Edan David Date: Tue Nov 8 10:30:45 2016 -0500 Deprecate SR-IOV 'physical_device_mappings' config option The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. Closes-Bug: #1640220 DocImpact Change-Id: I5f363347b327212a49a9b78a7164c11d9e457b10 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1641433/+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 1640835] Re: neutron doesn't report invalid values passed to it
Got your point. I'll close this bug as the issue seems to be fixed!
Thanks for finding out!
** 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/1640835
Title:
neutron doesn't report invalid values passed to it
Status in neutron:
Invalid
Bug description:
[stack@undercloud ~]$ neutron port-list | grep
699107e1-bdf7-4044-83fc-65201fb28f57
| 699107e1-bdf7-4044-83fc-65201fb28f57 | |
00:6e:03:64:5d:ad | {"subnet_id": "06e61421-520b-4afb-ad15-1e31e1503e44",
"ip_address": "192.0.2.9"} |
[stack@undercloud ~]$ nova list
+--++++-++
| ID | Name | Status |
Task State | Power State | Networks |
+--++++-++
| 9751809b-5033-43ca-bc8d-334e9acf2d4e | overcloud-controller-0 | ACTIVE | -
| Running | ctlplane=192.0.2.9 |
| 74a6b21a-db53-492d-bb36-9d05a70ef8d2 | overcloud-controller-2 | ACTIVE | -
| Running | ctlplane=192.0.2.6 |
+--++++-++
[stack@undercloud ~]$ nova stop 9751809b-5033-43ca-bc8d-334e9acf2d4e
Request to stop server 9751809b-5033-43ca-bc8d-334e9acf2d4e has been accepted.
[stack@undercloud ~]$ nova list
+--++-++-++
| ID | Name | Status |
Task State | Power State | Networks |
+--++-++-++
| 9751809b-5033-43ca-bc8d-334e9acf2d4e | overcloud-controller-0 | SHUTOFF | -
| Shutdown| ctlplane=192.0.2.9 |
| 74a6b21a-db53-492d-bb36-9d05a70ef8d2 | overcloud-controller-2 | ACTIVE | -
| Running | ctlplane=192.0.2.6 |
+--++-++-++
[stack@undercloud ~]$ neutron port-update --fixed-ip
subnet_id=06e61421-520b-4afb-ad15-1e31e1503e44,ip=192.0.2.26
699107e1-bdf7-4044-83fc-65201fb28f57
Updated port: 699107e1-bdf7-4044-83fc-65201fb28f57
[stack@undercloud ~]$ nova start 9751809b-5033-43ca-bc8d-334e9acf2d4e
Request to start server 9751809b-5033-43ca-bc8d-334e9acf2d4e has been
accepted.
[stack@undercloud ~]$ nova list
+--++++-+-+
| ID | Name | Status |
Task State | Power State | Networks|
+--++++-+-+
| 9751809b-5033-43ca-bc8d-334e9acf2d4e | overcloud-controller-0 | ACTIVE | -
| Running | ctlplane=192.0.2.10 |
| 74a6b21a-db53-492d-bb36-9d05a70ef8d2 | overcloud-controller-2 | ACTIVE | -
| Running | ctlplane=192.0.2.6 |
+--++++-+-+
- If used with ip=192.0.2.26 it won't report any issues, but will
automatically +1 on the IP from the pool.
Would be nice if the neutron has some input checks on whether the
value is one of the known ones.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640835/+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 1641523] [NEW] Nova can't force-delete instance that is stuck in deleting process
Public bug reported: I tried to delete an instance that got into error state during creation. And it's stuck in deleting "Task State". I checked with virsh and instance is not present. And after I tried to force-delete it nova client crashed with a message that it should be reported as bug. Installation is Newton on Centos 7. Here is part of nova-api.log 2016-11-14 08:37:05.099 4189 INFO nova.osapi_compute.wsgi.server [req-37d453be-6f18-479d-bae8-6b24493a3366 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] 10.6.0.11 "GET /v2.1/ HTTP/1.1" status: 200 len: 714 time: 0.0065050 2016-11-14 08:37:05.569 4189 INFO nova.osapi_compute.wsgi.server [req-9a5d94a1-a2cf-45b8-bfac-5f231f3e07b7 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] 10.6.0.11 "GET /v2.1/43dec04d0696450787fee3580b9780de/servers/198b4ce6-84cc-4a45-8eda-d0b3262f3df4 HTTP/1.1" status: 200 len: 2243 time: 0.2764120 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions [req-fa12df45-bf9b-471b-8914-24a57427e358 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] Unexpected exception in API method 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/deferred_delete.py", line 64, in _force_delete 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions self.compute_api.force_delete(context, instance) 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 165, in inner 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions return function(self, context, instance, *args, **kwargs) 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 138, in inner 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions method=f.__name__) 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions InstanceInvalidState: Instance 198b4ce6-84cc-4a45-8eda-d0b3262f3df4 in task_state deleting. Cannot force_delete while the instance is in this state. 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions 2016-11-14 08:37:05.651 4189 INFO nova.api.openstack.wsgi [req-fa12df45-bf9b-471b-8914-24a57427e358 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] HTTP exception thrown: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. ** 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/1641523 Title: Nova can't force-delete instance that is stuck in deleting process Status in OpenStack Compute (nova): New Bug description: I tried to delete an instance that got into error state during creation. And it's stuck in deleting "Task State". I checked with virsh and instance is not present. And after I tried to force-delete it nova client crashed with a message that it should be reported as bug. Installation is Newton on Centos 7. Here is part of nova-api.log 2016-11-14 08:37:05.099 4189 INFO nova.osapi_compute.wsgi.server [req-37d453be-6f18-479d-bae8-6b24493a3366 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] 10.6.0.11 "GET /v2.1/ HTTP/1.1" status: 200 len: 714 time: 0.0065050 2016-11-14 08:37:05.569 4189 INFO nova.osapi_compute.wsgi.server [req-9a5d94a1-a2cf-45b8-bfac-5f231f3e07b7 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] 10.6.0.11 "GET /v2.1/43dec04d0696450787fee3580b9780de/servers/198b4ce6-84cc-4a45-8eda-d0b3262f3df4 HTTP/1.1" status: 200 len: 2243 time: 0.2764120 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions [req-fa12df45-bf9b-471b-8914-24a57427e358 24bef1856bf643c2bda92b710a7a6fcd 43dec04d0696450787fee3580b9780de - default default] Unexpected exception in API method 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2016-11-14 08:37:05.651 4189 ERROR nova.api.openstack.extensi
[Yahoo-eng-team] [Bug 1361235] Re: visit horizon failure because of import module failure
** Also affects: openstack-ansible Importance: Undecided Status: New ** Changed in: openstack-ansible Status: New => In Progress ** Changed in: openstack-ansible Assignee: (unassigned) => Donovan Francesco (donovan-francesco) ** Changed in: openstack-ansible Importance: Undecided => High -- 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/1361235 Title: visit horizon failure because of import module failure Status in OpenStack Dashboard (Horizon): In Progress Status in openstack-ansible: In Progress Status in osprofiler: In Progress Status in python-mistralclient: Fix Released Status in tripleo: Fix Released Bug description: 1. Use TripleO to deploy both undercloud, and overcloud, and enable horizon when building images. 2. Visit horizon portal always failure, and has below errors in horizon_error.log [Wed Aug 20 01:45:58.441221 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] mod_wsgi (pid=5035): Exception occurred processing WSGI script '/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/django.wsgi'. [Wed Aug 20 01:45:58.441273 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] Traceback (most recent call last): [Wed Aug 20 01:45:58.441294 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 187, in __call__ [Wed Aug 20 01:45:58.449979 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self.load_middleware() [Wed Aug 20 01:45:58.45 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/core/handlers/base.py", line 44, in load_middleware [Wed Aug 20 01:45:58.450556 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] for middleware_path in settings.MIDDLEWARE_CLASSES: [Wed Aug 20 01:45:58.450576 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init__.py", line 54, in __getattr__ [Wed Aug 20 01:45:58.454248 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self._setup(name) [Wed Aug 20 01:45:58.454269 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init__.py", line 49, in _setup [Wed Aug 20 01:45:58.454305 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self._wrapped = Settings(settings_module) [Wed Aug 20 01:45:58.454319 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init __.py", line 128, in __init__ [Wed Aug 20 01:45:58.454338 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] mod = importlib.import_module(self.SETTINGS_MODULE) [Wed Aug 20 01:45:58.454350 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module [Wed Aug 20 01:45:58.462806 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] __import__(name) [Wed Aug 20 01:45:58.462826 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../openstack_dashboard/settings.py", line 28, in [Wed Aug 20 01:45:58.467136 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from openstack_dashboard import exceptions [Wed Aug 20 01:45:58.467156 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../openstack_dashboard/exceptions.py", line 22, in [Wed Aug 20 01:45:58.467667 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from keystoneclient import exceptions as keystoneclient [Wed Aug 20 01:45:58.467685 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../keystoneclient/__init__.py", line 28, in [Wed Aug 20 01:45:58.472968 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from keystoneclient import client [Wed Aug 20 01:45:58.472989 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../keystoneclient/client.py", line 13, in [Wed Aug 20 01:45:58.473833 2014] [:error] [pid 5035:tid 3038755648] [remote
[Yahoo-eng-team] [Bug 1641517] [NEW] spice can't support usb redirection
Public bug reported: I have a environment of Newton in ubuntu16.04, every component that i install is ok , then i build a vm with spice proxy,the configurations in nova.conf like : [spice] enabled = True agent_enabled = True server_listen = 0.0.0.0 server_proxyclient_address = $my_ip html5proxy_base_url = http://$my_ip:6082/spice_auto.html of course the console is also ok ,but when i want transfer some doc to vm from client usb, vm can't find the usb device there is nothing about usb in vm.xml : instance-0010 e465443f-32b6-4cb7-9e17-2aec45bac79f http://openstack.org/xmlns/libvirt/nova/1.0";> ccc 2016-11-11 09:23:24 256 1 0 0 1 admin admin 262144 262144 1 1024 /machine OpenStack Foundation OpenStack Nova 14.0.1 6a0225ac-4f57-329c-e89c-60965806fac3 e465443f-32b6-4cb7-9e17-2aec45bac79f Virtual Machine hvm destroy restart destroy /usr/bin/kvm-spice libvirt-e465443f-32b6-4cb7-9e17-2aec45bac79f libvirt-e465443f-32b6-4cb7-9e17-2aec45bac79f ** Affects: nova Importance: Undecided Assignee: wang jiedong (jeery) Status: New ** Changed in: nova Assignee: (unassigned) => wang jiedong (jeery) -- 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/1641517 Title: spice can't support usb redirection Status in OpenStack Compute (nova): New Bug description: I have a environment of Newton in ubuntu16.04, every component that i install is ok , then i build a vm with spice proxy,the configurations in nova.conf like : [spice] enabled = True agent_enabled = True server_listen = 0.0.0.0 server_proxyclient_address = $my_ip html5proxy_base_url = http://$my_ip:6082/spice_auto.html of course the console is also ok ,but when i want transfer some doc to vm from client usb, vm can't find the usb device there is nothing about usb in vm.xml : instance-0010 e465443f-32b6-4cb7-9e17-2aec45bac79f http://openstack.org/xmlns/libvirt/nova/1.0";> ccc 2016-11-11 09:23:24 256 1 0 0 1 admin admin 262144 262144 1 1024 /machine OpenStack Foundation OpenStack Nova 14.0.1 6a0225ac-4f57-329c-e89c-60965806fac3 e465443f-32b6-4cb7-9e17-2aec45bac79f Virtual Machine hvm destroy restart destroy /usr/bin/kvm-spice libvirt-e465443f-32b6-4cb7-9e17-2aec45bac79f libvirt-e465443f-32b6-4cb7-9e17-2aec45bac79f To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1641517/+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 1641509] [NEW] Creating vpn-service with router which belongs to another tenant causes invalid condition.
Public bug reported: - how to reproduce 1. to 5. and 12. are operated by TenantA 6. to 11. are operated by TenantB(should be context_is_admin.) ===operating by TenantA=== 1.neutron router-create router1 2.neutron net-create network1 3.neutron subnet-create network1 192.168.0.0/24 --name subnet1 4.neutron router-interface-add router1 subnet1 5.neutron router-gateway-set router1 public ===operating by TenantB=== 6.neutron vpn-service-create router1 --name vpnservice1 7.neutron vpn-ikepolicy-create ikepolicy1 8.neutron vpn-ipsecpolicy-create ipsecpolicy1 9.neutron vpn-endpoint-group-create --type subnet --value subnet1 --name endpoint1 10.neutron vpn-endpoint-group-create --type cidr --value 192.168.1.0/24 --name endpoint2 11.neutron ipsec-site-connection-create --vpnservice-id vpnservice1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --local-ep-group endpoint1 --peer-id 172.24.4.10 --peer-address 172.24.4.10 --psk test --peer-ep-group endpoint2 ===operating by TenantA=== 12.neutron router-gateway-clear router1 => The operation should be failed because vpn_service assumes gw_port is attached to the router. However, the operation is passed because 'TenantA' cannot find 'vpn_service' which belongs to 'TenantB' with own context. Alternatively, we should block creating vpn_service with router which belongs to another tenant. Following errors are caused by procedure 12. * VPN configuration(enable) is failed. * 500 error returns when creating additional site-connection for the vpn_service. - trace in vpn-agent 2016-11-14 05:15:10.863 27930 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'qrouter-0c80e9f8-e273-4770-8f02-6fc243301ac7', 'ip', 'route', 'get', '172.24.4.10'] execute_rootwrap_daemon /opt/stack/neutron/neutron/agent/linux/utils.py:107 2016-11-14 05:15:10.917 27930 ERROR neutron.agent.linux.utils [-] Exit code: 2; Stdin: ; Stdout: ; Stderr: RTNETLINK answers: Network is unreachable 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec [-] Failed to enable vpn process on router 0c80e9f8-e273-4770-8f02-6fc243301ac7 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec Traceback (most recent call last): 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 306, in enable 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec self.restart() 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 544, in restart 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec self.start() 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 634, in start 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec ipsec_site_conn['id']) 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 568, in _get_nexthop 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec routes = self._execute(['ip', 'route', 'get', ip_addr]) 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron-vpnaas/neutron_vpnaas/services/vpn/device_drivers/ipsec.py", line 411, in _execute 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec extra_ok_codes=extra_ok_codes) 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron/neutron/agent/linux/ip_lib.py", line 908, in execute 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec log_fail_as_error=log_fail_as_error, **kwargs) 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 146, in execute 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec raise ProcessExecutionError(msg, returncode=returncode) 2016-11-14 05:15:10.918 27930 ERROR neutron_vpnaas.services.vpn.device_drivers.ipsec ProcessExecutionError: Exit code: 2; Stdin: ; Stdout: ; Stderr: RTNETLINK answers: Network is unreachable - trace in neutron-server 2016-11-14 05:16:26.939 25357 ERROR neutron.api.v2.resource [req-5e2f3bb1-2e6b-495a-a327-47b1595668b5 6759f544889746448631792bb12bd2ea d713c7d4c02541d8b239d6d9761768e5 - - -] create failed: No details. 2016-11-14 05:16:26.939 25357 ERROR neutron.api.v2.resource Traceback (most re
[Yahoo-eng-team] [Bug 1641508] [NEW] image_api.get() in nova ignores custom properties of images.
Public bug reported: ImageMeta.from_dict() in nova.objects.image_meta.py only parse two type of key/value, _set_attr_from_legacy_name _set_attr_from_current_name any custom properties will be ignored. I'm writing a new type of virt.driver, and want to use custom properties, but compute.manager.py pass image_meta from ImageMeta.from_dict(), no way to get these custom properties. ** 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/1641508 Title: image_api.get() in nova ignores custom properties of images. Status in OpenStack Compute (nova): New Bug description: ImageMeta.from_dict() in nova.objects.image_meta.py only parse two type of key/value, _set_attr_from_legacy_name _set_attr_from_current_name any custom properties will be ignored. I'm writing a new type of virt.driver, and want to use custom properties, but compute.manager.py pass image_meta from ImageMeta.from_dict(), no way to get these custom properties. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1641508/+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 1361235] Re: visit horizon failure because of import module failure
** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Status: New => Triaged ** Changed in: horizon Importance: Undecided => Medium ** Changed in: horizon Milestone: None => ocata-1 -- 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/1361235 Title: visit horizon failure because of import module failure Status in OpenStack Dashboard (Horizon): In Progress Status in osprofiler: In Progress Status in python-mistralclient: Fix Released Status in tripleo: Fix Released Bug description: 1. Use TripleO to deploy both undercloud, and overcloud, and enable horizon when building images. 2. Visit horizon portal always failure, and has below errors in horizon_error.log [Wed Aug 20 01:45:58.441221 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] mod_wsgi (pid=5035): Exception occurred processing WSGI script '/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/django.wsgi'. [Wed Aug 20 01:45:58.441273 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] Traceback (most recent call last): [Wed Aug 20 01:45:58.441294 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 187, in __call__ [Wed Aug 20 01:45:58.449979 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self.load_middleware() [Wed Aug 20 01:45:58.45 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/core/handlers/base.py", line 44, in load_middleware [Wed Aug 20 01:45:58.450556 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] for middleware_path in settings.MIDDLEWARE_CLASSES: [Wed Aug 20 01:45:58.450576 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init__.py", line 54, in __getattr__ [Wed Aug 20 01:45:58.454248 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self._setup(name) [Wed Aug 20 01:45:58.454269 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init__.py", line 49, in _setup [Wed Aug 20 01:45:58.454305 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] self._wrapped = Settings(settings_module) [Wed Aug 20 01:45:58.454319 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/conf/__init __.py", line 128, in __init__ [Wed Aug 20 01:45:58.454338 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] mod = importlib.import_module(self.SETTINGS_MODULE) [Wed Aug 20 01:45:58.454350 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module [Wed Aug 20 01:45:58.462806 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] __import__(name) [Wed Aug 20 01:45:58.462826 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../openstack_dashboard/settings.py", line 28, in [Wed Aug 20 01:45:58.467136 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from openstack_dashboard import exceptions [Wed Aug 20 01:45:58.467156 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../openstack_dashboard/exceptions.py", line 22, in [Wed Aug 20 01:45:58.467667 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from keystoneclient import exceptions as keystoneclient [Wed Aug 20 01:45:58.467685 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../keystoneclient/__init__.py", line 28, in [Wed Aug 20 01:45:58.472968 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from keystoneclient import client [Wed Aug 20 01:45:58.472989 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] File "/opt/stack/venvs/openstack/lib/python2.7/site-packages/openstack_dashboard/wsgi/../../keystoneclient/client.py", line 13, in [Wed Aug 20 01:45:58.473833 2014] [:error] [pid 5035:tid 3038755648] [remote 10.74.104.27:54198] from keystoneclient import discover [Wed Aug 20 01:45:58.473851 2014] [:error] [pid 5035:tid 30
[Yahoo-eng-team] [Bug 1634696] Re: Leading or trailing space in name throws error for new or updated Instances
*** This bug is a duplicate of bug 1519386 *** https://bugs.launchpad.net/bugs/1519386 Reviewed: https://review.openstack.org/388868 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4cfd243ee020d28bb7cc9bbc20a178e9e62b515d Submitter: Jenkins Branch:master commit 4cfd243ee020d28bb7cc9bbc20a178e9e62b515d Author: Ernest Millan Date: Wed Oct 19 11:50:42 2016 -0700 Strip leading or trailing spaces from Instance names during update and create Fixes situation where exception and error is displayed for Instance names which have a leading or trailing space. Change-Id: Ida8d1f01acbaf4820e5fa94d12372a459bba8ed5 Closes-bug: #1634696 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1634696 Title: Leading or trailing space in name throws error for new or updated Instances Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 1. Go to Project -> Instances. 2. Either create a new Instance or edit an existing one. 3. Add either leading or trailing spaces to its "name" and submit the form. 4. An exception will be thrown and an error pop-up will appear. We should strip these out on creation and save. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1634696/+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 1641497] [NEW] horizon missing endpoints that contain %(tenant_id)s
Public bug reported: When logged into the dashboard in Newton with a domain-scoped token only, there are missing endpoints. Under Admin -> System Information -> System -> Services, any endpoint that contains %(tenant_id)s is missing. If a services' endpoints all contain %(tenant_id)s, then that service is not listed at all (e.g. Cinder, Heat). Swift only lists the Admin endpoint, but not the Public and Internal endpoints, as they contain %(tenant_id)s. I'm not sure if this should happen, as I don't have a project-scoped token. ** 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/1641497 Title: horizon missing endpoints that contain %(tenant_id)s Status in OpenStack Dashboard (Horizon): New Bug description: When logged into the dashboard in Newton with a domain-scoped token only, there are missing endpoints. Under Admin -> System Information -> System -> Services, any endpoint that contains %(tenant_id)s is missing. If a services' endpoints all contain %(tenant_id)s, then that service is not listed at all (e.g. Cinder, Heat). Swift only lists the Admin endpoint, but not the Public and Internal endpoints, as they contain %(tenant_id)s. I'm not sure if this should happen, as I don't have a project-scoped token. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1641497/+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 1585515] Re: Paramiko doesn't work with Nova
This affects mitaka, not sure how to make it say that in launchpad ** 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/1585515 Title: Paramiko doesn't work with Nova Status in OpenStack Compute (nova): New Bug description: It looks like Paramiko 2.0.0 again breaks nova which currently has a requirement for 'paramiko>=1.16.0 # LGPL'. nova.tests.unit.api.openstack.compute.test_keypairs.KeypairsTestV210.test_keypair_create_duplicate -- Captured traceback: ~~~ Traceback (most recent call last): File "nova/tests/unit/api/openstack/compute/test_keypairs.py", line 237, in test_keypair_create_duplicate self.controller.create, self.req, body=body) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 485, in assertRaises self.assertThat(our_callable, matcher) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 496, in assertThat mismatch_error = self._matchHelper(matchee, matcher, message, verbose) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 547, in _matchHelper mismatch = matcher.match(matchee) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py", line 108, in match mismatch = self.exception_matcher.match(exc_info) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py", line 62, in match mismatch = matcher.match(matchee) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 475, in match reraise(*matchee) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py", line 101, in match result = matchee() File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 1049, in __call__ return self._callable_object(*self._args, **self._kwargs) File "nova/api/openstack/wsgi.py", line 961, in version_select return func.func(self, *args, **kwargs) File "nova/api/openstack/extensions.py", line 504, in wrapped raise webob.exc.HTTPInternalServerError(explanation=msg) webob.exc.HTTPInternalServerError: Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. Captured pythonlogging: ~~~ 2016-05-25 09:55:14,571 INFO [nova.api.openstack] Loaded extensions: ['os-keypairs', 'servers'] 2016-05-25 09:55:16,314 ERROR [nova.api.openstack.extensions] Unexpected exception in API method Traceback (most recent call last): File "nova/api/openstack/extensions.py", line 478, in wrapped return f(*args, **kwargs) File "nova/api/validation/__init__.py", line 73, in wrapper return func(*args, **kwargs) File "nova/api/openstack/compute/keypairs.py", line 72, in create return self._create(req, body, type=True, user_id=user_id) File "nova/api/openstack/compute/keypairs.py", line 132, in _create context, user_id, name, key_type) File "nova/exception.py", line 110, in wrapped payload) File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 221, in __exit__ self.force_reraise() File "/root/upstream/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line 197, in force_reraise six.reraise(self.type_, self.value, self.tb) File "nova/exception.py", line 89, in wrapped return f(self, context, *args, **kw) File "nova/compute/api.py", line 4040, in create_key_pair user_id, key_type) File "nova/compute/api.py", line 4062, in _generate_key_pair return crypto.generate_key_pair() File "nova/crypto.py", line 152, in generate_key_pair key = generate_key(bits) File "nova/crypto.py", line 144, in generate_key key = paramiko.RSAKey(vals=(rsa.e, rsa.n)) TypeError: __init__() got an unexpected keyword argument 'vals' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1585515/+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 1615582] Re: Error: Unable to create the server. Unexpected API Error.
Reopening this bug, going through an upgrade from liberty -> mitaka and getting this bug ** Changed in: nova Status: Expired => 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/1615582 Title: Error: Unable to create the server. Unexpected API Error. Status in OpenStack Compute (nova): New Bug description: Description === After upgrading fresh OpenStack Liberty installation to Mitaka on Trusty with Juju, I am no longer able to create Nova instances. Steps to reproduce == * Install OpenStack Liberty with Juju from the attached "bundle.yaml" file. * Upgrade OpenStack Liberty to Mitaka by executing the following commands: juju upgrade-charm keystone juju upgrade-charm ceilometer juju upgrade-charm ceilometer-agent juju upgrade-charm ceph juju upgrade-charm ceph-osd juju upgrade-charm cinder juju upgrade-charm glance juju upgrade-charm nova-cloud-controller juju upgrade-charm nova-compute juju upgrade-charm neutron-api juju upgrade-charm neutron-gateway juju upgrade-charm openstack-dashboard juju set-config ceph source="cloud:trusty-mitaka" juju set-config ceph-osd source="cloud:trusty-mitaka" juju set-config keystone openstack-origin="cloud:trusty-mitaka" juju ssh keystone/0 sudo keystone-manage db_sync juju set-config ceilometer openstack-origin="cloud:trusty-mitaka" juju set-config ceilometer-agent openstack-origin="cloud:trusty-mitaka" juju set-config cinder openstack-origin="cloud:trusty-mitaka" juju ssh cinder/0 sudo cinder-manage db sync juju set-config glance openstack-origin="cloud:trusty-mitaka" juju ssh glance/0 sudo glance-manage db_sync juju set-config nova-cloud-controller openstack-origin="cloud:trusty-mitaka" juju ssh nova-cloud-controller/0 sudo nova-manage db sync juju set-config nova-compute openstack-origin="cloud:trusty-mitaka" juju set-config neutron-api openstack-origin="cloud:trusty-mitaka" juju ssh neutron-api/0 sudo neutron-db-manage upgrade heads juju set-config neutron-gateway openstack-origin="cloud:trusty-mitaka" juju set-config openstack-dashboard openstack-origin="cloud:trusty-mitaka" juju ssh ceph/0 sudo reboot juju ssh ceph/1 sudo reboot juju ssh ceph/2 sudo reboot juju ssh ceph-osd/0 sudo service ceph restart juju ssh ceph-osd/1 sudo service ceph restart juju ssh ceph-osd/2 sudo service ceph restart juju ssh keystone/0 sudo reboot juju ssh keystone/1 sudo reboot juju ssh keystone/2 sudo reboot juju ssh ceilometer/0 sudo reboot juju ssh ceilometer/1 sudo reboot juju ssh ceilometer/2 sudo reboot juju ssh ceilometer-agent/0 sudo service ceilometer-agent-compute restart juju ssh ceilometer-agent/1 sudo service ceilometer-agent-compute restart juju ssh ceilometer-agent/2 sudo service ceilometer-agent-compute restart juju ssh cinder/0 sudo reboot juju ssh cinder/1 sudo reboot juju ssh cinder/2 sudo reboot juju ssh glance/0 sudo reboot juju ssh glance/1 sudo reboot juju ssh glance/2 sudo reboot juju ssh nova-cloud-controller/0 sudo reboot juju ssh nova-cloud-controller/1 sudo reboot juju ssh nova-cloud-controller/2 sudo reboot juju ssh nova-compute/0 sudo service nova-compute restart juju ssh nova-compute/1 sudo service nova-compute restart juju ssh nova-compute/2 sudo service nova-compute restart juju ssh neutron-api/0 sudo reboot juju ssh neutron-api/1 sudo reboot juju ssh neutron-api/2 sudo reboot juju ssh neutron-gateway/0 sudo service neutron-dhcp-agent restart juju ssh neutron-gateway/0 sudo service neutron-lbaas-agent restart juju ssh neutron-gateway/0 sudo service neutron-metadata-agent restart juju ssh neutron-gateway/0 sudo service neutron-metering-agent restart juju ssh neutron-gateway/0 sudo service neutron-openvswitch-agent restart juju ssh neutron-gateway/0 sudo service neutron-vpn-agent restart juju ssh nova-compute/0 sudo service neutron-openvswitch-agent restart juju ssh nova-compute/1 sudo service neutron-openvswitch-agent restart juju ssh nova-compute/2 sudo service neutron-openvswitch-agent restart juju ssh openstack-dashboard/0 sudo reboot juju ssh openstack-dashboard/1 sudo reboot juju ssh openstack-dashboard/2 sudo reboot * Attempt to create Nova instance. Expected result === Nova instance being created. Actual result = * Nova instance not being created. * The following error messages being displayed: ** from GUI: Error: Unable to create the server. ** from CLI: 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-c035d518-50c0-4cab-913e-9a5263392a2a) Environment === 1. Exact version of OpenStack you are running. ubuntu@tkurek-maas:~$ juju ssh nova-cloud-controller/
[Yahoo-eng-team] [Bug 1641476] [NEW] multiple attach volume fails
Public bug reported:
We add the scenario to test multiple volume attaching in rally, however it
fails when attaching the volume again.
patch: https://review.openstack.org/#/c/351445/
2016-11-13 06:57:22.923770 | 2016-11-13 06:57:22.923 | 2016-11-13 06:57:22.901
21660 INFO rally.task.runner [-] Task 6886d84b-b604-46b8-b4d0-eb4f06a70c7e |
ITER: 1 START
2016-11-13 06:57:34.034978 | 2016-11-13 06:57:34.034 | 2016-11-13 06:57:34.032
21660 RALLYDEBUG rally.task.utils [-] Waiting for resource
s_rally_6886d84b_HN4l6vy3_0-2. Status changed: BUILD => ACTIVE in 9.22075796127
2016-11-13 06:57:34.163520 | 2016-11-13 06:57:34.162 | 2016-11-13 06:57:34.160
21660 RALLYDEBUG rally.task.utils [-] Waiting for resource
s_rally_6886d84b_HN4l6vy3_0-1. Status changed: BUILD => ACTIVE in 0.127621889114
2016-11-13 06:57:36.627807 | 2016-11-13 06:57:36.627 | 2016-11-13 06:57:36.623
21660 WARNING rally.common.logging [-] 'wait_for' is deprecated in Rally
v0.1.2: Use wait_for_status instead.
2016-11-13 06:57:37.360947 | 2016-11-13 06:57:37.359 | 2016-11-13 06:57:37.357
21660 RALLYDEBUG rally.task.utils [-] Waiting for resource
s_rally_6886d84b_a349YoA7. Status changed: AVAILABLE => ATTACHING in
0.157130002975
2016-11-13 06:57:45.793247 | 2016-11-13 06:57:45.787 | 2016-11-13 06:57:45.784
21660 RALLYDEBUG rally.task.utils [-] Waiting for resource
s_rally_6886d84b_a349YoA7. Status changed: ATTACHING => IN-USE in 8.42752099037
2016-11-13 06:57:46.387422 | 2016-11-13 06:57:46.386 | 2016-11-13 06:57:46.383
21660 RALLYDEBUG rally.task.utils [-] Waiting for resource
s_rally_6886d84b_a349YoA7. Status changed: AVAILABLE => ATTACHING in
0.157689094543
2016-11-13 07:01:07.961952 | 2016-11-13 07:01:07.961 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner [-] Rally tired waiting for Volume
s_rally_6886d84b_a349YoA7:6f92d96a-4d80-4d4b-88bc-d88143c9b20a to become
('IN-USE') current status ATTACHING
2016-11-13 07:01:07.963962 | 2016-11-13 07:01:07.963 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner Traceback (most recent call last):
2016-11-13 07:01:07.965875 | 2016-11-13 07:01:07.965 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner File
"/opt/stack/new/rally/rally/task/runner.py", line 73, in _run_scenario_once
2016-11-13 07:01:07.969149 | 2016-11-13 07:01:07.968 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner getattr(scenario_inst,
method_name)(**scenario_kwargs)
2016-11-13 07:01:07.971123 | 2016-11-13 07:01:07.970 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner File
"/opt/stack/new/rally/rally/plugins/openstack/scenarios/nova/servers.py", line
975, in run
2016-11-13 07:01:07.972949 | 2016-11-13 07:01:07.972 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner attachment = self._attach_volume(server,
volume)
2016-11-13 07:01:07.974537 | 2016-11-13 07:01:07.974 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner File
"/opt/stack/new/rally/rally/task/atomic.py", line 84, in func_atomic_actions
2016-11-13 07:01:07.976387 | 2016-11-13 07:01:07.975 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner f = func(self, *args, **kwargs)
2016-11-13 07:01:07.978897 | 2016-11-13 07:01:07.978 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner File
"/opt/stack/new/rally/rally/plugins/openstack/scenarios/nova/utils.py", line
685, in _attach_volume
2016-11-13 07:01:07.981709 | 2016-11-13 07:01:07.981 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner
CONF.benchmark.nova_server_resize_revert_poll_interval)
2016-11-13 07:01:07.983398 | 2016-11-13 07:01:07.982 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner File
"/opt/stack/new/rally/rally/task/utils.py", line 251, in wait_for_status
2016-11-13 07:01:07.985791 | 2016-11-13 07:01:07.985 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner resource_status=get_status(resource))
2016-11-13 07:01:07.988318 | 2016-11-13 07:01:07.987 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner TimeoutException: Rally tired waiting for Volume
s_rally_6886d84b_a349YoA7:6f92d96a-4d80-4d4b-88bc-d88143c9b20a to become
('IN-USE') current status ATTACHING
2016-11-13 07:01:07.990264 | 2016-11-13 07:01:07.989 | 2016-11-13 07:01:07.958
21660 ERROR rally.task.runner
2016-11-13 07:01:07.992710 | 2016-11-13 07:01:07.992 | 2016-11-13 07:01:07.959
21660 INFO rally.task.runner [-] Task 6886d84b-b604-46b8-b4d0-eb4f06a70c7e |
ITER: 1 END: Error TimeoutException: Rally tired waiting for Volume
s_rally_6886d84b_a349YoA7:6f92d96a-4d80-4d4b-88bc-d88143c9b20a to become
('IN-USE') current status ATTACHING
** 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/1641476
Title:
multiple attach volume fails
Status in OpenStack Compute (nova):
New
Bug description:
We add the scenario to test multiple volume attaching in
[Yahoo-eng-team] [Bug 1578842] Re: gratuitous arping causes exception filling up logs with errors on Ubuntu14.04
Reviewed: https://review.openstack.org/313177 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cc9ce5189db4f3300c38b36dd28a98d64ca7a1fe Submitter: Jenkins Branch:master commit cc9ce5189db4f3300c38b36dd28a98d64ca7a1fe Author: Arun Sriraman Date: Thu May 5 22:18:24 2016 + Changing arping command execute to accept 1 as extra OK code Connecting any network to a router causes l3-agent to send out gratuitous ARP packets that do not require a response. On Ubuntu 14.04 sometimes this command returns 1, which causes it to falsely report arping command failure. This is now added to the extra OK codes. Change-Id: I6299e936d4e4e7fd7497d23224e7abf605a99c15 Closes-bug: #1578842 ** Changed in: neutron Status: In Progress => 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/1578842 Title: gratuitous arping causes exception filling up logs with errors on Ubuntu14.04 Status in neutron: Fix Released Bug description: Connecting an external network to a router causes l3-agent to send out gratuitous arp packets to to the external network gateway IP in order to pre-populate the mac table without expecting a response. Similar behavior when associating floating IPs. Arping utility on CentOS7.2 returns 0 when no response but returns 1 on Ubuntu14.04 which causes an exception and thus a Traceback in the log files. Changing arping command call to not check return code status fixes this issue and that is the proposed fix. Pre-conditions: Router with external network attached. Step-by-step reproduction steps: 1) Create a router 2) Attach an external network as gateway. 3) Attach a tenant network to the router. 4) Associate a Floating IP to a VM instance powered on in that tenant network. Expected output: No errors in logs. Seen on CentOS7.2 Actual output: Traceback in l3 log. Seen on Ubuntu14.04 http://paste.openstack.org/show/496284/ Version: Openstack Liberty (Tag: 7.0.2). Ubuntu14.04. uname -a Linux ubuntu01 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Services running: l3-agent in dvr mode, ovs-agent, dhcp-agent, nova- compute. Perceived Severity: Medium (Causes issues with active monitoring) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1578842/+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 1640782] Re: oslo_config.cfg.NoSuchOptError: no such option profiler in group [DEFAULT] when running an isolated unit test
Reviewed: https://review.openstack.org/396258 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e727b92d3d643384cc2e34d26266cd1e2f3334fe Submitter: Jenkins Branch:master commit e727b92d3d643384cc2e34d26266cd1e2f3334fe Author: Ihar Hrachyshka Date: Tue Nov 8 19:54:04 2016 + Register osprofiler options before setting engine hook The patch makes the module to not assume the options are registered by some other code, that may never be executed, f.e. when it's part of a single test case execution. Change-Id: I7eefb32e6f34d732bda681919b434a96b8ad36da Closes-Bug: #1640782 ** Changed in: neutron Status: In Progress => 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/1640782 Title: oslo_config.cfg.NoSuchOptError: no such option profiler in group [DEFAULT] when running an isolated unit test Status in neutron: Fix Released Bug description: (py27) -bash-4.2$ python -m testtools.run neutron.tests.unit.objects.test_trunk.TrunkObjectTestCase.test_delete_objects Tests running... Policies ['update_rbac_policy:target_tenant'] are part of a cyclical reference. == ERROR: neutron.tests.unit.objects.test_trunk.TrunkObjectTestCase.test_delete_objects -- Traceback (most recent call last): File "neutron/tests/unit/objects/test_base.py", line 544, in setUp mock.patch.object(self.context.session, 'refresh').start() File "neutron/context.py", line 134, in session self._session = db_api.get_session() File "neutron/db/api.py", line 201, in get_session return context_manager.get_legacy_facade().get_session( File "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 667, in get_legacy_facade return self._factory.get_legacy_facade() File "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 261, in get_legacy_facade self._start() File "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 363, in _start engine_args, maker_args) File "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 389, in _setup_for_connection hook(engine) File "neutron/db/api.py", line 38, in set_hook if cfg.CONF.profiler.enabled and cfg.CONF.profiler.trace_sqlalchemy: File "/home/vagrant/git/neutron/.tox/py27/lib/python2.7/site-packages/oslo_config/cfg.py", line 2316, in __getattr__ raise NoSuchOptError(name) oslo_config.cfg.NoSuchOptError: no such option profiler in group [DEFAULT] Ran 1 test in 0.256s FAILED (failures=1) Apparently, the option is not registered. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1640782/+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 1640220] Re: Deprecate SR-IOV 'physical_device_mappings' config option
Reviewed: https://review.openstack.org/395044 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=03b84bc920b5499e1fef23c646268fffa1d859d7 Submitter: Jenkins Branch:master commit 03b84bc920b5499e1fef23c646268fffa1d859d7 Author: Edan David Date: Tue Nov 8 10:30:45 2016 -0500 Deprecate SR-IOV 'physical_device_mappings' config option The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. Closes-Bug: #1640220 DocImpact Change-Id: I5f363347b327212a49a9b78a7164c11d9e457b10 ** Changed in: neutron Status: In Progress => 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/1640220 Title: Deprecate SR-IOV 'physical_device_mappings' config option Status in neutron: Fix Released Bug description: The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1640220/+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 1641433] [NEW] Deprecate SR-IOV 'physical_device_mappings' config option
Public bug reported: https://review.openstack.org/395044 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 03b84bc920b5499e1fef23c646268fffa1d859d7 Author: Edan David Date: Tue Nov 8 10:30:45 2016 -0500 Deprecate SR-IOV 'physical_device_mappings' config option The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. Closes-Bug: #1640220 DocImpact Change-Id: I5f363347b327212a49a9b78a7164c11d9e457b10 ** Affects: neutron Importance: Undecided Status: New ** Tags: doc 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/1641433 Title: Deprecate SR-IOV 'physical_device_mappings' config option Status in neutron: New Bug description: https://review.openstack.org/395044 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 03b84bc920b5499e1fef23c646268fffa1d859d7 Author: Edan David Date: Tue Nov 8 10:30:45 2016 -0500 Deprecate SR-IOV 'physical_device_mappings' config option The device to physnet validation is made in Nova by pci_whitelist config option. Therefore it is redundant to validate it in Neutron with physical_device_mappings config option. Closes-Bug: #1640220 DocImpact Change-Id: I5f363347b327212a49a9b78a7164c11d9e457b10 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1641433/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()
Reviewed: https://review.openstack.org/394877 Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=f765cb9ef92a73f7f15524217d4ba7785996cf38 Submitter: Jenkins Branch:master commit f765cb9ef92a73f7f15524217d4ba7785996cf38 Author: bailinzhang Date: Tue Nov 8 18:07:35 2016 +0800 Replaces uuid.uuid4 with uuidutils.generate_uuid() Change-Id: I81b4c4a4c57b9e4bbff48b055105148734879d4c Closes-Bug: #1082248 ** Changed in: networking-ovn Status: In Progress => 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/1082248 Title: Use uuidutils instead of uuid.uuid4() Status in Cinder: In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in kuryr: In Progress Status in kuryr-libnetwork: In Progress Status in Magnum: New Status in Mistral: Fix Released Status in Murano: In Progress Status in networking-ovn: Fix Released Status in networking-sfc: In Progress Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in Sahara: Fix Released Status in senlin: Fix Released Status in tacker: In Progress Bug description: Openstack common has a wrapper for generating uuids. We should only use that function when generating uuids for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1082248/+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 1400966] Re: [OSSA-2014-041] Glance allows users to download and delete any file in glance-api server (CVE-2014-9493)
invalid Bug ID mentioned in commit ** Changed in: juniperopenstack/trunk Status: In Progress => Invalid ** Changed in: juniperopenstack/trunk Assignee: Grant Murphy (gmurphy) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1400966 Title: [OSSA-2014-041] Glance allows users to download and delete any file in glance-api server (CVE-2014-9493) Status in Glance: Fix Released Status in Glance icehouse series: Fix Released Status in Glance juno series: Fix Released Status in Juniper Openstack: Invalid Status in Juniper Openstack trunk series: Invalid Status in openstack-ansible: Fix Released Status in openstack-ansible icehouse series: Fix Released Status in openstack-ansible juno series: Fix Released Status in OpenStack Security Advisory: Fix Released Bug description: Updating image-location by update images API users can download any file for which glance-api has read permission. And the file for which glance-api has write permission will be deleted when users delete the image. For example: When users specify '/etc/passwd' as locations value of an image user can get the file by image download. When locations of an image is set with 'file:///path/to/glance- api.conf' the conf will be deleted when users delete the image. How to recreate the bug: download files: - set show_multiple_locations True in glance-api.conf - create a new image - set locations of the image's property a path you want to get such as file:///etc/passwd. - download the image delete files: - set show_multiple_locations True in glance-api.conf - create a new image - set locations of the image's property a path you want to delete such as file:///path/to/glance-api.conf - delete the image I found this bug in 2014.2 (742c898956d655affa7351505c8a3a5c72881eae). What a big A RE RE!! To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1400966/+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 1641412] [Review update] master
Review in progress for https://review.opencontrail.org/26021 Submitter: Ganesha HV (ganesh...@juniper.net) ** Also affects: juniperopenstack/trunk Importance: Undecided Status: New ** Also affects: juniperopenstack/trunk Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1641412 Title: [3.0.2.0-51~kilo]Need to add image to glance thru heat Status in Glance: New Status in Juniper Openstack: In Progress Status in Juniper Openstack trunk series: In Progress Bug description: Need support to add image to glance thru heat. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1641412/+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 1641413] [NEW] Unnecessary db traffic when constructing instance object from db info
Public bug reported: During construction of an instance object from db info, a call to _from_db_object() is made. In many situations this results in one or more unnecessary db calls due to the way instance extras are handled. This occurs when the following two conditions apply; (1) the 'expected_attrs' parameter contains one of the affected instance_extras fields (see below) and (2) the corresponding value in the provided db_instance data either does not exist or else contains None. The affected instance extras fields are: - numa_topology - pci_requests - device_metadata - vcpu_model ** Affects: nova Importance: Medium Assignee: Hans Lindgren (hanlind) Status: New ** Tags: unified-objects -- 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/1641413 Title: Unnecessary db traffic when constructing instance object from db info Status in OpenStack Compute (nova): New Bug description: During construction of an instance object from db info, a call to _from_db_object() is made. In many situations this results in one or more unnecessary db calls due to the way instance extras are handled. This occurs when the following two conditions apply; (1) the 'expected_attrs' parameter contains one of the affected instance_extras fields (see below) and (2) the corresponding value in the provided db_instance data either does not exist or else contains None. The affected instance extras fields are: - numa_topology - pci_requests - device_metadata - vcpu_model To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1641413/+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 1641412] [NEW] [3.0.2.0-51~kilo]Need to add image to glance thru heat
Public bug reported: Need support to add image to glance thru heat. ** Affects: glance Importance: Undecided Status: New ** Affects: juniperopenstack Importance: Undecided Status: In Progress ** Affects: juniperopenstack/trunk Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1641412 Title: [3.0.2.0-51~kilo]Need to add image to glance thru heat Status in Glance: New Status in Juniper Openstack: In Progress Status in Juniper Openstack trunk series: In Progress Bug description: Need support to add image to glance thru heat. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1641412/+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 1640059] Re: Placeholder not set on new glance image upload
Reviewed: https://review.openstack.org/394805 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=016724d4ed2b9de2a843e81b450f9e99650fbfa2 Submitter: Jenkins Branch:master commit 016724d4ed2b9de2a843e81b450f9e99650fbfa2 Author: Maxime Guyot Date: Tue Nov 8 08:09:53 2016 +0100 Set the placeholder attribute in forms.py Closes-Bug: #1640059 Change-Id: I4428d4c6ef7c198b480595bda8e12d8794b25e8d ** Changed in: horizon Status: In Progress => Fix Released -- 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/1640059 Title: Placeholder not set on new glance image upload Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Back in Juno the "Create An Image" form used to have a placeholder attribute on the "Image location" field. It is not there anymore in trunk (probably since Kilo) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1640059/+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 1641383] [NEW] Uploading OVA to Glance via Horizon Fails
Public bug reported: If a user wishes to upload an image to Glance that is an OVA file, the import fails because the disk_format gets marked as "bare" and the container_format is not taken into account. I've checked the dashboard for images and found this problem can be very easily fixed by checking if the user specified ova in the form and updating these 2 settings. dashboards/project/images/images/forms.py after line 63 elif disk_format == 'ova': # The ova format requires glance to set the disk format to vmdk and # the container format to ova in order for glance to accept the image # and to allow successful launch of the image. OVA does not support # a container format of bare. container_format = 'ova' disk_format = 'vmdk' Upon adding this change, OVAs can be added via the UI without error, and Glance can launch the OVA as expected. This only impacts single-disk OVA. Can someone verify this for me so we know on our side this is the correct action? I'm not totally familiar with contributing to the project, so I'm working on that internally as well. ** 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/1641383 Title: Uploading OVA to Glance via Horizon Fails Status in OpenStack Dashboard (Horizon): New Bug description: If a user wishes to upload an image to Glance that is an OVA file, the import fails because the disk_format gets marked as "bare" and the container_format is not taken into account. I've checked the dashboard for images and found this problem can be very easily fixed by checking if the user specified ova in the form and updating these 2 settings. dashboards/project/images/images/forms.py after line 63 elif disk_format == 'ova': # The ova format requires glance to set the disk format to vmdk and # the container format to ova in order for glance to accept the image # and to allow successful launch of the image. OVA does not support # a container format of bare. container_format = 'ova' disk_format = 'vmdk' Upon adding this change, OVAs can be added via the UI without error, and Glance can launch the OVA as expected. This only impacts single- disk OVA. Can someone verify this for me so we know on our side this is the correct action? I'm not totally familiar with contributing to the project, so I'm working on that internally as well. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1641383/+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
