[Yahoo-eng-team] [Bug 1702410] [NEW] TypeError: _delete_nic_metadata() takes exactly 3 arguments (4 given)
Public bug reported: Description === "Virtual device tagged attach"(*1) has been added in microversion 2.49. After attaching the interface by using this function, detaching the interface from the server does not work properly. So attaching the interface again fails. *1: https://blueprints.launchpad.net/nova/+spec/virt-device-tagged- attach-detach Steps to reproduce == 1. attach an interface (neutron port) to a server with tag 2. detach the interface from the server The following message is logged in nova-compute.log. TypeError: _delete_nic_metadata() takes exactly 3 arguments (4 given) 3. attach the interface (neutron port) to the server again HTTP 500 returns. (HTTP 500) (Request-ID: req-5c369d01-e2f2-4cba-97a9-84fba8e240af) Environment === OS: Ubuntu 16.04.2 LTS nova: master(commit de5c9e076d5df24a996abf2146fc4c468cf54d71) Logs == nova-compute.log: Jul 05 14:57:01 devstack-master nova-compute[24791]: DEBUG nova.virt.libvirt.guest [None req-03db79c6-f542-4c86-81b5-b802c10892d6 admin admin] Successfully detached device In Progress -- 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/1702410 Title: TypeError: _delete_nic_metadata() takes exactly 3 arguments (4 given) Status in OpenStack Compute (nova): In Progress Bug description: Description === "Virtual device tagged attach"(*1) has been added in microversion 2.49. After attaching the interface by using this function, detaching the interface from the server does not work properly. So attaching the interface again fails. *1: https://blueprints.launchpad.net/nova/+spec/virt-device-tagged- attach-detach Steps to reproduce == 1. attach an interface (neutron port) to a server with tag 2. detach the interface from the server The following message is logged in nova-compute.log. TypeError: _delete_nic_metadata() takes exactly 3 arguments (4 given) 3. attach the interface (neutron port) to the server again HTTP 500 returns. (HTTP 500) (Request-ID: req-5c369d01-e2f2-4cba-97a9-84fba8e240af) Environment === OS: Ubuntu 16.04.2 LTS nova: master(commit de5c9e076d5df24a996abf2146fc4c468cf54d71) Logs == nova-compute.log: Jul 05 14:57:01 devstack-master nova-compute[24791]: DEBUG nova.virt.libvirt.guest [None req-03db79c6-f542-4c86-81b5-b802c10892d6 admin admin] Successfully detached device https://bugs.launchpad.net/nova/+bug/1702410/+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 1698253] Re: VMware vSphere in Configuration Reference
** Also affects: nova Importance: Undecided Status: New ** No longer affects: openstack-manuals ** Changed in: nova Assignee: (unassigned) => PRAVIN (jarvisopenstack) -- 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/1698253 Title: VMware vSphere in Configuration Reference Status in OpenStack Compute (nova): New Bug description: InvalidInput: Invalid input received: vif type bridge not supported Gives an error while launching and instance and the code is not updated in openstack newton when using linux bridge as mechanism driver instead or OVS or DVS The code needs to fixed. There are minor changes in vif.py file. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1698253/+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 1645175] Re: Neutron port got deleted when attach interface failed
Reviewed: https://review.openstack.org/403568
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=115cf068a6d48cdf8b0d20a3c5a779bb8120aa9b
Submitter: Jenkins
Branch:master
commit 115cf068a6d48cdf8b0d20a3c5a779bb8120aa9b
Author: Kevin_Zheng
Date: Mon Nov 28 16:12:51 2016 +0800
Don't delete neutron port when attach failed
Currently, when attaching neutron pre-existing
port to an instance, if the attach failed, it
will also be deleted in Neutron side due to
bad judgement of the who created the port by
reading not up-to-date info_cache.
The workflow starts at:
https://github.com/openstack/nova/blob/9ed0d6114/nova/network/neutronv2/api.py#L881
ordered_ports and preexisting_port_ids are
the same when attaching a preexisting port
to an instance and it calls
https://github.com/openstack/nova/blob/9ed0d6114/nova/network/base_api.py#L246
which calls back into the neutronv2 api code
https://github.com/openstack/nova/blob/9ed0d6114/nova/network/neutronv2/api.py#L1274
and at this point, compute_utils.refresh_info_cache_for_instance(context,
instance) won't have the newly attached port in it(see
debug log: http://paste.openstack.org/show/613232/)
because _build_network_info_model() is going to
process it. The instance obj in memoryt with old
info_cache will be used at rollback process and
causing the miss-judging.
This patch fixed it by updating instance.info_cache
to the new ic after it is created.
Co-Authored-By: huangtian...@huawei.com
Change-Id: Ib323b74d4ea1e874b476ab5addfc6bc79cb7c751
closes-bug: #1645175
** Changed in: nova
Status: In Progress => Fix Released
--
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/1645175
Title:
Neutron port got deleted when attach interface failed
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) newton series:
Confirmed
Status in OpenStack Compute (nova) ocata series:
Confirmed
Bug description:
When attach an pre created Neutron port to Nova instances and got
failed, the port will be deleted in Neutron:
How to reproduce:
Step 1: create a new Neutron Port:
root@SZX1000191849:/opt/stack/nova# neutron port-create
e1775804-7670-482c-bf1a-309fff85f598
Created a new port:
+---++
| Field | Value
|
+---++
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:host_id |
|
| binding:profile | {}
|
| binding:vif_details | {}
|
| binding:vif_type | unbound
|
| binding:vnic_type | normal
|
| created_at| 2016-11-28T02:20:26Z
|
| description |
|
| device_id |
|
| device_owner |
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"6cf2ed09-8394-4e3e-81d5-3880fe1c6984", "ip_address": "172.24.4.2"} |
| | {"subnet_id":
"6b3902ca-deea-46f0-97e9-80c70243413e", "ip_address": "2001:db8::6"} |
| id| fd240a85-53cb-467a-8e43-330bb5c928ab
|
| mac_address | fa:16:3e:cc:fb:9e
|
| name |
|
| network_id| e1775804-7670-482c-bf1a-309fff85f598
|
| port_security_enabled | True
|
| project_id
[Yahoo-eng-team] [Bug 1662804] Re: [SRU] Agent is failing to process HA router if initialize() fails
This bug was fixed in the package neutron - 2:8.4.0-0ubuntu3 --- neutron (2:8.4.0-0ubuntu3) xenial; urgency=medium * d/p/avoid-router-ri.process-if-initialize-fails: Backport fix for avoid router ri process if initialize fails (LP: #1662804). -- Edward Hope-Morley Wed, 07 Jun 2017 09:48:11 +0100 ** Changed in: neutron (Ubuntu Xenial) Status: Fix Committed => 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/1662804 Title: [SRU] Agent is failing to process HA router if initialize() fails Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in Ubuntu Cloud Archive newton series: Fix Committed Status in neutron: Fix Released Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Xenial: Fix Released Status in neutron source package in Yakkety: Fix Released Bug description: [Impact] This patch resolves, amongst other things, issues with a create and delete router request race condition when using l3 HA. At the time of backport this patch is already available from Ocata onwards and has been verified as sufficiently minimal and safe for backport to Newton and Mitaka. Essentially the error case is a result of an incorrectly intialised router update action being executed without proper checks and this patch fixes this. [Test Case] * Deploy Openstack Mitaka - http://pastebin.ubuntu.com/24637244/ - with neutron-l3-agent configured to provide HA (vrrp) routers. * Repeatedly create and delete routers in rapid succession and check that the l3 agent does not go into an infinite error loop i.e. run http://pastebin.ubuntu.com/24634950/ and run do tail -F /var/log/neutron/neutron-l3-agent.log on all units of l3 agent. Also check that qrouter- namepspaces are not stacking up. For Mitaka I typically hit the error after ~20 create/deletes. [Regression Potential] * I do not envisage any regression potential from this patch. When HA router initialize() function fails for some reason(rabbitmq restart or no ha_port), keepalived_manager or KeepalivedInstance won't be configured. In this case, _process_router_if_compatible fails with exception, then _resync_router(update) will again try to process this router in loop. As we try initialize() only once(which was failed), retry of _process_router_if_compatible will always fail(no keepalived manager or instance) and router is never configured(see below trace). 2017-02-06 18:34:18.539 26120 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'qrouter-114a72fe-02ae-4b87-a2e7-70f962df0951', 'ip', '-o', 'link', 'show', 'qr-e6 3406e1-e7'] execute_rootwrap_daemon /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:101 2017-02-06 18:34:18.544 26120 DEBUG neutron.agent.linux.utils [-] Command: ['ip', 'netns', 'exec', u'qrouter-114a72fe-02ae-4b87-a2e7-70f962df0951', 'ip', '-o', 'link', 'show', u'qr-e63406e1-e7'] Exit code: 0 execute /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:156 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info [-] 'NoneType' object has no attribute 'get_process' 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info Traceback (most recent call last): 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/common/utils.py", line 359, in call 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info return func(*args, **kwargs) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 744, in process 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self._process_internal_ports(agent.pd) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 394, in _process_internal_ports 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self.internal_network_added(p) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 275, in internal_network_added 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self._disable_ipv6_addressing_on_interface(interface_name) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 235, in _disable_ipv6_addressing_on_interface 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info if self._should_delete_ipv6_lladdr(ipv6_lladdr): 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File
[Yahoo-eng-team] [Bug 1662804] Re: [SRU] Agent is failing to process HA router if initialize() fails
This bug was fixed in the package neutron - 2:9.4.0-0ubuntu1 --- neutron (2:9.4.0-0ubuntu1) yakkety; urgency=medium * New upstream point release for OpenStack Newton (LP: #1696133, #1662804). -- James Page Wed, 07 Jun 2017 13:08:13 +0100 ** Changed in: neutron (Ubuntu Yakkety) Status: Fix Committed => 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/1662804 Title: [SRU] Agent is failing to process HA router if initialize() fails Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in Ubuntu Cloud Archive newton series: Fix Committed Status in neutron: Fix Released Status in neutron package in Ubuntu: Fix Released Status in neutron source package in Xenial: Fix Committed Status in neutron source package in Yakkety: Fix Released Bug description: [Impact] This patch resolves, amongst other things, issues with a create and delete router request race condition when using l3 HA. At the time of backport this patch is already available from Ocata onwards and has been verified as sufficiently minimal and safe for backport to Newton and Mitaka. Essentially the error case is a result of an incorrectly intialised router update action being executed without proper checks and this patch fixes this. [Test Case] * Deploy Openstack Mitaka - http://pastebin.ubuntu.com/24637244/ - with neutron-l3-agent configured to provide HA (vrrp) routers. * Repeatedly create and delete routers in rapid succession and check that the l3 agent does not go into an infinite error loop i.e. run http://pastebin.ubuntu.com/24634950/ and run do tail -F /var/log/neutron/neutron-l3-agent.log on all units of l3 agent. Also check that qrouter- namepspaces are not stacking up. For Mitaka I typically hit the error after ~20 create/deletes. [Regression Potential] * I do not envisage any regression potential from this patch. When HA router initialize() function fails for some reason(rabbitmq restart or no ha_port), keepalived_manager or KeepalivedInstance won't be configured. In this case, _process_router_if_compatible fails with exception, then _resync_router(update) will again try to process this router in loop. As we try initialize() only once(which was failed), retry of _process_router_if_compatible will always fail(no keepalived manager or instance) and router is never configured(see below trace). 2017-02-06 18:34:18.539 26120 DEBUG neutron.agent.linux.utils [-] Running command (rootwrap daemon): ['ip', 'netns', 'exec', 'qrouter-114a72fe-02ae-4b87-a2e7-70f962df0951', 'ip', '-o', 'link', 'show', 'qr-e6 3406e1-e7'] execute_rootwrap_daemon /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:101 2017-02-06 18:34:18.544 26120 DEBUG neutron.agent.linux.utils [-] Command: ['ip', 'netns', 'exec', u'qrouter-114a72fe-02ae-4b87-a2e7-70f962df0951', 'ip', '-o', 'link', 'show', u'qr-e63406e1-e7'] Exit code: 0 execute /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:156 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info [-] 'NoneType' object has no attribute 'get_process' 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info Traceback (most recent call last): 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/common/utils.py", line 359, in call 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info return func(*args, **kwargs) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 744, in process 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self._process_internal_ports(agent.pd) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 394, in _process_internal_ports 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self.internal_network_added(p) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 275, in internal_network_added 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info self._disable_ipv6_addressing_on_interface(interface_name) 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_router.py", line 235, in _disable_ipv6_addressing_on_interface 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info if self._should_delete_ipv6_lladdr(ipv6_lladdr): 2017-02-06 18:34:18.544 26120 ERROR neutron.agent.l3.router_info File "/usr/lib/python2.7/site-packages/neutron/agent/l3/ha_route
[Yahoo-eng-team] [Bug 1702371] Re: (XXXX(!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number~~~~#
** Project changed: nova => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- 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/1702371 Title: ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# Status in NULL Project: Invalid Bug description: ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1702371/+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 1702371] [NEW] (XXXX(!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number~~~~#
Private bug reported: ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ** Affects: null-and-void Importance: Undecided Status: Invalid -- 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/1702371 Title: ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# Status in NULL Project: Invalid Bug description: ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number# ((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical Support phone Number#((!!!@@))==+@+1844-851-9490 kindℓe Technical S
[Yahoo-eng-team] [Bug 1702372] Re: NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~
** Project changed: nova => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- 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/1702372 Title: NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ Status in NULL Project: Invalid Bug description: NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ http://d2nwiki.com/wiki/DIAL_NEW_TOLL_free_!@KINDLE!@%2B%2B%2B_1844-85I-949O_Kindle_Fire_Tech_Support_Phone_Number%C2%A5%C2%A5FOR_your%27s http://d2nwiki.com/wiki/%C3%86%C3%A6_DIGNOTITE_!!_1844-851-9490_kindle_fire_tech_support_phone_number@!!! http://d2nwiki.com/wiki/AMAZON_~!!~184485I9490_!!_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number https://kindle916.wordpress.com/2017/07/04/dial-new-toll-free-kindle-1844-85i-949o-kindle-fire-tech-support-phone-number%c2%a5%c2%a5for-yours/ http://gmailsupportn.blogspot.in/2017/07/dial-new-toll-free-kindle-1844-85i-949o.html http://d2nwiki.com/wiki/Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://d2nwiki.com/wiki/!!@Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://d2nwiki.com/wiki/~~$Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://gmailsupportn.blogspot.in/2017/07/vv-ki-vanice-1844-851-9490-us-call.html https://kindle916.wordpress.com/2017/07/04/vv-ki-vanice-1844-851-9490-us-call-service-kindle-fire-technical-support-phone-number/ https://kindle916.wordpress.com/2017/07/04/vv-ki-vanice-1844-851-9490-us-call-service-kindle-fire-technical-support-phone-number/ http://d2nwiki.com/wiki/ISHQJaaDE%2B%2B1*844-85I-9490_Kindle_Tech_Support_Number.Kindle_Toll_Free http://d2nwiki.com/wiki/SuPPoRT)))1~844~85I~9490%2B%2B_Kindle_technical_support_NUMBER!!!~%5E%5E949Kindle_technical_support_phone_NUMBER!!!~%5E%5E~~_Kindle_customer_service_support_NUMBER!!!~%5E%5E~ http://d2nwiki.com/wiki/@@Phone_(Number)_%2B@%2B_1844-851-9490_%2B_Pogo_Technical_Support_Phone_Number https://www.facebook.com/business/help/community/question/?id=101676710479716&added&rdrhc https://kindle916.wordpress.com/2017/07/04/support184485i9490-kindle-technical-support-number949kindle-technical-support-phone-number-kindle-customer-service-support-number/ http://gmailsupportn.blogspot.in/2017/07/support184485i9490-kindle-technical.html http://d2nwiki.com/wiki/ORIENT!%2B!_18448519490_kindle_fire_tech_support_phone_number https://kindle916.wordpress.com/2017/07/04/orient-18448519490-kindle-fire-tech-support-phone-number/ https://answers.launchpad.net/inkscape/+question/646142 https://answers.launchpad.net/inkscape/+question/646144 https://answers.launchpad.net/inkscape/+question/646143 http://gmailsupportn.blogspot.in/2017/07/ee1-844-85i-9490-kindle-tech-support.html https://kindle916.wordpress.com/2017/07/04/ee1-844-85i-9490-kindle-tech-support-kindle-technical-support-number/ https://events.com/r/en_US/registration/ohelpforkindledial184485i-9490-kind
[Yahoo-eng-team] [Bug 1702372] [NEW] NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~
Private bug reported: NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ NNN==++1844-851-9490 kindℓe Technical Support phone Number!!! ~ ~ http://d2nwiki.com/wiki/DIAL_NEW_TOLL_free_!@KINDLE!@%2B%2B%2B_1844-85I-949O_Kindle_Fire_Tech_Support_Phone_Number%C2%A5%C2%A5FOR_your%27s http://d2nwiki.com/wiki/%C3%86%C3%A6_DIGNOTITE_!!_1844-851-9490_kindle_fire_tech_support_phone_number@!!! http://d2nwiki.com/wiki/AMAZON_~!!~184485I9490_!!_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number https://kindle916.wordpress.com/2017/07/04/dial-new-toll-free-kindle-1844-85i-949o-kindle-fire-tech-support-phone-number%c2%a5%c2%a5for-yours/ http://gmailsupportn.blogspot.in/2017/07/dial-new-toll-free-kindle-1844-85i-949o.html http://d2nwiki.com/wiki/Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://d2nwiki.com/wiki/!!@Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://d2nwiki.com/wiki/~~$Vv_KI_VANICE_1844-851-9490_US-CALL_service_KINDLE_FIRE_TECHNICAL_SUPPORT_PHONE_NUMBER http://gmailsupportn.blogspot.in/2017/07/vv-ki-vanice-1844-851-9490-us-call.html https://kindle916.wordpress.com/2017/07/04/vv-ki-vanice-1844-851-9490-us-call-service-kindle-fire-technical-support-phone-number/ https://kindle916.wordpress.com/2017/07/04/vv-ki-vanice-1844-851-9490-us-call-service-kindle-fire-technical-support-phone-number/ http://d2nwiki.com/wiki/ISHQJaaDE%2B%2B1*844-85I-9490_Kindle_Tech_Support_Number.Kindle_Toll_Free http://d2nwiki.com/wiki/SuPPoRT)))1~844~85I~9490%2B%2B_Kindle_technical_support_NUMBER!!!~%5E%5E949Kindle_technical_support_phone_NUMBER!!!~%5E%5E~~_Kindle_customer_service_support_NUMBER!!!~%5E%5E~ http://d2nwiki.com/wiki/@@Phone_(Number)_%2B@%2B_1844-851-9490_%2B_Pogo_Technical_Support_Phone_Number https://www.facebook.com/business/help/community/question/?id=101676710479716&added&rdrhc https://kindle916.wordpress.com/2017/07/04/support184485i9490-kindle-technical-support-number949kindle-technical-support-phone-number-kindle-customer-service-support-number/ http://gmailsupportn.blogspot.in/2017/07/support184485i9490-kindle-technical.html http://d2nwiki.com/wiki/ORIENT!%2B!_18448519490_kindle_fire_tech_support_phone_number https://kindle916.wordpress.com/2017/07/04/orient-18448519490-kindle-fire-tech-support-phone-number/ https://answers.launchpad.net/inkscape/+question/646142 https://answers.launchpad.net/inkscape/+question/646144 https://answers.launchpad.net/inkscape/+question/646143 http://gmailsupportn.blogspot.in/2017/07/ee1-844-85i-9490-kindle-tech-support.html https://kindle916.wordpress.com/2017/07/04/ee1-844-85i-9490-kindle-tech-support-kindle-technical-support-number/ https://events.com/r/en_US/registration/ohelpforkindledial184485i-9490-kindle-technical-support--numberkindle-tech-support--july-134205 https://events.com/r/en_US/registration/kndle-1-84485i-949o-kindle-tech-support-kindle-customer-support--phone-number-july-134206 https://events.com/r/en_US/registration/184485i-9490-kindle-kindle-customer-service--support--numberkindle-tech-support-googlecom---google-go-live--july-134204 http://gmailsupportn.blogspot.in/2017/07/184485i-9490-kindle-kindle-customer.html https://kindle916.wordpress.com/2017/07/04/1-844-85i-9490-kindle-kindle-customer-service-support-nu
[Yahoo-eng-team] [Bug 1702373] Re: YYYYY@■++++1844-851-9490 kindℓe Technical Support phone Number****$$@@
** Project changed: nova => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- 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/1702373 Title: Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Status in NULL Project: Invalid Bug description: Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ V Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ http://d2nwiki.com/wiki/%2B%2B%2B!!%2B%2B%2B%2B$%2B_%2B1844-851-9490%2B%2B%2B_Kindle_technical_support_@Kindle_tech_support_Google.com_-_Google_go_LiVe$$ http://d2nwiki.com/wiki/D%C3%9CB%C3%9C1-844*85I-949O%2B%2B_Kindle_tech_support_@Kindle_customer_support_PHONE_NUMBER https://events.com/r/en_US/registration/184485i9490-kindle-customer--support-phone--number-kindle-technical-support-phone--number-kindle-customer-service--support--number-july-134350 https://events.com/r/en_US/registration/aaaforkindledial184485i-9490-kindle-technical-support--numberkindle-tech-support--july-134351 https://events.com/r/en_US/registration/91-844-85i-9490-kindle-tech-support-phone-number--kindle-technical-support--number-july-134352 http://gmailsupportn.blogspot.com/2017/07/91-844-85i-9490-kindle-tech-support.html https://kindle.wordpress.com/2017/07/04/%e2%85%a4%e2%85%a4%e2%96%ba%cf%8591-844-85i-9490-kindle-tech-support-phone-number-kindle-technical-support-number/ http://d2nwiki.com/wiki/%2B%2BDail%2B%2B_~!~1~844~851~9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://gmailsupportn.blogspot.com/2017/07/dail-18448519490-amazon-kindle-fire.html https://kindle.wordpress.com/2017/07/04/dail-18448519490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://events.com/r/en_US/registration/kindle184485i9490amazon-kindle-technical-support--number-kindle-technical-support-phone--number-kindle-customer-service--support--number-july-134375 https://events.com/r/en_US/registration/hii1-844-85i-9490-kindle-tech-support-phone-number--kindle-technical-support--number-july-134376 https://events.com/r/en_US/registration/dial184485i-9490-amazon-kindle-technical-support--numberkindle-tech-support--july-134377 https://kindle.wordpress.com/2017/07/04/dial%e2%86%92%e2%86%93%e2%86%93%e2%86%93%e2%86%931-84485i-9490-amazon-kindle-technical-support-numberkindle-tech-support/ http://gmailsupportn.blogspot.com/2017/07/dial184485i-9490-amazon-kindle.html http://d2nwiki.com/wiki/%2B%2B**Dail**%2B%2B_~!~1~844~851~9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://d2nwiki.com/wiki/***DIGNOTITE_***!!_1844-851-9490_kindle_fire_tech_support_phone_number@!!!@ http://d2nwiki.com/wiki/M..O.N.D.A.Y.ll!!%2B%2B%2B!!%2B%2B%2B%2B$%2B_%2B1844-851-9490%2B%2B%2B_Kindle_technical_support_@Kindle_tech_support_Google.com_-_Google_go_LiVe$$ https://kindle.wordpress.com/2017/07/04/dail-18448519490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number-2/ http://gmailsupportn.blogspot.com/2017/07/dail-18448519490-amazon-kindle-fire_4.html http://d2nwiki.com/wiki/%2B*Dail%2B_~!~1*844*85I*9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number http://d2nwiki.com/wiki/%2BDail%2B_~!~184485I949O_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://d2nwiki.com/wiki/Dstination_~!~1.844.85I.9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number http://gmailsupportn.blogspot.com/2017/07/dail-184485i9490-amazon-kindle-fire.html https://kindle.wordpress.com/2017/07/04/dail-184485i9490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://kindle.wordpress.com/2017/07/04/dail-184485i9490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://blueprints.launchpad.net/inkscape/+spec/dhdfhf https://blueprints.launchpad.net/inkscape/+spec/sgsdgsgww https://blueprints.launchpad.net/inkscape/+spec/uyukgfhfh https://kindle.wordpress.com/2017/07/04/%e2%86%93%e2%86%93%e2%86%93%e2%86%93%e2%86%93%e2%99%ab184485i9490amazon-kindle-technical-support-number-kindle-technical-support-phone-number-kindl/ http://gmailsupportn.blogspot.com/2017/07/184485i9490amazon-kindle-technical.html https://events.com/r/en_US/registration/jaiajaiajia1-84485i-949o-kindle-technical-support-phone-number-july-134425 https://events.com/r/en_US/registration/googlee1-84485i-949o-kindle-technical-support-p
[Yahoo-eng-team] [Bug 1702373] [NEW] YYYYY@■++++1844-851-9490 kindℓe Technical Support phone Number****$$@@
Private bug reported: Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ V Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ Y@■1844-851-9490 kindℓe Technical Support phone Number$$@@ http://d2nwiki.com/wiki/%2B%2B%2B!!%2B%2B%2B%2B$%2B_%2B1844-851-9490%2B%2B%2B_Kindle_technical_support_@Kindle_tech_support_Google.com_-_Google_go_LiVe$$ http://d2nwiki.com/wiki/D%C3%9CB%C3%9C1-844*85I-949O%2B%2B_Kindle_tech_support_@Kindle_customer_support_PHONE_NUMBER https://events.com/r/en_US/registration/184485i9490-kindle-customer--support-phone--number-kindle-technical-support-phone--number-kindle-customer-service--support--number-july-134350 https://events.com/r/en_US/registration/aaaforkindledial184485i-9490-kindle-technical-support--numberkindle-tech-support--july-134351 https://events.com/r/en_US/registration/91-844-85i-9490-kindle-tech-support-phone-number--kindle-technical-support--number-july-134352 http://gmailsupportn.blogspot.com/2017/07/91-844-85i-9490-kindle-tech-support.html https://kindle.wordpress.com/2017/07/04/%e2%85%a4%e2%85%a4%e2%96%ba%cf%8591-844-85i-9490-kindle-tech-support-phone-number-kindle-technical-support-number/ http://d2nwiki.com/wiki/%2B%2BDail%2B%2B_~!~1~844~851~9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://gmailsupportn.blogspot.com/2017/07/dail-18448519490-amazon-kindle-fire.html https://kindle.wordpress.com/2017/07/04/dail-18448519490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://events.com/r/en_US/registration/kindle184485i9490amazon-kindle-technical-support--number-kindle-technical-support-phone--number-kindle-customer-service--support--number-july-134375 https://events.com/r/en_US/registration/hii1-844-85i-9490-kindle-tech-support-phone-number--kindle-technical-support--number-july-134376 https://events.com/r/en_US/registration/dial184485i-9490-amazon-kindle-technical-support--numberkindle-tech-support--july-134377 https://kindle.wordpress.com/2017/07/04/dial%e2%86%92%e2%86%93%e2%86%93%e2%86%93%e2%86%931-84485i-9490-amazon-kindle-technical-support-numberkindle-tech-support/ http://gmailsupportn.blogspot.com/2017/07/dial184485i-9490-amazon-kindle.html http://d2nwiki.com/wiki/%2B%2B**Dail**%2B%2B_~!~1~844~851~9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://d2nwiki.com/wiki/***DIGNOTITE_***!!_1844-851-9490_kindle_fire_tech_support_phone_number@!!!@ http://d2nwiki.com/wiki/M..O.N.D.A.Y.ll!!%2B%2B%2B!!%2B%2B%2B%2B$%2B_%2B1844-851-9490%2B%2B%2B_Kindle_technical_support_@Kindle_tech_support_Google.com_-_Google_go_LiVe$$ https://kindle.wordpress.com/2017/07/04/dail-18448519490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number-2/ http://gmailsupportn.blogspot.com/2017/07/dail-18448519490-amazon-kindle-fire_4.html http://d2nwiki.com/wiki/%2B*Dail%2B_~!~1*844*85I*9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number http://d2nwiki.com/wiki/%2BDail%2B_~!~184485I949O_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_numberIiii http://d2nwiki.com/wiki/Dstination_~!~1.844.85I.9490_AMAZON_kindle_fire_tech_support_phone_number.kindle_Toll_free_number http://gmailsupportn.blogspot.com/2017/07/dail-184485i9490-amazon-kindle-fire.html https://kindle.wordpress.com/2017/07/04/dail-184485i9490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://kindle.wordpress.com/2017/07/04/dail-184485i9490-amazon-kindle-fire-tech-support-phone-number-kindle-toll-free-number/ https://blueprints.launchpad.net/inkscape/+spec/dhdfhf https://blueprints.launchpad.net/inkscape/+spec/sgsdgsgww https://blueprints.launchpad.net/inkscape/+spec/uyukgfhfh https://kindle.wordpress.com/2017/07/04/%e2%86%93%e2%86%93%e2%86%93%e2%86%93%e2%86%93%e2%99%ab184485i9490amazon-kindle-technical-support-number-kindle-technical-support-phone-number-kindl/ http://gmailsupportn.blogspot.com/2017/07/184485i9490amazon-kindle-technical.html https://events.com/r/en_US/registration/jaiajaiajia1-84485i-949o-kindle-technical-support-phone-number-july-134425 https://events.com/r/en_US/registration/googlee1-84485i-949o-kindle-technical-support-phone-numbernumber-july-134426 https://events.com/r/en_US/registration/1kndlehelp-1-84485i-949o-kindle-technical-support-phone-number-number-july-134424 http://gmailsupportn.blogspot.com/2017/07/1kndlehelp-1-84485i-949o-kindle.html https://kindle.wordpress.com/2017/07/04/1kndlehelp-1-84485i-949o-kindle-technical-support-phone-number-number/ https://bugs.launchpad.net/inkscape/+bug/1702352 https://bugs.launchpad.net/inkscape/+bug/1702353 https://bugs.launchpad.net/inkscape/+bug/1702354 https://kindle.wordpress.com/2017/07/04/state1844-851-9490
[Yahoo-eng-team] [Bug 1701288] Re: In scale testing RPC timeout error seen in the ovs_neutron_agent when update_device_list is called with DVR routers
Reviewed: https://review.openstack.org/479091 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5be1ace5462994b492b811e20d8a90caac0fcffd Submitter: Jenkins Branch:master commit 5be1ace5462994b492b811e20d8a90caac0fcffd Author: Kevin Benton Date: Thu Jun 29 15:46:21 2017 -0700 Use subqueryload in l2pop DB for binding ports This adjusts the l2pop DB queries that leverage the port relationship on the PortBinding and DistributedPortBinding models to ensure that the port gets loaded from the DB as part of the initial query. Without this the number of DB queries will increase with the number of ports since the port wasn't being loaded until the 'port' attribute was referenced on its corresponding binding object. Closes-Bug: #1701288 Change-Id: I7c3b08d525b2c90100c9fe4efaee973cf3a076f3 ** 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/1701288 Title: In scale testing RPC timeout error seen in the ovs_neutron_agent when update_device_list is called with DVR routers Status in neutron: Fix Released Bug description: At large scale testing when trying to deploy around 8000 VMs with DVR routers, we are seeing an RPC Timeout error in ovs_neutron_agent. This RPC Timeout error occurs when the ovs_neutron_agent tries to bind the vif port. On further analysis it seems that the update_port_status is taking a lot more time at large scale to return and so the ovs_neutron_agent timesout waiting for the message. Looking into the update_port_status code path, after the port status update occurs it calls the update_port_postcommit call. Since L2pop is enabled by default with DVR, the update_port_postcommit calls _create_agent_fdb entries for the agent, if this is the first port associated with the agent. In _create_agent_fdb it tries to retrieve all the PortInfo associated with network and this DB call is very expensive and sometimes we have seen it take upto to 3900s at some instances. 2017-06-15 17:48:30.651 9320 DEBUG neutron.agent.linux.utils [req-51df1df5-8a51-4679-938b-895545a225c2 - - - - -] Exit code: 0 execute /opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-ece15133-1294-46c0-b0b5-cab785d4314b - - - - -] Error while processing VIF ports 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 2044, in rpc_loop 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent port_info, ovs_restarted) 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/osprofiler/profiler.py", line 154, in wrapper 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent return f(*args, **kwargs) 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 1648, in process_network_ports 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent failed_devices['added'] |= self._bind_devices(need_binding_devices) 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py", line 888, in _bind_devices 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent self.conf.host) 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/agent/rpc.py", line 181, in update_device_list 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent agent_id=agent_id, host=host) 2017-06-15 17:48:38.420 9320 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File "/opt/stack/venv/neutron-20170421T033908Z/lib/python2.7/site-packages/neutron/common/rpc.py", line 185, in call 2017-06-15
[Yahoo-eng-team] [Bug 1702336] [NEW] Image no selectable when 'Launch' is triggered
Public bug reported: Hi, horizon (10.0.0.dev1973) http://website.com/project/images ->Compute ->Images Click 'Launch' next to an image On proceeding 'Launch Instance' window, under Source, the selected image is not visible on either Allocated or Available table Tested with Chrome Version 59.0.3071.115 and Firefox on Windows 7 Regards, ** 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/1702336 Title: Image no selectable when 'Launch' is triggered Status in OpenStack Dashboard (Horizon): New Bug description: Hi, horizon (10.0.0.dev1973) http://website.com/project/images ->Compute ->Images Click 'Launch' next to an image On proceeding 'Launch Instance' window, under Source, the selected image is not visible on either Allocated or Available table Tested with Chrome Version 59.0.3071.115 and Firefox on Windows 7 Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1702336/+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 1702312] [NEW] [FWaaS v2] Does not work with core plugin non based on Neutron DB model
Public bug reported: The FWaaS v2 service plugin is extends the Neutron DB models and it is completely depend on it. So if we used a core plugin not based on the Neutron DB model (like Contrail one), we cannot use that service plugin and implement a specific driver. The service plugin must be more generic and also provide a plugable backend driver mechanism to authorize different drivers than ML2 with OVS. ** Affects: neutron Importance: Undecided Status: New ** Tags: fwaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1702312 Title: [FWaaS v2] Does not work with core plugin non based on Neutron DB model Status in neutron: New Bug description: The FWaaS v2 service plugin is extends the Neutron DB models and it is completely depend on it. So if we used a core plugin not based on the Neutron DB model (like Contrail one), we cannot use that service plugin and implement a specific driver. The service plugin must be more generic and also provide a plugable backend driver mechanism to authorize different drivers than ML2 with OVS. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1702312/+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 1702310] [NEW] Unclear description of 'disable-log-reason' api-ref
Public bug reported: 'disable-log-reason' API action disable the compute service and log the disabled reason. But api-ref statement sounds like this API only log the disable reason. - https://developer.openstack.org/api-ref/compute/#log-disabled-compute- service-information ** Affects: nova Importance: Undecided Assignee: Ghanshyam Mann (ghanshyammann) Status: In Progress -- 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/1702310 Title: Unclear description of 'disable-log-reason' api-ref Status in OpenStack Compute (nova): In Progress Bug description: 'disable-log-reason' API action disable the compute service and log the disabled reason. But api-ref statement sounds like this API only log the disable reason. - https://developer.openstack.org/api-ref/compute/#log-disabled- compute-service-information To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702310/+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 1702238] Re: 'project_id' & 'user_id' are required keys in server group APIs
Reviewed: https://review.openstack.org/480162 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d22fe3998614118272936aa11fa44de57a87d27f Submitter: Jenkins Branch:master commit d22fe3998614118272936aa11fa44de57a87d27f Author: ghanshyam Date: Tue Jul 4 15:03:18 2017 +0300 Fix 'project-id' 'user-id' as required in server group 'project_id' and 'user_id' are introduced as mandatory param in microversion 2.13 but api-ref shows them as optional - https://developer.openstack.org/api-ref/compute/?expanded=show-server-group-details-detail#show-server-group-details api-ref should reflect the actual behavior. Change-Id: Id7e734c65a97c82824c00ed054c13cb9fae2dd3c Closes-Bug: #1702238 ** Changed in: nova Status: In Progress => Fix Released -- 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/1702238 Title: 'project_id' & 'user_id' are required keys in server group APIs Status in OpenStack Compute (nova): Fix Released Bug description: 'project_id' and 'user_id' are introduced as mandatory param in microversion 2.13 but api-ref shows them as optional - https://developer.openstack.org/api-ref/compute/?expanded=show-server- group-details-detail#show-server-group-details api-ref should be fixed to reflect the actual behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702238/+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 1702304] [NEW] MISC_SHARES_VIA_AGGREGATE not found still show up in the functional test
Public bug reported: The trait MISC_SHARES_VIA_AGGREGATE still may not found in the functional test, even after the fix https://review.openstack.org/478564. One of case: http://logs.openstack.org/85/330285/83/check/gate-nova-tox-functional-py35-ubuntu-xenial/94a3627/testr_results.html.gz 29 hits: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22%2Fusr%2Flocal%2Fbin%2Fdevstack-version:%20line%203:%20unexpected%20EOF%20while%20looking%20for%20matching%20%60''%5C%22%20AND%20tags:%5C%22console%5C%22&from=7d ** 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/1702304 Title: MISC_SHARES_VIA_AGGREGATE not found still show up in the functional test Status in OpenStack Compute (nova): New Bug description: The trait MISC_SHARES_VIA_AGGREGATE still may not found in the functional test, even after the fix https://review.openstack.org/478564. One of case: http://logs.openstack.org/85/330285/83/check/gate-nova-tox-functional-py35-ubuntu-xenial/94a3627/testr_results.html.gz 29 hits: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22%2Fusr%2Flocal%2Fbin%2Fdevstack-version:%20line%203:%20unexpected%20EOF%20while%20looking%20for%20matching%20%60''%5C%22%20AND%20tags:%5C%22console%5C%22&from=7d To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702304/+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 1452568] Re: nova allows to live-migrate instance from one availability zone to another
Closing an old bug, as it was fixed by http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented /check-destination-on-migrations-newton.html Now, if you provide a destination, we verify by calling the scheduler for that target unless you provide an explicit "force" flag to the migration call. ** Changed in: nova Status: Confirmed => Won't Fix -- 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/1452568 Title: nova allows to live-migrate instance from one availability zone to another Status in OpenStack Compute (nova): Won't Fix Bug description: Nova allows to live migrate instance from one AZ to another: Steps to reproduce: 1.boot instance with --availability-zone param 2. live migrate this instance on host located in another AZ, nova live-migration inst1 host2 If user specify host during live-migration scheduler doen't make any checks: Result: instance migrate successfully, but information in instances table in db doesn't updates mysql> select hostname, availability_zone from instances where deleted=false; +--+---+ | hostname | availability_zone | +--+---+ | demo | alice-zone | +--+---+ while nova show command show real AZ info: root@node-7:~# nova show demo +--+--+ | Property | Value | +--+--+ | OS-EXT-AZ:availability_zone | bob-zone | | name | demo | +--+--+ Nova should forbid such live migration, by adding extra checks, or update info in db table to provide data consistency To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1452568/+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 1700999] Re: during nova service install , an unneeded httpd conf bug fix causes openstack client cli crash
The content in question is being moved to the nova repository, see https://review.openstack.org/#/c/477488/. I'm also not sure about the suggested fix, the nova placement configuration is not a verification step. ** Project changed: openstack-manuals => nova -- 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/1700999 Title: during nova service install ,an unneeded httpd conf bug fix causes openstack client cli crash Status in OpenStack Compute (nova): Confirmed Bug description: - [X] This doc is inaccurate in this way: Hi , Please MOVE the quoted section below from : https://docs.openstack.org/ocata/install-guide-rdo/nova-controller- install.html#install-and-configure-components To: https://docs.openstack.org/ocata/install-guide-rdo/nova-verify.html (before no.5). reason: When the patch is done at the original location it breaks the openstack client cli , breaking openstack configuration cli (openstack user create ...etc.): details further down ... """ Due to a packaging bug, you must enable access to the Placement API by adding the following configuration to /etc/httpd/conf.d/00 -nova-placement-api.conf: = 2.4> Require all granted Order allow,deny Allow from all Restart the httpd service: # systemctl restart httpd """ when you do add this section to the named httpd conf file. it causes the following error on all openstack client cli : #openstack endpoint list;openstack catalog list Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Internal Server Error (HTTP 500) Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Internal Server Error (HTTP 500) Bug suggested solution : Please MOVE the mentioned section to https://docs.openstack.org/ocata/install-guide-rdo/nova-verify.html (before no.5 - nova-status upgrade check). Adding the httpd section patch at this step works flawlessly. The solution to the original bug placement as is : Undo && redo the following part of the identity service install : https://docs.openstack.org/ocata/install-guide-rdo/keystone-install.html openstack vers. : #rpm -qa |grep openstack-nova openstack-nova-common-15.0.3-2.el7.noarch openstack-nova-conductor-15.0.3-2.el7.noarch openstack-nova-api-15.0.3-2.el7.noarch openstack-nova-console-15.0.3-2.el7.noarch openstack-nova-scheduler-15.0.3-2.el7.noarch openstack-nova-novncproxy-15.0.3-2.el7.noarch OS details : CentOS Linux release 7.3.1611 (Core) Derived from Red Hat Enterprise Linux 7.3 (Source) NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/"; BUG_REPORT_URL="https://bugs.centos.org/"; CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" CentOS Linux release 7.3.1611 (Core) CentOS Linux release 7.3.1611 (Core) cpe:/o:centos:centos:7 --- Release: 15.0.0 on 2017-06-22 12:09 SHA: 33b12839643984b75465df265ee355683e40c6cf Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/nova-controller-install.rst URL: https://docs.openstack.org/ocata/install-guide-rdo/nova-controller-install.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1700999/+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 1700999] [NEW] during nova service install , an unneeded httpd conf bug fix causes openstack client cli crash
You have been subscribed to a public bug: - [X] This doc is inaccurate in this way: Hi , Please MOVE the quoted section below from : https://docs.openstack.org/ocata/install-guide-rdo/nova-controller- install.html#install-and-configure-components To: https://docs.openstack.org/ocata/install-guide-rdo/nova-verify.html (before no.5). reason: When the patch is done at the original location it breaks the openstack client cli , breaking openstack configuration cli (openstack user create ...etc.): details further down ... """ Due to a packaging bug, you must enable access to the Placement API by adding the following configuration to /etc/httpd/conf.d/00-nova- placement-api.conf: = 2.4> Require all granted Order allow,deny Allow from all Restart the httpd service: # systemctl restart httpd """ when you do add this section to the named httpd conf file. it causes the following error on all openstack client cli : #openstack endpoint list;openstack catalog list Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Internal Server Error (HTTP 500) Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Internal Server Error (HTTP 500) Bug suggested solution : Please MOVE the mentioned section to https://docs.openstack.org/ocata/install-guide-rdo/nova-verify.html (before no.5 - nova-status upgrade check). Adding the httpd section patch at this step works flawlessly. The solution to the original bug placement as is : Undo && redo the following part of the identity service install : https://docs.openstack.org/ocata/install-guide-rdo/keystone-install.html openstack vers. : #rpm -qa |grep openstack-nova openstack-nova-common-15.0.3-2.el7.noarch openstack-nova-conductor-15.0.3-2.el7.noarch openstack-nova-api-15.0.3-2.el7.noarch openstack-nova-console-15.0.3-2.el7.noarch openstack-nova-scheduler-15.0.3-2.el7.noarch openstack-nova-novncproxy-15.0.3-2.el7.noarch OS details : CentOS Linux release 7.3.1611 (Core) Derived from Red Hat Enterprise Linux 7.3 (Source) NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/"; BUG_REPORT_URL="https://bugs.centos.org/"; CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" CentOS Linux release 7.3.1611 (Core) CentOS Linux release 7.3.1611 (Core) cpe:/o:centos:centos:7 --- Release: 15.0.0 on 2017-06-22 12:09 SHA: 33b12839643984b75465df265ee355683e40c6cf Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/nova-controller-install.rst URL: https://docs.openstack.org/ocata/install-guide-rdo/nova-controller-install.html ** Affects: nova Importance: High Status: Confirmed ** Tags: httpd install install-guide nova -- during nova service install ,an unneeded httpd conf bug fix causes openstack client cli crash https://bugs.launchpad.net/bugs/1700999 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- 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 1029950] Re: No limits on image size
** Changed in: glance Status: New => Opinion -- 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/1029950 Title: No limits on image size Status in Glance: Opinion Status in OpenStack Compute (nova): Opinion Status in OpenStack Security Advisory: Won't Fix Bug description: Using Epel Essex packages on RHEL 6.3 Glance should impose configurable limits (or tenant quotas) on the size of the images it allows to be registered and/or uploaded. Two separate example exploits here 1. Glance Denial of Service by file system exhaustion 2. Nova Compute Denial of Service by file system exhaustion = 1 = Using the glance x-image-meta-property-copy-from header it is possible to get glance to keep downloading a large resource until it fills up the local harddrive e.g. $ glance add name="big image" disk_format=raw container_format=ovf copy_from=http://server/cgi-bin/t.cgi # [1] Failed to add image. Got error: The request returned a 413 Request Entity Too Large. This generally means that rate limiting or a quota threshold was breached. The response body: 413 Request Entity Too Large The body of your request was too large for this server. Image storage media is full: There is not enough disk space on the image storage media. Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'. $ ls -lh /var/lib/glance/images/f1db6d09-1eac-4ce4-86ff-8a34bfea33af -rw-r--r--. 1 glance glance 87G Jul 27 13:03 /var/lib/glance/images/f1db6d09-1eac-4ce4-86ff-8a34bfea33af $ df -h /var/lib/glance/images/ FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_rheva8c03-lv_root 104G 98G 261M 100% / this would allow any authenticated user to preform a denial of service on a glance server, with a file system backend. I havn't looked into swift but will it just keep going until is starts filling up storage nodes? = 2 = Nova is also open to a similar exploit, by using the x-image-meta- location header in a glance add, a large resource can be registered with glance, any nova compute node that tries to use this image to start an instance can have its disk space very quickly exhausted with a singe instance # Registering an image 1TB in size (can go bigger if needs be) $ glance add name="big image" disk_format=raw container_format=ovf location=http://server/cgi-bin/t.cgi Added new image with ID: 1a528173-7ca9-4320-b0f3-dac127a1f337 $ glance index ID Name Disk Format Container Format Size -- -- 1a528173-7ca9-4320-b0f3-dac127a1f337 big image raw ovf 1099511627776 $ nova boot --flavor 1 --image 1a528173-7ca9-4320-b0f3-dac127a1f337 bigtest # the filesystem now fills up, the boot fails and nova deletes the partial download # next I check the apache logs to see how much nova downloaded. "GET /cgi-bin/t.cgi HTTP/1.1" 200 93406637550 "-" "-" # Note : I know I will probably not get the same compute node next time but # this will at least give me an idea of what size might be tolerated. # edit cgi script [1] to change the content length to something slightly smaller then 93406637550 $ glance add name="smaller big image" disk_format=raw container_format=ovf location=http://server/cgi-bin/t.cgi Added new image with ID: a5eb1eab-1536-438f-82cf-4b642cf9d363 $ glance index ID Name Disk Format Container Format Size -- -- a5eb1eab-1536-438f-82cf-4b642cf9d363 smaller big image raw ovf 90406637550 1a528173-7ca9-4320-b0f3-dac127a1f337 big image raw ovf 1099511627776 $ nova boot --flavor 1 --image a5eb1eab-1536-438f-82cf-4b642cf9d363 bigtest_2 $ ls -lh /var/lib/nova/instances/_base/7f9a4e3c2891c537a784391cd962e6a5527d0a27 -rw-r--r--. 1 qemu qemu 85G Jul 27 14:13 /var/lib/nova/instances/_base/7f9a4e3c2891c537a784391cd962e6a5527d0a27 $ df -h /var/lib/nova/instances/_base/ FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_rheva8c03-lv_root 104G 97G 1.1G 99% / $ [1] Standard http cgi script used as the vm image #!/usr/bin/python import os, sys, uuid print "Content-Type: text/html" #print "Content-Length: 1099511627776" # this shouldn't be present for first exploit print data
[Yahoo-eng-team] [Bug 1658070] Re: Failed SR_IOV evacuation with host
** Changed in: mos Milestone: 9.x-updates => 10.0 ** Changed in: mos Status: Confirmed => Won't Fix -- 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/1658070 Title: Failed SR_IOV evacuation with host Status in Mirantis OpenStack: Won't Fix Status in Mirantis OpenStack 9.x series: Fix Released Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) newton series: In Progress Status in OpenStack Compute (nova) ocata series: Fix Committed Bug description: When we try evacuate SR-IOV vm on concret host the VM is in ERROR state Steps to reproduce: 1) Download trusty image 2) Create image 3) Create vf port: neutron port-create --binding:vnic-type direct --device_owner nova-compute --name sriov 4) Boot vm on this port: nova boot vm --flavor m1.small --image 1ff0759c-ea85-4909-a711-70fd6b71ad23 --nic port-id=cfc947be-1975-42f3-95bd-f261a2eccec0 --key-name vm_key 5) Sgut down node with vm 6) Evacuate vm: nova evacuate vm node-5.test.domain.local Expected result: VM evacuates on the 5th node Actual result: VM in error state Workaround: We can evacuate without pointing the host just nova evacuate vm Environment: #785 snap 2 controllers? 2 compute with SR-IOV To manage notifications about this bug go to: https://bugs.launchpad.net/mos/+bug/1658070/+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 1675788] Re: Sequential API requests in instance details as a bottleneck
Reviewed: https://review.openstack.org/449652 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7fdd8757036e7f014528b977ee27007a125d841c Submitter: Jenkins Branch:master commit 7fdd8757036e7f014528b977ee27007a125d841c Author: Mateusz Kowalski Date: Fri Mar 24 15:10:39 2017 +0100 Make API calls in Instances.DetailView parallel In order to increase rendering speed, make nova and network api calls parallel in instance Detail View panel. Closes-bug: #1675788 Change-Id: I3c94292981d6bf11e6e2947704b314842a99676f ** 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/1675788 Title: Sequential API requests in instance details as a bottleneck Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When loading instance details, the following API calls are executed sequentially * api.nova.server_get * api.nova.instance_volumes_list * api.nova.flavor_get * api.network.server_security_groups * api.network.servers_update_addresses The last 4 can be executed in parallel. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675788/+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 1702275] [NEW] Extra Provider summary returned from AllocationCandidates.get_by_filters
Public bug reported: The case is there are three resource providers, only two RPs have enough resources. But the return of AllocationCandidates.get_by_filters includes the provider summary of the RP without enough resource. This is due to miss a filter like the comment said https://github.com/openstack/nova/blob/3863eca0ac5a9437354288de673c831d5dc20f2e/nova/objects/resource_provider.py#L2364 in the code ** Affects: nova Importance: Undecided Assignee: Alex Xu (xuhj) Status: In Progress ** Tags: placement ** Changed in: nova Assignee: (unassigned) => Alex Xu (xuhj) ** Tags added: placement -- 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/1702275 Title: Extra Provider summary returned from AllocationCandidates.get_by_filters Status in OpenStack Compute (nova): In Progress Bug description: The case is there are three resource providers, only two RPs have enough resources. But the return of AllocationCandidates.get_by_filters includes the provider summary of the RP without enough resource. This is due to miss a filter like the comment said https://github.com/openstack/nova/blob/3863eca0ac5a9437354288de673c831d5dc20f2e/nova/objects/resource_provider.py#L2364 in the code To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702275/+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 1702270] [NEW] glance-api does not exit gracefully on sigkill and sigterm signal
Public bug reported: When user sends either sigkill or sigterm signal to glance-api's parent process then it exits immediately without completing the current request. As per openstack serivce standards it should wait until current request is completed and should not accept new request for processing till exiting. Note: For kill signal parent process exits immediately where as child process keeps running forever whereas for terminate signal parent and child processes exits immediately. Expected behavior: 1. glance-api should complete current request before exiting 2. glance-api should not accept new request for processing ** Affects: glance Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1702270 Title: glance-api does not exit gracefully on sigkill and sigterm signal Status in Glance: New Bug description: When user sends either sigkill or sigterm signal to glance-api's parent process then it exits immediately without completing the current request. As per openstack serivce standards it should wait until current request is completed and should not accept new request for processing till exiting. Note: For kill signal parent process exits immediately where as child process keeps running forever whereas for terminate signal parent and child processes exits immediately. Expected behavior: 1. glance-api should complete current request before exiting 2. glance-api should not accept new request for processing To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1702270/+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 1702268] [NEW] scheduler service does not exit gracefully on receiving sigkill signal
Public bug reported: When user sends sigkill signal to nova-scheduler parent process, parent process terminates immediately without processing the current request. Old message remains in rabbitmq. If new request is sent then it remains in rabbitmq. When nova-scheduler is up again then it picks all requests from rabbitmq for processing. Note: If user sends sigterm signal to nova-scheduler then parent process waits until current request is completed. Expected behavior: 1. scheduler should complete current request before exiting - Not Good 2. scheduler should not accept new request for processing - Good ** Affects: nova Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) 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/1702268 Title: scheduler service does not exit gracefully on receiving sigkill signal Status in OpenStack Compute (nova): New Bug description: When user sends sigkill signal to nova-scheduler parent process, parent process terminates immediately without processing the current request. Old message remains in rabbitmq. If new request is sent then it remains in rabbitmq. When nova-scheduler is up again then it picks all requests from rabbitmq for processing. Note: If user sends sigterm signal to nova-scheduler then parent process waits until current request is completed. Expected behavior: 1. scheduler should complete current request before exiting - Not Good 2. scheduler should not accept new request for processing - Good To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702268/+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 1702260] [NEW] nova compute child process remains orphan after sending sigkill or sigterm signal to parent process
Public bug reported: When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to nova- comupte parent process then parent process terminates immediately but child process keeps running forever and keeps processing the requests received from rabbitmq. Steps to reproduce: 1. Identify running processes of nova-compute using "ps aux | grep nova-compute' 2. Send kill or terminate signal to parent process. $ kill -9 or kill -15 3. Verify parent process is killed using "ps aux | grep nova-compute' ** Affects: nova Importance: Undecided Status: New ** Summary changed: - nova compute child process remains orphan after sending kill or interrupt signal to parent process + nova compute child process remains orphan after sending sigkill or sigterm signal to parent process ** Description changed: - When user sends SIGKILL (kill -9) or SIGINT (kill -15) signal to nova- + When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to nova- comupte parent process then parent process terminates immediately but child process keeps running forever and keeps processing the requests received from rabbitmq. Steps to reproduce: 1. Identify running processes of nova-compute using "ps aux | grep nova-compute' 2. Send kill or terminate signal to parent process. -$ kill -9 or kill -15 + $ kill -9 or kill -15 3. Verify parent process is killed using "ps aux | grep nova-compute' -- 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/1702260 Title: nova compute child process remains orphan after sending sigkill or sigterm signal to parent process Status in OpenStack Compute (nova): New Bug description: When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to nova-comupte parent process then parent process terminates immediately but child process keeps running forever and keeps processing the requests received from rabbitmq. Steps to reproduce: 1. Identify running processes of nova-compute using "ps aux | grep nova-compute' 2. Send kill or terminate signal to parent process. $ kill -9 or kill -15 3. Verify parent process is killed using "ps aux | grep nova-compute' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702260/+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 1702263] [NEW] nova conductor does not exits gracefully
Public bug reported: When user sends sigkill or sigterm signal to nova-conductor parent process, parent process is exits immediately. Child process which is processing the request get killed after sometime (2-3 seconds) without completing the current request. Meantime if new request is sent then nova-conductor does not picks that request from rabbitmq for processing. Once nova-conductor is up and running again then it picks the pending requests from rabbitmq for processing. Expected behavior: 1. conductor should complete current request before exiting - Not Good 2. conductor should not accept new request for processing - Good ** 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/1702263 Title: nova conductor does not exits gracefully Status in OpenStack Compute (nova): New Bug description: When user sends sigkill or sigterm signal to nova-conductor parent process, parent process is exits immediately. Child process which is processing the request get killed after sometime (2-3 seconds) without completing the current request. Meantime if new request is sent then nova-conductor does not picks that request from rabbitmq for processing. Once nova-conductor is up and running again then it picks the pending requests from rabbitmq for processing. Expected behavior: 1. conductor should complete current request before exiting - Not Good 2. conductor should not accept new request for processing - Good To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702263/+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 1521756] Re: race condition in test_upload_image_http_nonexistent_location_url: glance_store doesn't handle properly invalid HTTP reply
I have confirmed that this is not a failure any more by running these
tests in 6 different terminals and continuously 1 hour using "while
true; do tox -e py27 glance.tests.unit.v1.test_api || break; done"
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1521756
Title:
race condition in test_upload_image_http_nonexistent_location_url:
glance_store doesn't handle properly invalid HTTP reply
Status in Glance:
Invalid
Bug description:
Victor asked for me to have a look at an intermittent failure he was
seeing in https://review.openstack.org/#/c/250083/
it shows up like so:
Traceback (most recent call last):
File
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/eventlet/greenpool.py",
line 82, in _spawn_n_impl
func(*args, **kwargs)
File "/home/robertc/work/openstack/glance/glance/api/v1/images.py", line
737, in _upload_and_activate
location_data = self._upload(req, image_meta)
File "/home/robertc/work/openstack/glance/glance/api/v1/images.py", line
671, in _upload
{'status': 'saving'})
File
"/home/robertc/work/openstack/glance/glance/registry/client/v1/api.py", line
174, in update_image_metadata
from_state=from_state)
File
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line
209, in update_image
headers=headers)
File
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line
141, in do_request
'exc_name': exc_name})
File
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/oslo_utils/excutils.py",
line 204, in __exit__
six.reraise(self.type_, self.value, self.tb)
File
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/six.py",
line 686, in reraise
raise value
File
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line
124, in do_request
**kwargs)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line
71, in wrapped
return func(self, *args, **kwargs)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line
375, in do_request
headers=copy.deepcopy(headers))
File "/home/robertc/work/openstack/glance/glance/common/client.py", line
88, in wrapped
return func(self, method, url, body, headers)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line
524, in _do_request
raise exception.NotFound(res.read())
glance.common.exception.NotFound: b'Image not found'
==
FAIL:
glance.tests.unit.v1.test_api.TestGlanceAPI.test_upload_image_http_nonexistent_location_url
tags: worker-0
--
Traceback (most recent call last):
File
"/home/robertc/work/openstack/glance/glance/tests/unit/v1/test_api.py", line
1149, in test_upload_image_http_nonexistent_location_url
self.assertEqual(404, res.status_int)
File
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
line 350, in assertEqual
self.assertThat(observed, matcher, message)
File
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
line 435, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 404 != 201
and through bisection I can reproduce it with 75 tests - I'm working on
shrinking the set but it takes a couple hundred runs to be sure its a false
branch, so its not super fast.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1521756/+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 1702256] [NEW] [Hyper-V][Azure]cloudinit fail to get_source on Azure
Public bug reported: cloud-init on Azure cannot work properly: This is in fact a regression, caused by commit: ebc9ecbc8a76bdf511a456fb72339a7eb4c20568 The issue happens in the following code: cloudinit/source/DataSourceAzure.py. The removal of "sources.DEP_NETWORK" makes sources.list_sources() return [] for DataSourceAzure, which is the root cause. + # Used to match classes to dependencies datasources = [ -(DataSourceAzureNet, (sources.DEP_FILESYSTEM, sources.DEP_NETWORK)), +(DataSourceAzure, (sources.DEP_FILESYSTEM, )), ] The error log: 2017-07-04 08:28:49,555 - __init__.py[DEBUG]: Searching for network data source in: [] 2017-07-04 08:28:49,555 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2017-07-04 08:28:49,555 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/cmd/main.py", line 331, in main_init init.fetch(existing=existing) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/stages.py", line 349, in fetch return self._get_data_source(existing=existing) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/stages.py", line 259, in _get_data_source pkg_list, self.reporter) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/sources/__init__.py", line 334, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1702256 Title: [Hyper-V][Azure]cloudinit fail to get_source on Azure Status in cloud-init: New Bug description: cloud-init on Azure cannot work properly: This is in fact a regression, caused by commit: ebc9ecbc8a76bdf511a456fb72339a7eb4c20568 The issue happens in the following code: cloudinit/source/DataSourceAzure.py. The removal of "sources.DEP_NETWORK" makes sources.list_sources() return [] for DataSourceAzure, which is the root cause. + # Used to match classes to dependencies datasources = [ -(DataSourceAzureNet, (sources.DEP_FILESYSTEM, sources.DEP_NETWORK)), +(DataSourceAzure, (sources.DEP_FILESYSTEM, )), ] The error log: 2017-07-04 08:28:49,555 - __init__.py[DEBUG]: Searching for network data source in: [] 2017-07-04 08:28:49,555 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2017-07-04 08:28:49,555 - util.py[DEBUG]: No instance datasource found! Likely bad things to come! Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/cmd/main.py", line 331, in main_init init.fetch(existing=existing) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/stages.py", line 349, in fetch return self._get_data_source(existing=existing) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/stages.py", line 259, in _get_data_source pkg_list, self.reporter) File "/usr/local/lib/python2.7/site-packages/cloud_init-0.7.9-py2.7.egg/cloudinit/sources/__init__.py", line 334, in find_source raise DataSourceNotFoundException(msg) DataSourceNotFoundException: Did not find any data source, searched classes: () To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1702256/+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 1702242] [NEW] Convert conntrack command properly when firewall rule has port range
Public bug reported: Current code only converts conntrack command from firewall rule properly if the firewall rule contains only single port like: `neutron firewall-rule-create --protocol tcp --action allow --ip-version 4 --destination-port 8777 --enabled True` However, if the rule contains port range, which is possible when creating firewall rule like this: `neutron firewall-rule-create --protocol tcp --action allow --ip-version 4 --destination-port 8778:9000 --enabled True` The conntrack command would look like: ['ip', 'netns', 'exec', 'qrouter-7bab1e53-0330-41af-8e98-b925d1a76984', 'conntrack', '-D', '-p', 'tcp', '-f', 'ipv4', '--dport', '8778:9000'] Conntrack-tools does not understand the option `--dport 8778:9000`, it instead applies above command to port 8778 only, which is not expected. This Patch Set fixes that issue by following the same method in netlink implementation [1] [1] https://review.openstack.org/#/c/438445/ ** Affects: neutron Importance: Undecided Assignee: Vu Cong Tuan (tuan.vu) Status: In Progress ** Tags: fwaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1702242 Title: Convert conntrack command properly when firewall rule has port range Status in neutron: In Progress Bug description: Current code only converts conntrack command from firewall rule properly if the firewall rule contains only single port like: `neutron firewall-rule-create --protocol tcp --action allow --ip-version 4 --destination-port 8777 --enabled True` However, if the rule contains port range, which is possible when creating firewall rule like this: `neutron firewall-rule-create --protocol tcp --action allow --ip-version 4 --destination-port 8778:9000 --enabled True` The conntrack command would look like: ['ip', 'netns', 'exec', 'qrouter-7bab1e53-0330-41af-8e98-b925d1a76984', 'conntrack', '-D', '-p', 'tcp', '-f', 'ipv4', '--dport', '8778:9000'] Conntrack-tools does not understand the option `--dport 8778:9000`, it instead applies above command to port 8778 only, which is not expected. This Patch Set fixes that issue by following the same method in netlink implementation [1] [1] https://review.openstack.org/#/c/438445/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1702242/+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 1702238] [NEW] 'project_id' & 'user_id' are required keys in server group APIs
Public bug reported: 'project_id' and 'user_id' are introduced as mandatory param in microversion 2.13 but api-ref shows them as optional - https://developer.openstack.org/api-ref/compute/?expanded=show-server- group-details-detail#show-server-group-details api-ref should be fixed to reflect the actual behavior. ** Affects: nova Importance: Undecided Assignee: Ghanshyam Mann (ghanshyammann) Status: New ** Changed in: nova Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann) -- 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/1702238 Title: 'project_id' & 'user_id' are required keys in server group APIs Status in OpenStack Compute (nova): New Bug description: 'project_id' and 'user_id' are introduced as mandatory param in microversion 2.13 but api-ref shows them as optional - https://developer.openstack.org/api-ref/compute/?expanded=show-server- group-details-detail#show-server-group-details api-ref should be fixed to reflect the actual behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1702238/+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 1702230] [NEW] fernet token fails with keystone HA
Public bug reported:
I have newton release in my environment with keystone provider fernet on Centos
7.
When I am trying to upload image to glance it is failing with below message.
glance-api.log:
2017-07-04 02:03:28.771 8105 WARNING keystonemiddleware.auth_token [-] Identity
response: {"error": {"message": "This is not a recognized Fernet token
gABZWy-wVlXrPlfa6_6PsyXky45ejM06Yt04UTLN6I51-CDT-kio83aIM00Xd6XL0bRzdwY8-Ks1L8SJD-xsGKyf-XUtm5TzskxpmhPXi0vDBYnM7pH2MnopcHW3RYH7YEUnqLIHGUVoBS5MGxgmSsgv0w20onikCu7xD-kDtR1gDOdryPU=",
"code": 404, "title": "Not Found"}}
2017-07-04 02:03:28.772 8105 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
Below is the debug message I am getting.
# openstack image list --debug
START with options: [u'image', u'list', u'--debug']
options: Namespace(access_key='', access_secret='***', access_token='***',
access_token_endpoint='', access_token_type='', auth_type='',
auth_url='http://192.168.27.23:35357/v3', authorization_code='', cacert=None,
cert='', client_id='', client_secret='***', cloud='', consumer_key='',
consumer_secret='***', debug=True, default_domain='default',
default_domain_id='', default_domain_name='', deferred_help=False,
discovery_endpoint='', domain_id='', domain_name='', endpoint='',
identity_provider='', identity_provider_url='', insecure=None, interface='',
key='', log_file=None, old_profile=None, openid_scope='',
os_beta_command=False, os_compute_api_version='', os_identity_api_version='3',
os_image_api_version='2', os_network_api_version='', os_object_api_version='',
os_project_id=None, os_project_name=None, os_volume_api_version='',
passcode='', password='***', profile=None, project_domain_id='',
project_domain_name='Default', project_id='', project_name='admin',
protocol='', redirect_ur
i='', region_name='', timing=False, token='***', trust_id='', url='',
user_domain_id='', user_domain_name='Default', user_id='', username='admin',
verbose_level=3, verify=None)
Auth plugin password selected
auth_config_hook(): {'auth_type': 'password', 'beta_command': False,
u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0',
u'metering_api_version': u'2', 'auth_url': 'http://192.168.27.23:35357/v3',
u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2',
'networks': [], u'image_api_version': '2', 'verify': True, u'dns_api_version':
u'2', u'object_store_api_version': u'1', u'status': u'active', 'verbose_level':
3, 'region_name': '', 'api_timeout': None, u'baremetal_api_version': u'1',
'auth': {'user_domain_name': 'Default', 'project_name': 'admin',
'project_domain_name': 'Default'}, 'default_domain': 'default', 'debug': True,
u'image_api_use_tasks': False, u'floating_ip_source': u'neutron',
u'orchestration_api_version': u'1', 'timing': False, 'password': 'gaian',
'cacert': None, u'key_manager_api_version': u'v1', 'deferred_help': False,
u'identity_api_version': '3', u'volume_api_version': u'2', 'username': 'admin',
'cert': None, u'secgroup_sourc
e': u'neutron', u'container_api_version': u'1', u'interface': None,
u'disable_vendor_agent': {}}
defaults: {u'auth_type': 'password', u'status': u'active',
u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0',
'api_timeout': None, u'baremetal_api_version': u'1', u'image_api_version':
u'2', u'metering_api_version': u'2', u'image_api_use_tasks': False,
u'floating_ip_source': u'neutron', u'orchestration_api_version': u'1',
'cacert': None, u'network_api_version': u'2', u'message': u'', u'image_format':
u'qcow2', u'key_manager_api_version': u'v1', 'verify': True,
u'identity_api_version': u'2.0', u'volume_api_version': u'2', 'cert': None,
u'secgroup_source': u'neutron', u'container_api_version': u'1',
u'dns_api_version': u'2', u'object_store_api_version': u'1', u'interface':
None, u'disable_vendor_agent': {}}
cloud cfg: {'auth_type': 'password', 'beta_command': False,
u'compute_api_version': u'2', u'orchestration_api_version': u'1',
u'database_api_version': u'1.0', u'metering_api_version': u'2', 'auth_url':
'http://192.168.27.23:35357/v3', u'network_api_version': u'2', u'message': u'',
u'image_format': u'qcow2', 'networks': [], u'image_api_version': '2', 'verify':
True, u'dns_api_version': u'2', u'object_store_api_version': u'1', u'status':
u'active', 'verbose_level': 3, 'region_name': '', 'api_timeout': None,
u'baremetal_api_version': u'1', 'auth': {'username': 'admin', 'project_name':
'admin', 'user_domain_name': 'Default', 'auth_url':
'http://192.168.27.23:35357/v3', 'password': '***', 'project_domain_name':
'Default'}, 'default_domain': 'default', u'container_api_version': u'1',
u'image_api_use_tasks': False, u'floating_ip_source': u'neutron', 'key': None,
'timing': False, 'password': '***', 'cacert': None, u'key_manager_api_version':
u'v1', 'deferred_help': False, u'identity_api_vers
ion': '3', u'volume_api_version': u'2', 'username': 'admin', 'cert': None,
u'secgroup_source':
