date:20170130

Reviewed:  https://review.openstack.org/426817
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=11825081ec7ad8b1fa8f250e1d4cd908612be64f
Submitter: Jenkins
Branch:master

commit 11825081ec7ad8b1fa8f250e1d4cd908612be64f
Author: Boden R 
Date:   Mon Jan 30 09:00:43 2017 -0700

Fix link in QoS devref

The QoS devref has a bad link to the L2 agent extensions
doc. This patch fixes the link.

Note: The bug reports a few other neutron dead links, but
these are either already fixed, or for liberty release notes
and liberty is already EOL.

Change-Id: I047f638f0a348d636aa533c0db93e8a1f23c6356
Closes-Bug: #1652944


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

Title:
  Broken links

Status in neutron:
  Fix Released
Status in openstack-manuals:
  Fix Released

Bug description:
  The documentation of neutron (see referer below) contains links to
  pages that do not exist. This was found by a global check of pages on
  docs.openstack.org using scrapy.

  {"url": 
"http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/quality_of_service.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_ovs.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/layer3.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario4b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario1b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario3b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_lb.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/adv_config_ipv6.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/releasenotes/neutron/liberty.html"},
  {"url": 
"http://docs.openstack.org/developer/neutron/devref/l2_agent_extensions;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/quality_of_service.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_lb.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario4b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario1b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/deploy_scenario3b.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/linuxbridge_agent.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/scenario_legacy_ovs.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/developer/neutron/devref/layer3.html"},
  {"url": 
"http://docs.openstack.org/newton/networking-guide/adv_config_ipv6.html;, 
"status": 404, "referer": 
"http://docs.openstack.org/releasenotes/neutron/liberty.html"},
  {"url": 
"http://docs.openstack.org/developer/openstack-ansible/install-guide-revised-draft/targethosts-networkconfig.html;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/openstack-ansible-os_neutron/newton/app-openvswitch.html"},
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/others/testing.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/route-advertisement.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/design/drivers.rst;,
 "status": 404, "referer": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/bgp-speaker.html"},
  {"url": 
"http://docs.openstack.org/developer/neutron-dynamic-routing/functionality/dynamic-routing-agent.rst;,
 "status": 404, "referer":

[Yahoo-eng-team] [Bug 1577630] Re: ERROR neutron_lbaas.agent.agent_manager - HaproxyNSDriver

[Expired for octavia because there has been no activity for 60 days.]

** Changed in: octavia
   Status: Incomplete => Expired

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

Title:
  ERROR neutron_lbaas.agent.agent_manager - HaproxyNSDriver

Status in neutron:
  Invalid
Status in octavia:
  Expired

Bug description:
  Hi,

  I use OpenStack Liberty with Ubuntu 14.04.

  I installed LBaaSv2;

  # aptitude install haproxy neutron-lbaasv2-agent python-neutron-lbaas

  /etc/neutron/neutron.conf
  [DEFAULT]
  service_plugins = 
router,neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2
  [service_providers]
  service_provider = 
LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default

  /etc/neutron/neutron_lbaas.conf
  [service_providers]
  
service_provider=LOADBALANCERV2:Haproxy:neutron_lbaas.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default

  /etc/neutron/lbaas_agent.ini
  [DEFAULT]
  interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
  ovs_use_veth = False
  device_driver = 
neutron_lbaas.services.loadbalancer.drivers.haproxy.namespace_driver.HaproxyNSDriver
  [haproxy]
  user_group = haproxy

  # tail -f /var/log/neutron/neutron-lbaasv2-agent.log
  2016-05-01 21:12:16.266 6459 INFO neutron.common.config [-] Logging enabled!
  2016-05-01 21:12:16.267 6459 INFO neutron.common.config [-] 
/usr/bin/neutron-lbaasv2-agent version 7.0.3
  2016-05-01 21:12:16.294 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on controller:5672
  2016-05-01 21:12:16.318 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on controller:5672
  2016-05-01 21:12:16.335 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on controller:5672
  2016-05-01 21:12:16.337 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on controller:5672
  2016-05-01 21:12:16.475 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on controller:5672
  2016-05-01 21:12:16.495 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on controller:5672

  $ neutron lbaas-loadbalancer-create --name lb01 
f64e80e1-da2a-40b7-ba9b-903dc72242ba
  Created a new loadbalancer:
  +-+--+
  | Field   | Value|
  +-+--+
  | admin_state_up  | True |
  | description |  |
  | id  | 599a3226-5239-4100-a118-5ad1fe6ea55d |
  | listeners   |  |
  | name| lb01 |
  | operating_status| OFFLINE  |
  | provider| haproxy  |
  | provisioning_status | PENDING_CREATE   |
  | tenant_id   | 60d7922e29e44dc1ac62df3fe7ba3841 |
  | vip_address | 192.168.100.15   |
  | vip_port_id | 5f998bc7-17bc-4bb8-9fb5-07a6b9de5860 |
  | vip_subnet_id   | f64e80e1-da2a-40b7-ba9b-903dc72242ba |
  +-+--+

  neutron lbaas-loadbalancer-list
  
+--+--++-+--+
  | id   | name | vip_address| 
provisioning_status | provider |
  
+--+--++-+--+
  | 599a3226-5239-4100-a118-5ad1fe6ea55d | lb01 | 192.168.100.15 | ERROR
   | haproxy  |
  
+--+--++-+--+

  $ tail -f /var/log/neutron/neutron-lbaasv2-agent.log 
  2016-05-01 21:12:16.337 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on controller:5672
  2016-05-01 21:12:16.475 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connecting to AMQP server on controller:5672
  2016-05-01 21:12:16.495 6459 INFO oslo.messaging._drivers.impl_rabbit [-] 
Connected to AMQP server on controller:5672
  2016-05-01 21:40:43.582 6459 ERROR neutron_lbaas.agent.agent_manager 
[req-214be154-00fb-4c8a-8fe3-7212ffc19cb2 f0c587f6748346d9a7dd1a6d911da3b4 
60d7922e29e44dc1ac62df3fe7ba3841 - - -] Create loadbalancer 
599a3226-5239-4100-a118-5ad1fe6ea55d failed on device driver haproxy_ns
  2016-05-01 21:40:43.582 6459 ERROR neutron_lbaas.agent.agent_manager 
Traceback (most recent call last):
  2016-05-01 21:40:43.582 6459 ERROR neutron_lbaas.agent.agent_manager   File 
"/usr/lib/python2.7/dist-packages/neutron_lbaas/agent/agent_manager.py", line 
270, in create_loadbalancer

[Yahoo-eng-team] [Bug 1660511] Re: TestVolumeSwap.test_volume_swap fails in cells v1 job waiting for first volume to detach

2017-01-30 Thread Matt Riedemann

** Also affects: devstack
   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/1660511

Title:
  TestVolumeSwap.test_volume_swap fails in cells v1 job waiting for
  first volume to detach

Status in devstack:
  In Progress
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Ever since https://review.openstack.org/#/c/374373/ and
  https://review.openstack.org/#/c/399735/ merged today I've seen at
  least two changes in the gate get bumped out due to the swap volume
  test failing in the cells v1 job, seen here:

  http://logs.openstack.org/06/425806/8/check/gate-tempest-dsvm-cells-
  ubuntu-xenial/ab0bba2/console.html#_2017-01-31_01_48_47_209159

  2017-01-31 01:48:47.209256 | Captured traceback:
  2017-01-31 01:48:47.209267 | ~~~
  2017-01-31 01:48:47.209316 | Traceback (most recent call last):
  2017-01-31 01:48:47.209350 |   File "tempest/test.py", line 99, in wrapper
  2017-01-31 01:48:47.209375 | return f(self, *func_args, **func_kwargs)
  2017-01-31 01:48:47.209404 |   File 
"tempest/api/compute/admin/test_volume_swap.py", line 64, in test_volume_swap
  2017-01-31 01:48:47.209420 | volume1['id'], 'available')
  2017-01-31 01:48:47.209445 |   File "tempest/common/waiters.py", line 
189, in wait_for_volume_status
  2017-01-31 01:48:47.209465 | raise lib_exc.TimeoutException(message)
  2017-01-31 01:48:47.209486 | tempest.lib.exceptions.TimeoutException: 
Request timed out
  2017-01-31 01:48:47.209530 | Details: Volume 
e4fede42-0453-45b0-88c4-5285ca1fbf11 failed to reach available status (current 
detaching) within the required time (196 s).

  It looks like it's also hitting the ceph job:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Volume%5C%22%20AND%20message%3A%5C%22failed%20to%20reach%20available%20status%20(current%20detaching)%20within%20the%20required%20time%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20voting%3A1=7d

  Note that the devstack change to enable the test does not run the ceph
  or cells v1 job in the check queue, so we were likely not going to see
  the failure until AFTER the nova and devstack patches all merged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1660511/+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 1660511] [NEW] TestVolumeSwap.test_volume_swap fails in cells v1 job waiting for first volume to detach

2017-01-30 Thread Matt Riedemann

Public bug reported:

Ever since https://review.openstack.org/#/c/374373/ and
https://review.openstack.org/#/c/399735/ merged today I've seen at least
two changes in the gate get bumped out due to the swap volume test
failing in the cells v1 job, seen here:

http://logs.openstack.org/06/425806/8/check/gate-tempest-dsvm-cells-
ubuntu-xenial/ab0bba2/console.html#_2017-01-31_01_48_47_209159

2017-01-31 01:48:47.209256 | Captured traceback:
2017-01-31 01:48:47.209267 | ~~~
2017-01-31 01:48:47.209316 | Traceback (most recent call last):
2017-01-31 01:48:47.209350 |   File "tempest/test.py", line 99, in wrapper
2017-01-31 01:48:47.209375 | return f(self, *func_args, **func_kwargs)
2017-01-31 01:48:47.209404 |   File 
"tempest/api/compute/admin/test_volume_swap.py", line 64, in test_volume_swap
2017-01-31 01:48:47.209420 | volume1['id'], 'available')
2017-01-31 01:48:47.209445 |   File "tempest/common/waiters.py", line 189, 
in wait_for_volume_status
2017-01-31 01:48:47.209465 | raise lib_exc.TimeoutException(message)
2017-01-31 01:48:47.209486 | tempest.lib.exceptions.TimeoutException: 
Request timed out
2017-01-31 01:48:47.209530 | Details: Volume 
e4fede42-0453-45b0-88c4-5285ca1fbf11 failed to reach available status (current 
detaching) within the required time (196 s).

It looks like it's also hitting the ceph job:

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Volume%5C%22%20AND%20message%3A%5C%22failed%20to%20reach%20available%20status%20(current%20detaching)%20within%20the%20required%20time%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20voting%3A1=7d

Note that the devstack change to enable the test does not run the ceph
or cells v1 job in the check queue, so we were likely not going to see
the failure until AFTER the nova and devstack patches all merged.

** Affects: devstack
 Importance: Undecided
 Assignee: Matt Riedemann (mriedem)
 Status: In Progress

** Affects: nova
 Importance: High
 Status: Confirmed


** Tags: libvirt swap-volume volumes

-- 
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/1660511

Title:
  TestVolumeSwap.test_volume_swap fails in cells v1 job waiting for
  first volume to detach

Status in devstack:
  In Progress
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Ever since https://review.openstack.org/#/c/374373/ and
  https://review.openstack.org/#/c/399735/ merged today I've seen at
  least two changes in the gate get bumped out due to the swap volume
  test failing in the cells v1 job, seen here:

  http://logs.openstack.org/06/425806/8/check/gate-tempest-dsvm-cells-
  ubuntu-xenial/ab0bba2/console.html#_2017-01-31_01_48_47_209159

  2017-01-31 01:48:47.209256 | Captured traceback:
  2017-01-31 01:48:47.209267 | ~~~
  2017-01-31 01:48:47.209316 | Traceback (most recent call last):
  2017-01-31 01:48:47.209350 |   File "tempest/test.py", line 99, in wrapper
  2017-01-31 01:48:47.209375 | return f(self, *func_args, **func_kwargs)
  2017-01-31 01:48:47.209404 |   File 
"tempest/api/compute/admin/test_volume_swap.py", line 64, in test_volume_swap
  2017-01-31 01:48:47.209420 | volume1['id'], 'available')
  2017-01-31 01:48:47.209445 |   File "tempest/common/waiters.py", line 
189, in wait_for_volume_status
  2017-01-31 01:48:47.209465 | raise lib_exc.TimeoutException(message)
  2017-01-31 01:48:47.209486 | tempest.lib.exceptions.TimeoutException: 
Request timed out
  2017-01-31 01:48:47.209530 | Details: Volume 
e4fede42-0453-45b0-88c4-5285ca1fbf11 failed to reach available status (current 
detaching) within the required time (196 s).

  It looks like it's also hitting the ceph job:

  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Volume%5C%22%20AND%20message%3A%5C%22failed%20to%20reach%20available%20status%20(current%20detaching)%20within%20the%20required%20time%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20voting%3A1=7d

  Note that the devstack change to enable the test does not run the ceph
  or cells v1 job in the check queue, so we were likely not going to see
  the failure until AFTER the nova and devstack patches all merged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1660511/+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 1647855] Re: Page title not updated in AngularJS based Panels

Reviewed:  https://review.openstack.org/414812
Committed: 
https://git.openstack.org/cgit/openstack/ui-cookiecutter/commit/?id=befdbc96f12b5610f23158c8f289a1ade27b1fdc
Submitter: Jenkins
Branch:master

commit befdbc96f12b5610f23158c8f289a1ade27b1fdc
Author: Shu Muto 
Date:   Mon Dec 26 13:01:52 2016 +0900

Set reasonable name to browser title bar

Currently, when using anuglar table, the name of title bar on
browser is always "Horizon - OpenStack Dashboard".
It's not good at point of view of usability.
This patch fix it.

Change-Id: I77ff241b2354a620197cb3125f4f0d4544d08da8
Closes-Bug: #1647855


** Changed in: ui-cookiecutter
   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/1647855

Title:
  Page title not updated in AngularJS based Panels

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Magnum UI:
  Fix Released
Status in UI Cookiecutter:
  Fix Released
Status in Zun-UI:
  Fix Released

Bug description:
  How to reproduce:
  1. Go to Project->Images or Admin->Images or enable a new angularjs-based 
panel (e.g. admin->flavors).
  2. See the Page Title  is "Horizon - OpenStack Dashboard"

  Expected result:
  The page title should read the panel title as the user moves between panels, 
this title is tipically the same as the content of an h1 inside of 
div.panel-header.

  Actual result:
  The title reads "Horizon - OpenStack Dashboard". If the user has 20 tabs 
opened then good luck finding a tab - cannot distinguish by the title!

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1647855/+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 1643017] Re: libvirtError: block copy still active: disk 'vdb' not ready for pivot yet

Reviewed:  https://review.openstack.org/399735
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=9ed782641970dd371adc151e7d3913a402369dd3
Submitter: Jenkins
Branch:master

commit 9ed782641970dd371adc151e7d3913a402369dd3
Author: Lee Yarwood 
Date:   Mon Nov 21 11:30:01 2016 +

libvirt: Use the mirror element to detect job completion

The mirror element was introduced in Libvirt 0.10.0 [1] and provides a
ready attribute that helps to determine when a blockjob is complete.
This is now used in addition to checking the progress of a given
blockjob to ensure Nova waits until these jobs complete fully.

[1] 
https://libvirt.org/git/?p=libvirt.git;a=commit;h=ae6aa8c3965e9aaa245b8e669c6324d44312ac1b

Closes-bug: #1643017
Change-Id: I0c52917aa70c4973f37dea1aebf878dd73b4


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

Title:
  libvirtError: block copy still active: disk 'vdb' not ready for pivot
  yet

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  This is an additional corner case for swap_volume not covered by
  bug#1630600.

  The following failure is taken from the devstack change enabling the
  new swap_volume tempest test :

  tempest: configure compute-feature-enabled.swap_volume if libvirt
  https://review.openstack.org/#/c/374373/

  http://logs.openstack.org/73/374373/3/check/gate-tempest-dsvm-neutron-
  full-ubuntu-
  xenial/961698c/logs/screen-n-cpu.txt.gz#_2016-11-18_16_11_39_759

  2016-11-18 16:11:39.759 4511 ERROR root [req-f40054e1-f18d-478a-
  ae14-9c738bb961f2 tempest-TestVolumeSwap-1057055027 tempest-
  TestVolumeSwap-1057055027] Original exception being dropped:
  ['Traceback (most recent call last):\n', '  File
  "/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 1228, in
  _swap_volume\ndev.abort_job(pivot=True)\n', '  File
  "/opt/stack/new/nova/nova/virt/libvirt/guest.py", line 647, in
  abort_job\nself._guest._domain.blockJobAbort(self._disk,
  flags=flags)\n', '  File "/usr/local/lib/python2.7/dist-
  packages/eventlet/tpool.py", line 186, in doit\nresult =
  proxy_call(self._autowrap, f, *args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 144,
  in proxy_call\nrv = execute(f, *args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 125,
  in execute\nsix.reraise(c, e, tb)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 83,
  in tworker\nrv = meth(*args, **kwargs)\n', '  File
  "/usr/local/lib/python2.7/dist-packages/libvirt.py", line 739, in
  blockJobAbort\nif ret == -1: raise libvirtError
  (\'virDomainBlockJobAbort() failed\', dom=self)\n', "libvirtError:
  block copy still active: disk 'vdb' not ready for pivot yet\n"]

  As discussed in bug#1630600 and at length in RHBZ#1382165 the issue
  here is that QEMU reports the progress of the block job as complete
  (status.cur == status.end) _before_ updating the ready field of the
  block job. This causes the following attempt to pivot to fail.

  Nova should attempt to use the ready field of the block job when
  available (libvirt >1.2.18) to ensure that we are able to pivot.

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

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

[Yahoo-eng-team] [Bug 1629133] Re: New neutron subnet pool support breaks multinode testing.

2017-01-30 Thread Thomas Morin

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

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

Title:
  New neutron subnet pool support breaks multinode testing.

Status in networking-bgpvpn:
  Fix Released
Status in devstack:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  New
Status in neutron:
  Incomplete
Status in OpenStack DBaaS (Trove):
  In Progress

Bug description:
  The new subnet pool support in devstack breaks multinode testing bceause it 
results in the route for 10.0.0.0/8 being set to via br-ex when the host has 
interfaces that are actually on 10 nets and that is where we need the routes to 
go out. Multinode testing is affected because it uses these 10 net addresses to 
run the vxlan overlays between hosts.
  For many years devstack-gate has set FIXED_RANGE to ensure that the networks 
devstack uses do not interfere with the underlying test host's networking. 
However this setting was completely ignored when setting up the subnet pools.

  I think the correct way to fix this is to use a much smaller subnet
  pool range to avoid conflicting with every possible 10.0.0.0/8 network
  in the wild, possibly by defaulting to the existing FIXED_RANGE
  information. Using the existing information will help ensure that
  anyone with networks in 10.0.0.0/8 will continue to work if they have
  specified a range that doesn't conflict using this variable.

  In addition to this we need to clearly document what this new stuff in
  devstack does and how people can work around it should they conflict
  with the new defaults we end up choosing.

  I have proposed https://review.openstack.org/379543 which mostly works
  except it fails one tempest test that apparently depends on this new
  subnet pool stuff. Specifically the V6 range isn't large enough aiui.

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

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

[Yahoo-eng-team] [Bug 1629861] Re: L3: missing registry callback notification at Router Interface creation

2017-01-30 Thread Thomas Morin

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

** Changed in: bgpvpn
   Importance: Undecided => Medium

** Changed in: bgpvpn
 Assignee: (unassigned) => Thomas Morin (tmmorin-orange)

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

Title:
  L3: missing registry callback notification at Router Interface
  creation

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

Bug description:
  The code triggering a ROUTER_INTERFACE AFTER_CREATE registry
  notification is not ran if the Router to which an interface is added
  has no gateway connected.

  [1]
  
https://github.com/openstack/neutron/blob/930655cf57de523181b2d59bb4428b9f23991cce/neutron/db/l3_dvr_db.py#L427
  )

  This behavior is problematic for components that need to rely on this
  functionality, and not consistent with what the non-DVR code does [2].

  [2]
  
https://github.com/openstack/neutron/blob/f4ba9ea8ac18fabac80cb0443bc18d9f950482b3/neutron/db/l3_db.py#L815

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1629861/+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 1660449] [NEW] Lack of some methods calling information in OpenStack Profiler page

2017-01-30 Thread Lingxian Kong

Public bug reported:

Branch: ocata
Only changed keystone configuration in local_settings.py, configuration for 
profiler_settings:

OPENSTACK_PROFILER.update({
'enabled': True,
'keys': ['SECRET_KEY'],
'notifier_connection_string': 'mongodb://192.168.200.50:27017',
'receiver_connection_string': 'mongodb://192.168.200.50:27017'
})

The MongoDB works fine.

After enabling 'OpenStack Profiler', I clicked 'Access & Security'
panel, the total time that chrome told me was a big different with what
i saw in the profiler page.  i checked the code, some methods with
'profiler.trace' decorator are not included in the profiler page, e.g.
tenant_quota_usages. an example is here:
http://pasteboard.co/sr4VFgkSK.png

** Affects: horizon
 Importance: Medium
 Status: Triaged

-- 
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/1660449

Title:
  Lack of some methods calling information in OpenStack Profiler page

Status in OpenStack Dashboard (Horizon):
  Triaged

Bug description:
  Branch: ocata
  Only changed keystone configuration in local_settings.py, configuration for 
profiler_settings:

  OPENSTACK_PROFILER.update({
  'enabled': True,
  'keys': ['SECRET_KEY'],
  'notifier_connection_string': 'mongodb://192.168.200.50:27017',
  'receiver_connection_string': 'mongodb://192.168.200.50:27017'
  })

  The MongoDB works fine.

  After enabling 'OpenStack Profiler', I clicked 'Access & Security'
  panel, the total time that chrome told me was a big different with
  what i saw in the profiler page.  i checked the code, some methods
  with 'profiler.trace' decorator are not included in the profiler page,
  e.g. tenant_quota_usages. an example is here:
  http://pasteboard.co/sr4VFgkSK.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1660449/+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 1660444] [NEW] Glance stable/mitaka docs cannot be built

2017-01-30 Thread Ian Cordasco

Public bug reported:

The Glance stable/mitaka docs job has been failing consistently for over
a week now. An example of a failure is here: http://logs.openstack.org
/periodic-stable/periodic-glance-docs-mitaka/384794b/

(Quoted below for posterity)

2017-01-30 06:10:21.562396 | Installing collected packages: six, pep8, pbr, 
pyflakes, mccabe, flake8, hacking, pytz, Babel, PyYAML, stevedore, smmap2, 
gitdb2, GitPython, bandit, coverage, extras, python-mimeparse, linecache2, 
traceback2, argparse, unittest2, testtools, fixtures, mox3, funcsigs, mock, 
Pygments, docutils, MarkupSafe, Jinja2, sphinx, requests, python-subunit, 
testrepository, testresources, testscenarios, psutil, requestsexceptions, 
wrapt, positional, iso8601, keystoneauth1, appdirs, os-client-config, 
debtcollector, oslotest, PyMySQL, psycopg2, pysendfile, qpid-python, pycparser, 
cffi, xattr, futures, python-swiftclient, oslosphinx, dulwich, reno
2017-01-30 06:10:21.562433 |   Found existing installation: six 1.10.0
2017-01-30 06:10:21.562461 | Uninstalling six-1.10.0:
2017-01-30 06:10:21.562495 |   Successfully uninstalled six-1.10.0
2017-01-30 06:10:21.562524 |   Rolling back uninstall of six
2017-01-30 06:10:21.562542 | Exception:
2017-01-30 06:10:21.562573 | Traceback (most recent call last):
2017-01-30 06:10:21.562659 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/basecommand.py",
 line 215, in main
2017-01-30 06:10:21.562691 | status = self.run(options, args)
2017-01-30 06:10:21.562779 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/commands/install.py",
 line 342, in run
2017-01-30 06:10:21.562808 | prefix=options.prefix_path,
2017-01-30 06:10:21.562895 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/req/req_set.py",
 line 784, in install
2017-01-30 06:10:21.562915 | **kwargs
2017-01-30 06:10:21.563004 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/req/req_install.py",
 line 851, in install
2017-01-30 06:10:21.563052 | self.move_wheel_files(self.source_dir, 
root=root, prefix=prefix)
2017-01-30 06:10:21.563147 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/req/req_install.py",
 line 1064, in move_wheel_files
2017-01-30 06:10:21.563174 | isolated=self.isolated,
2017-01-30 06:10:21.563263 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/wheel.py",
 line 247, in move_wheel_files
2017-01-30 06:10:21.563286 | prefix=prefix,
2017-01-30 06:10:21.563377 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pip/locations.py",
 line 140, in distutils_scheme
2017-01-30 06:10:21.563407 | d = Distribution(dist_args)
2017-01-30 06:10:21.563494 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/setuptools/dist.py",
 line 320, in __init__
2017-01-30 06:10:21.563527 | _Distribution.__init__(self, attrs)
2017-01-30 06:10:21.563575 |   File "/usr/lib/python2.7/distutils/dist.py", 
line 287, in __init__
2017-01-30 06:10:21.563628 | self.finalize_options()
2017-01-30 06:10:21.563722 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/setuptools/dist.py",
 line 386, in finalize_options
2017-01-30 06:10:21.563759 | ep.require(installer=self.fetch_build_egg)
2017-01-30 06:10:21.563850 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 2318, in require
2017-01-30 06:10:21.563914 | items = working_set.resolve(reqs, env, 
installer, extras=self.extras)
2017-01-30 06:10:21.563998 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 862, in resolve
2017-01-30 06:10:21.564036 | new_requirements = 
dist.requires(req.extras)[::-1]
2017-01-30 06:10:21.564121 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 2562, in requires
2017-01-30 06:10:21.564150 | dm = self._dep_map
2017-01-30 06:10:21.564235 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 2809, in _dep_map
2017-01-30 06:10:21.564270 | self.__dep_map = self._compute_dependencies()
2017-01-30 06:10:21.564362 |   File 
"/home/jenkins/workspace/periodic-glance-docs-mitaka/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 2818, in _compute_dependencies
2017-01-30 06:10:21.564406 | for req in

[Yahoo-eng-team] [Bug 1660436] [NEW] Federated users cannot log into horizon

2017-01-30 Thread Colleen Murphy

Public bug reported:

As of this bugfix in novaclient, federated users cannot log in to
horizon:

https://bugs.launchpad.net/python-novaclient/+bug/1658963

Before this bugfix, horizon would attempt to list nova extensions using
what was apparently the wrong class, and the error would be caught and
quietly logged as such:

 Call to list supported extensions failed. This is likely due to a
problem communicating with the Nova endpoint. Host Aggregates panel will
not be displayed.

The dashboard would display:

 Error: Unable to retrieve usage information.

but at least the user was logged into the dashboard.

The error that was being hidden was:

 __init__() takes at least 3 arguments (2 given)

Now that that is fixed, horizon makes it further but fails to
authenticate the federated user when attempting this request, giving the
traceback here:

 http://paste.openstack.org/show/596929/

The problem lies somewhere between keystoneauth, novaclient, and
horizon.

keystoneauth:

When keystoneauth does version discovery, it first tries the Identity
v2.0 API, and finding no domain information in the request, returns that
API as the Identity endpoint. Modifying keystoneauth to not stop there
and continue trying the v3 API, even though it lacks domain information,
allows the user to successfully log in:

 http://paste.openstack.org/show/596930/

I'm not really sure why that works or what would break with that change.

novaclient:

When creating a Token plugin the novaclient is aware of a project's
domain but not of a domain on its own or of a default domain:

 http://git.openstack.org/cgit/openstack/python-
novaclient/tree/novaclient/client.py#n137

keystoneauth relies on having default_domain_(id|name),
domain_(id|name), or project_domain(id|name) set, and novaclient isn't
receiving information about the project_domain(id|name) and isn't
capable of sending any other domain information when using the Token
plugin, which it must for a federated user.

horizon:

For federated users novaclient is only set up to pass along domain info
for the project, which horizon doesn't store in its user object:

http://git.openstack.org/cgit/openstack/django_openstack_auth/tree/openstack_auth/user.py#n202

However things seem to just work if we fudge the user_domain_id as the
project_domain_id, though that is obviously not a good solution:

 http://paste.openstack.org/show/596933/

** Affects: horizon
 Importance: Undecided
 Status: New

** Affects: keystoneauth
 Importance: Undecided
 Status: New

** Affects: python-novaclient
 Importance: Undecided
 Status: New

** Also affects: python-novaclient
   Importance: Undecided
   Status: New

** Also 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/1660436

Title:
  Federated users cannot log into horizon

Status in OpenStack Dashboard (Horizon):
  New
Status in keystoneauth:
  New
Status in python-novaclient:
  New

Bug description:
  As of this bugfix in novaclient, federated users cannot log in to
  horizon:

  https://bugs.launchpad.net/python-novaclient/+bug/1658963

  Before this bugfix, horizon would attempt to list nova extensions
  using what was apparently the wrong class, and the error would be
  caught and quietly logged as such:

   Call to list supported extensions failed. This is likely due to a
  problem communicating with the Nova endpoint. Host Aggregates panel
  will not be displayed.

  The dashboard would display:

   Error: Unable to retrieve usage information.

  but at least the user was logged into the dashboard.

  The error that was being hidden was:

   __init__() takes at least 3 arguments (2 given)

  Now that that is fixed, horizon makes it further but fails to
  authenticate the federated user when attempting this request, giving
  the traceback here:

   http://paste.openstack.org/show/596929/

  The problem lies somewhere between keystoneauth, novaclient, and
  horizon.

  keystoneauth:

  When keystoneauth does version discovery, it first tries the Identity
  v2.0 API, and finding no domain information in the request, returns
  that API as the Identity endpoint. Modifying keystoneauth to not stop
  there and continue trying the v3 API, even though it lacks domain
  information, allows the user to successfully log in:

   http://paste.openstack.org/show/596930/

  I'm not really sure why that works or what would break with that
  change.

  novaclient:

  When creating a Token plugin the novaclient is aware of a project's
  domain but not of a domain on its own or of a default domain:

   http://git.openstack.org/cgit/openstack/python-
  novaclient/tree/novaclient/client.py#n137

  keystoneauth relies on having default_domain_(id|name),
  domain_(id|name), or project_domain(id|name) set, and novaclient isn't
  receiving

[Yahoo-eng-team] [Bug 1354694] Re: useradd crashes if group list contains whitespace

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1354694

Title:
  useradd crashes if group list contains whitespace

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A specific usage of user data to cloud-init will fail to add a user.

  This cloud-config:
    #cloud-config
    users:
  - default
  - name: foobar
    gecos: "My User"
    groups: sudo, adm

  Will fail with information in the cloud-init log showing:
  2016-12-19 21:39:32,713 - util.py[WARNING]: Failed to create group  adm
  2016-12-19 21:39:32,713 - util.py[DEBUG]: Failed to create group  adm
  Traceback (most recent call last):
  ...
  cloudinit.util.ProcessExecutionError: Unexpected error while running command.
  Command: ['groupadd', ' adm']
  Exit code: 3
  Reason: -
  Stdout: ''
  Stderr: "groupadd: ' adm' is not a valid group name\n"

  While changing the last line to the following would work:
    groups: [sudo, adm]

  [Test Case]
  $ cat > user-data <<"EOF"
  #cloud-config
  users:
    - default
    - name: foobar
  gecos: "My User"
  groups: sudo, adm
    - name: wark
  groups: [sudo, adm]
  EOF

  $ release=yakkety
  $ name="$release-1354694"

  $ lxc launch "ubuntu-daily:$release" "$name" \
   "--config=user.user-data=$(cat user-data)"

  $ sleep 10

  ## Check foobar is in expected groups
  $ lxc exec $name -- groups foobar
  foobar : foobar adm sudo

  $ lxc exec $name -- groups wark
  wark : wark adm sudo

  $ lxc exec $name -- grep WARN /var/log/cloud-init.log || echo "no warn"
  no warn

  [Regression Potential]
  There are 3 changes in this commit
  a.) if 'groups' entry is a string, split on "," and strip pieces
  The most likely path to failure here is if previously a non-string
  (possibly bytes) was being passed in and now will be ignored.
  That seems unlikely and clearly wrong input.

  b.) fix and unit tests to explicitly set system=False or no_create_home=True.
  Previously those paths did not test the value of the entry, only the
  presense of the entry.
  This meant that these 2 configs were the same:
    users: {name: bob, system: True}
  and
    users: {name: bob, system: False}

  That bug is fixed here so that 'system: False' is just explicitly
  disabling the '--system' flag to adduser.

  c.) debug message cleanup:

     LOG.debug("created group %s for user %s", name, group)
     LOG.debug("created group '%s' for user '%s'", group, name)

  [Other Info]
  Upstream commit at
    
https://git.launchpad.net/cloud-init/commit/?id=ca3ae67211d907b4cfdcd685c0ae4f9530cb7da1

  === End SRU Template ===

  See downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1126365

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1354694/+subscriptions

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

[Yahoo-eng-team] [Bug 1625766] Re: Fallback networking doesn't handle IOError when reading sys/net//carrier

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1625766

Title:
  Fallback networking doesn't handle IOError when reading
  sys/net//carrier

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  Sometimes reading from /sys/class/net//carrier returns an error
  and is unhangled causing fallback networking to not bring anything up.

  
  [Original Description]

  I am running Arch on a KVM vps provider. I installed using this
  template: Arch Linux 2016.03 64-bit (template). Everything was working
  fine until I decided to upgrade. I did pacman -Syu and everything
  upgraded without error until it restarted.

  I had to manually install certain python packages. But, I kept getting
  more errors so I joined IRC.

  Here's the log: https://irclogs.ubuntu.com/2016/09/20/%23cloud-
  init.html

  Was told to post it Here to sum up everything

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1625766/+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 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1460715

Title:
  MBR disk setup fails because sfdisk no longer accepts M as a valid
  unit

Status in cloud-init:
  Fix Released
Status in Ubuntu Image:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init has function to partition disks on devices.
  Creating partitions on a disk no longer works with sfdisk as recent versions 
of
  sfdisk no accept the unit 'M' as input, this function is broken.

  [Test Case]
  1. Launch an instance with provided user-data

     On Azure, this will work:
   #cloud-config
   disk_setup:
     ephemeral0:
     table_type: mbr
     layout: [66, [33, 82]]
     overwrite: True
   fs_setup:
     - device: ephemeral0.1
   filesystem: ext4
     - device: ephemeral0.2
   filesystem: swap
   mounts:
     - ["ephemeral0.1", "/mnt2"]
     - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

     On a typical kvm openstack use:
   #cloud-config
   disk_setup:
     /dev/vdb:
     table_type: mbr
     layout: [66, [33, 82]]
     overwrite: True
   fs_setup:
     - device: /dev/vdb1
   filesystem: ext4
     - device: /dev/vdb2
   filesystem: swap
   mounts:
     - ["/dev/vdb1", "/mnt2"]
     - ["/dev/vdb2", "none", "swap", "sw", "0", "0"]

  2. Add proposed, update, and reboot as fresh instance.

     # enable proposed
     echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main 
| sudo tee /etc/apt/sources.list.d/proposed.list
     sudo apt-get -qy update && sudo apt-get -qy install cloud-init https://bugs.launchpad.net/cloud-init/+bug/1460715/+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 1643990] Re: cloud-init-local.service messages not written to /var/log/cloud-init.log in systemd

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1643990

Title:
  cloud-init-local.service messages not written to /var/log/cloud-
  init.log in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Triaged
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  Cloud-init's logging is inconsistent due to availability of syslog during
  boot.

  Cloud-init logs to /var/log/cloud-init.log by default.  It does this in
  a way that was originally designed to prefer to use syslog if it was
  available, and then fall back to writing directly to that file.

  Over time this has been shown to be problematic.
  a.) it relied on syslog during boot, and on some distros it wasn't
  present.
  b.) sometimes it would not be available during cloud-init-local.service
  and then would be during cloud-init.service.  The result was that
  the log would have two different time stamp formats (one written
  by rsyslog and one by python logging).
  c.) if rsyslog was used, micro seconds were not included in the log.
  d.) since the move to systemd, there has even been times when cloud-init's
  attempt to determine if syslog was available would false-positive.
  that would result logging not being written to the file at all.

  Over all, the complexity was just not found to worth the benefit.

  [Test Case]
* Launch an instance.
* Look at /var/log/cloud-init.log.
  on start, the cloud-int process logs a message like
'Cloud-init v 0.7.8 running'
  Look at those messages specifically.  In the example here (lxd), neither
  cloud-init.service or cloud-init-local.service successfully logged at all.

  # grep Cloud-init /var/log/cloud-init.log 
  Dec  2 18:06:56 y2 [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.8 
running 'modules:config' at Fri, 02 Dec 2016 18:06:56 +. Up 5.0 seconds.
  Dec  2 18:06:58 y2 [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.8 
running 'modules:final' at Fri, 02 Dec 2016 18:06:58 +. Up 7.0 seconds.
  Dec  2 18:06:58 y2 [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.8 
finished at Fri, 02 Dec 2016 18:06:58 +. Datasource DataSourceNoCloud 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 7.0 seconds

* update to proposed, cleanup reboot
  # enable propose and update
  # cleanup

  sudo rm -Rf /var/log/cloud-init* /var/lib/cloud/
  sudo reboot
  
* login again and look.

  This time, all messages will have the format:
 2016-12-02 17:58:43,175 - util.py[DEBUG]: Cloud-init v. 0.7.8 running 
'init-local' at Fri, 02 Dec 2016 17:58:43 +. Up 13.73 seconds.

  And you will have one for each 'init-local', 'init', 'modules:config' and
  modules:final.

  [Regression Potential] 
  Users relying on cloud-init writing entries to syslog will lose that.

  [Other Info]

  === End SRU Template ===

  
  output of cloud-init-local.service can get lost in systemd.
  The result is that there is no output in /var/log/cloud-init.log from

[Yahoo-eng-team] [Bug 1647708] Re: Ephemeral disk on xenial is not mounted at boot

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1647708

Title:
  Ephemeral disk on xenial is not mounted at boot

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  An ephemeral disk will not correctly be mounted on /mnt.
  This affects Azure and other instances where an ephemeral device is
  mounted by default on /mnt.  It is recreated in Azure and on OpenStack.

  This can be mitigated by either:
   1.) mount -a
   2.) reboot

  [Test Case]
  In a correctly functioning image on OpenStack or Azure, you should be
  able to:

  1.) Launch an instance
  2.) ssh into instance and look around
 $ awk '$2 == "/mnt" { print $0 }' /etc/fstab
 /dev/vdb /mnt  auto  
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig  0  2
 $ awk '$2 == "/mnt" { print $0 }' /proc/mounts
  /dev/vdb /mnt vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
 0 0

 $ df -h /mnt
 Filesystem  Size  Used Avail Use% Mounted on
 /dev/vdb 40G   32K   40G   1% /mnt

  To check that this is functional with -proposed, after you've seen it
  failed

  3.) enable -proposed and apt-get install cloud-init
  4.) clean up and reboot as if fresh:
  sudo rm -Rf /var/lib/cloud /var/log/cloud-init
  sudo sed -i '/cloudconfig/d' /etc/fstab
  sudo reboot

  [Regression Potential]
  This is a regression caused by bug 1611074, so in addition to the above
  test case, we should go through the test cases shown there to see that
  those also work.
  === End SRU Template ===


  When I boot the latest xenial Azure image (containing cloud-init
  0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end
  up mounted (though it is formatted appropriately).  Restarting the
  mnt.mount service does mount it, which suggests there is an issue in
  the ordering of the services at boot.

  $ mount | grep mnt
  $ sudo systemctl status mnt.mount
  ● mnt.mount - /mnt
     Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
     Active: inactive (dead)
  Where: /mnt
   What: /dev/disk/cloud/azure_resource-part1
   Docs: man:fstab(5)
     man:systemd-fstab-generator(8)
  $ sudo journalctl -u mnt.mount
  -- No entries --
  $ cat /etc/fstab
  # CLOUD_IMG: This file was created/modified by the Cloud Image build process
  UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 /ext4   
defaults,discard0 0
  /dev/disk/cloud/azure_resource-part1  /mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  $ sudo systemctl restart mnt.mount
  $ mount | grep mnt
  /dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
  $ ls /mnt/
  lost+found
  $ sudo systemctl status mnt.mount
  ● mnt.mount - /mnt
     Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
     Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
  Where: /mnt

[Yahoo-eng-team] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

Status in cloud-init:
  Fix Released
Status in MAAS:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  On a system booted with both ip6= and ip= on the kernel command line
  cloud-init will raise an exception and fail to process user-data and
  have its normal affect on boot.

  That is because cloud-init previously raised an exception when more
  than one file in /run/net*.conf declared the same DEVICE.  Changes to
  isc-dhcp and initramfs-tools have changed their behavior and cloud-init
  has to adjust to allow DEVICE6= and DEVICE= in separate files.

  [Test Case]
  Boot a system on a network with both ipv4 and ipv6 dhcp servers,
  and pass kernel command line with:
    ip=dhcp ip6=dhcp

  [Regression Potential]
  Regression seems unlikely as this is relaxing a check.  Where previously
  an exception would have been raised, cloud-init will now go on.

  So it seems most likely, something that didn't work before (due to raised
  exception) would now still not work, but with failures.  That is not
  expected, but that would likely be where regressions were found.

  === End SRU Template ===

  In changes made under bug 1621615 (specifically a1cdebdea), we now
  expect that there may be a 'ip6=' argument on the kernel command line.
  The changes made did not test the case where there is 'ip6=' and no
  'ip='.

  The code currently will return with no network configuration found if
  there is only ip6=...

  Related bugs:
   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+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 1648380] Re: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1648380

Title:
  cloud-init fails to find CloudSigma datasource with cloud-init
  0.7.8-1-g3705bb5-0ubuntu1

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Without this fix, images built with cloud-init 0.7.8-1-g3705bb5-0ubuntu1  and 
later will not correctly boot and become unreachable

  [Impact]
  Some cloud images built with this version of cloud-init may become unusable

  [Fix]
  Reinstate the second element of the datasources list as a tuple instead of a 
string.

  [Test Case]
  This test must be done on CloudSigma to complete correctly :

  Build cloud image with only the CloudSigma datasource using cloud-init 
version 0.7.8-1-g3705bb5-0ubuntu1 or later
  Launch an instance with this image
  The instance will boot but will not be accessible through ssh

  With this fix,the instance will complete its boot sequence and be
  accessible through ssh

  [Regression]
  None expected, the second element was a tuple in previous versions of the 
CloudSigma datasource

  [Description of the problem]
  The issue materialized itself on cloud instances launched with such images 
that became unreachable through SSH with the following message:

  "Connection closed by {IP} port 22"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1648380/+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 1644043] Re: Read Kernel Config tests missing MAC Address

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1~16.10.1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
into patches in debian/patches.
  * New upstream snapshot.
- mounts: use mount -a again to accomplish mounts (LP: #1647708)
- CloudSigma: Fix bug where datasource was not loaded in local search.
  (LP: #1648380)
- when adding a user, strip whitespace from group list
  [Lars Kellogg-Stedman] (LP: #1354694)
- fix decoding of utf-8 chars in yaml test
- Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
- fix problems found in python2.6 test.
- OpenStack: extend physical types to include hyperv, hw_veb, vhost_user.
  (LP: #1642679)
- tests: fix assumptions that expected no eth0 in system. (LP: #1644043)
- net/cmdline: Consider ip= or ip6= on command line not only ip=
  (LP: #1639930)
- Just use file logging by default [Joshua Harlow] (LP: #1643990)
- Improve formatting for ProcessExecutionError [Wesley Wiedenmeier]
- flake8: fix trailing white space
- Doc: various documentation fixes [Sean Bright]
- cloudinit/config/cc_rh_subscription.py: Remove repos before adding
  [Brent Baude]
- packages/redhat: fix rpm spec file.
- main: set TZ in environment if not already set. [Ryan Harper]
- disk_setup: Use sectors as unit when formatting MBR disks with sfdisk.
  [Daniel Watkins] (LP: #1460715)

 -- Scott Moser   Mon, 19 Dec 2016 15:07:12 -0500

** Changed in: cloud-init (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 cloud-init.
https://bugs.launchpad.net/bugs/1644043

Title:
  Read Kernel Config tests missing MAC Address

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  http://pad.lv/1644043
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1644043
  
  === Begin SRU Template ===
  [Impact] 
  Unit tests would fail, causing build failure.

  [Test Case]
  Run cloud-init tests a system with a network device named 'eth0'
  Building cloud-init runs the unit tests, so even just building on
  such a system is sufficient.

  lxc provides such an environment.

  Generally, the build worked, so unit tests passed.

  [Regression Potential] 
  None: unit test changes only.

  === End SRU Template ===

  
  Unittests are broken [1] preventing cloud-init from building currently. The 
issue is the kernel config tests are looking for a MAC address that is not 
there.

  [1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-
  lts/35/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1644043/+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 1657450] Re: a wrong indentation in openstack_dashboard/api/base.py:206

Reviewed:  https://review.openstack.org/421886
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=60db0269e08b4129f0c98ee83f0a283bca31abd1
Submitter: Jenkins
Branch:master

commit 60db0269e08b4129f0c98ee83f0a283bca31abd1
Author: liaozd 
Date:   Wed Jan 18 20:58:45 2017 +0800

wrong indentations

Change-Id: I967fbe1e1e92851f1ca330cf43b00fc1d65e5b36
Closes-Bug: 1657450


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

Title:
  a wrong indentation in openstack_dashboard/api/base.py:206

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  a wrong indentation in openstack_dashboard/api/base.py:206

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1657450/+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 1658048] Re: The generated apache configuration does not spawn enough processes and this can lead to a stalling server (potential DoS)

Reviewed:  https://review.openstack.org/423202
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=600620a8d50fc13f7a9cc4901b0307d09039e7bb
Submitter: Jenkins
Branch:master

commit 600620a8d50fc13f7a9cc4901b0307d09039e7bb
Author: Yves-Gwenael Bourhis 
Date:   Fri Jan 20 11:49:34 2017 +0100

Configuring number of apache processes

By default apache spawns only one process for the wsgi app if not specified.
This patch detects the number of CPUS to configure n CPUs +1 processes by
default and allows to specify the number of processes explicitly.

Change-Id: I684ecd15193cef169d7a86f66a47b7d1d76c1c24
Closes-Bug: #1658048


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

Title:
  The generated apache configuration does not spawn enough processes and
  this can lead to a stalling server (potential DoS)

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When creating the apache configuration with:

   python manage.py make_web_conf --apache

  The apache configuration file does not specify the number of apache processes.
  By default apache will spawn only one. not only is it a performance issue, 
but it can lead to Denial of Service if the apache process is to long to 
respond or stalled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1658048/+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 1657454] Re: use safer method splitlines() to replace split('\n')

Reviewed:  https://review.openstack.org/421998
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=d2ec7d3d187815619170d054d7ff47744aceb2ac
Submitter: Jenkins
Branch:master

commit d2ec7d3d187815619170d054d7ff47744aceb2ac
Author: liaozd 
Date:   Wed Jan 18 21:16:52 2017 +0800

use safer method splitlines() to replace split('\n')

user may copy/paste content from a file created in Windows,
the line breaks are different in between win/unix/mac,
`splitlines()` is better and safer than `split('\n')`

Change-Id: I969b8b6b9de90f5eae6f2684623ec6db0014b05e
Closes-Bug: 1657454


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

Title:
  use safer method splitlines() to replace split('\n')

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  user may copy/paste content from a txt file created in Windows, line
  breaks are different, splitlines() method is better and safer than
  split('\n')

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1657454/+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 1652344] Re: Allow keystone v3 in the designate driver

Based on what I'm seeing, we should update [1] to include the ability to
keystone v3 in the [designate] config. See change for more details.

Moving this to openstack-manuals as I don't see any docs in the neutron
repo that need updating as a part of this.

[1]
http://docs.openstack.org/newton/networking-guide/config-dns-int.html#configuring-openstack-networking-for-integration-with-an-external-dns-service

** Project changed: neutron => openstack-manuals

** Changed in: openstack-manuals
Status: Confirmed => New

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

Title:
Allow keystone v3 in the designate driver

Status in openstack-manuals:
New

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

commit 91d048dbde83a52f43aceebaf1b1e1ef0937602d
Author: Gyorgy Szombathelyi
Date: Wed Nov 16 14:37:38 2016 +0100

Allow keystone v3 in the designate driver

Using the loader from keystoneauth1, it is possible to easily use
keystone v3 options in [designate].
For the end user, it means she/he must specify designate.auth_type,
then she/he can specify an Keystone v3 endpoint in designate.auth_url.

Change-Id: I8bb02f11e60767dacdf6ac852979cfa82de1e08b
Closes-bug: #1585976
DocImpact

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1652344/+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 1649720] Re: DSCP packet marking support in Linuxbridge agent

I agree with comment #1 and I didn't find any direct refs to the agent
and DSCP other than a generic reference about DSCP in [1].

However to be on the safe side I'm moving to openstack-manuals in case
there's a ref or work in progress I'm missing; otherwise it can safely
be closed out as invalid IMO.

[1] http://docs.openstack.org/newton/networking-guide/config-qos.html
#supported-qos-rule-types

** Project changed: neutron => openstack-manuals

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

Title:
  DSCP packet marking support in Linuxbridge agent

Status in openstack-manuals:
  New

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

  commit fd3bf3327cada36ef57eefebabc78a112298be8d
  Author: Sławek Kapłoński 
  Date:   Wed Nov 23 22:14:30 2016 +

  DSCP packet marking support in Linuxbridge agent
  
  Linuxbridge agent uses iptable rules in POSTROUTING chain
  in the mangle table to mark outgoing packets with the
  DSCP mark value configured by the user in QoS policy.
  
  DocImpact: DSCP Marking rule support is extended to the
 Linuxbridge L2 agent
  
  Closes-Bug: #1644369
  
  Change-Id: I47e44cb2e67ab73bd5ee0aa4cca47cb3d07e43f3

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1649720/+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 1660385] [NEW] Alert user of Ec2 Datasource on lookalike cloud

2017-01-30 Thread Scott Moser

Public bug reported:

Many cloud providers mimic the EC2 Metadata service [1] in order to provide
a level of EC2 compatibility for images.  This is quite useful and allows
image portability.

Because this is a network based metadata service, cloud-init opportunistically
poll an IPv4 link local address (http://169.254.169.254) to determine if there
is metadata available.  That can have negative side affects such as timeouts.

AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].

Cloud-init will change its behavior to only attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.

--
[1] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html

** Affects: cloud-init
 Importance: Medium
 Assignee: Scott Moser (smoser)
 Status: In Progress

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
   Status: Confirmed => In Progress

** Changed in: cloud-init
 Assignee: (unassigned) => Scott Moser (smoser)

-- 
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/1660385

Title:
  Alert user of Ec2 Datasource on lookalike cloud

Status in cloud-init:
  In Progress

Bug description:
  Many cloud providers mimic the EC2 Metadata service [1] in order to provide
  a level of EC2 compatibility for images.  This is quite useful and allows
  image portability.

  Because this is a network based metadata service, cloud-init opportunistically
  poll an IPv4 link local address (http://169.254.169.254) to determine if there
  is metadata available.  That can have negative side affects such as timeouts.

  AWS has recently begun providing a way for instances to determine if they
  are running on EC2 [2].

  Cloud-init will change its behavior to only attempt to find the EC2 metadata
  service only if it has determined itself to be running on EC2 or another
  known cloud provider which provides an EC2 metadata service.

  --
  [1] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
  [2] 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1660385/+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 1642104] Re: Admin can reuse Project Volumes Snapshots Overview page

Reviewed:  https://review.openstack.org/398031
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=040210239fdd8d531dd65d1bf7588df6f14dbbee
Submitter: Jenkins
Branch:master

commit 040210239fdd8d531dd65d1bf7588df6f14dbbee
Author: Cindy Lu 
Date:   Tue Nov 15 17:38:21 2016 -0800

Reuse Overview tab for Admin Volume Snapshots

Admin should reuse Project's Overview tab.

Change-Id: I2c8adff108593f539ddf28713de59b0f9f5c4dd1
Closes-Bug: #1642104


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

Title:
  Admin can reuse Project Volumes Snapshots Overview page

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  We have _detail_overview.html defined twice - one for Project, one for
  Admin. They are exactly the same.

  We can reuse one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1642104/+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 1651549] Re: fix spec file variable

Reviewed:  https://review.openstack.org/413208
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=d4083d18ad78276aa99843f99d0dbc16d0d81266
Submitter: Jenkins
Branch:master

commit d4083d18ad78276aa99843f99d0dbc16d0d81266
Author: Cindy Lu 
Date:   Tue Dec 20 10:32:59 2016 -0800

Fix spec file variable/ improve code coverage

- fix wrong deferred.resolve() assignment
- static/app/core/images/details/ branch coverage
used to be 50%
- use angular.isArray() instead of $.isArray()

Change-Id: Iad7a688513a2f71a779bb621b6046485cb62cc0d
Closes-Bug: #1651549


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

Title:
  fix spec file variable

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/static/app/core/images/details/overview.controller.spec.js#L33

  should be sessionDeferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1651549/+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 1659710] Re: Transition qos notification driver into qos driver

Best I can tell, there's nothing needed herein from a neutron doc
(devref or apiref) POV. The respective change that generated this bug
already contained devref updates [1].

As per [2] the 'notification_drivers' config option is deprecated for
QoS; therefore we need to update the associated config ref.

Moving this to openstack-manuals.


[1] 
https://review.openstack.org/#/c/396651/29/doc/source/devref/quality_of_service.rst
[2] 
https://review.openstack.org/#/c/396651/29/neutron/conf/services/qos_driver_manager.py

** Project changed: neutron => openstack-manuals

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

Title:
  Transition qos notification driver into qos driver

Status in openstack-manuals:
  New

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

  commit 38c1812015b6977f8212723d08cefb0926e6
  Author: Miguel Angel Ajo 
  Date:   Thu Nov 17 09:17:29 2016 -0500

  Transition qos notification driver into qos driver
  
  This will deprecate the notification_driver config setting,
  and no config setting will be needed.
  
  Also it lays down the foundation for a more decoupled interaction
  with mechanism drivers.
  
  Closes-Bug: #1657379
  Related-Bug: #1627749
  DocImpact
  
  Change-Id: I2f166a43f0b980ad22617f8a3f7b4cc7f4786c48

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/1659710/+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 1657923] Re: Add a ReST client for placement API

Best I can tell, nothing needs updating in neutron (devref or apiref).
The manuals were already updated as per the related project bug.

Thus marking as invalid for neutron as per [1] since there's nothing we
need to do in the neutron repo.


[1] 
http://docs.openstack.org/developer/neutron/policies/bugs.html#bug-triage-process

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

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

Title:
  Add a ReST client for placement API

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

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

  commit ebe62dcd33b54165a0e06340295c4d832f89d3dc
  Author: Miguel Lavalle 
  Date:   Sat Dec 24 18:38:57 2016 -0600

  Add a ReST client for placement API
  
  This patchset adds a ReST client for the placement API. This
  client is used to update the IPv4 inventories associated with
  routed networks segments. This information is used by the
  Nova scheduler to decide the placement of instances in hosts,
  based on the availability of IPv4 addresses in routed
  networks segments
  
  DocImpact: Adds [placement] section to neutron.conf with two
 options: region_name and endpoint_type
  
  Change-Id: I2aa614d4e6229161047b08c8bdcbca0e2e5d1f0b
  Partially-Implements: blueprint routed-networks

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1657923/+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 1625514] Re: Horizon Browser Support should be merged into devref

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

Title:
  Horizon Browser Support should be merged into devref

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  https://wiki.openstack.org/wiki/Horizon/BrowserSupport is outdated and
  should be merged into devref

  In addition, the information is currently outdated and incomplete, so
  it should be updated to include more recent information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1625514/+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 1653770] Re: incorrect policy check added to network-topo

** Changed in: horizon
   Status: Fix Committed => 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/1653770

Title:
  incorrect policy check added to network-topo

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  https://review.openstack.org/414315 introduced an incorrect policy
  check to the network-topology panel. My comment there:

  "I'm not sure how where this call is actually made and why it would be 
applicable to this particular panel, see 
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/network_topology/views.py#L196
  Which is where the data for the topology is gathered. When applying policy 
rules we can't infer or guess which one is applicable. I typically instrument 
the service server code to verify the policy calls made."

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1653770/+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 1660375] [NEW] gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial failure in test_server_connectivity_stop_start

2017-01-30 Thread Jakub Libosvar

Public bug reported:

Instance stays in SHUTOFF state after attempt to start it again. There is a 
failure sent over RPC about communication with Neutron:
http://logs.openstack.org/47/416647/4/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/ba26dec/logs/screen-n-cpu.txt.gz#_2017-01-26_13_30_33_303

e-r-q:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Connection%20aborted%5C%22%20AND%20message%3A%5C%22BadStatusLine%5C%22%20AND%20build_name
%3Agate-tempest-dsvm-neutron-linuxbridge-ubuntu-
xenial%20AND%20tags%3Ascreen-n-cpu.txt

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: gate-failure linuxbridge tempest

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

Title:
  gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial failure in
  test_server_connectivity_stop_start

Status in neutron:
  New

Bug description:
  Instance stays in SHUTOFF state after attempt to start it again. There is a 
failure sent over RPC about communication with Neutron:
  
http://logs.openstack.org/47/416647/4/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/ba26dec/logs/screen-n-cpu.txt.gz#_2017-01-26_13_30_33_303

  e-r-q:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Connection%20aborted%5C%22%20AND%20message%3A%5C%22BadStatusLine%5C%22%20AND%20build_name
  %3Agate-tempest-dsvm-neutron-linuxbridge-ubuntu-
  xenial%20AND%20tags%3Ascreen-n-cpu.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1660375/+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 1658224] Re: Volumes Should Have Own Panel

Unless there is accompanying work to go with this, there's not much
point in us carrying a bug for it. If you'd like to suggest it via the
openstack-dev mailer for discussion, I'd be happy to discuss it.

** Changed in: horizon
   Status: New => Opinion

-- 
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/1658224

Title:
  Volumes Should Have Own Panel

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  Volumes haven't been part of Compute (Nova) for quite some time.
  Volumes deserve their own panel, with top level links for Volumes,
  Snapshots, and Backups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1658224/+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 1659874] Re: Install and configure in Installation Guide

The code to disable this is here:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/routers/panel.py#L30

I think what is actually happening is that you've installed an extension
that is attempting to use the routers templates, and is failing its not
present.

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

-- 
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/1659874

Title:
  Install and configure in Installation Guide

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in openstack-manuals:
  Invalid

Bug description:
  - [ ] This doc is inaccurate in this way: __

  in 
  http://docs.openstack.org/newton/install-guide-rdo/horizon-install.html
  section 
  if you chose networking option 1, disable support for layer-3 networking 
services:

  if 'enable_router': False, I always get this error:
  /var/log/httpd/error_log:[Fri Jan 27 15:29:32.804086 2017] [:error] [pid 
14936] TemplateSyntaxError: u'routers' is not a registered namespace inside 
'horizon:admin'

  
  if 'enable_router': True,
   all work fine.




  ---
  Release: 0.1 on 2017-01-26 10:44
  SHA: b31e549708a48752e24a55f1c9c373dd4fa64b21
  Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-install.rst
  URL: http://docs.openstack.org/newton/install-guide-rdo/horizon-install.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1659874/+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 1656355] Re: The py-modindex for networking-bgpvpn docs is a broken link

2017-01-30 Thread Thomas Morin

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

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

Title:
  The py-modindex for networking-bgpvpn docs is a broken link

Status in networking-bgpvpn:
  New
Status in neutron:
  In Progress

Bug description:
  The Module Index link on this page:

  http://docs.openstack.org/developer/networking-bgpvpn/

  Is giving a 404 error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bgpvpn/+bug/1656355/+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 1657087] Re: Functional versioned notification test test_create_delete_server_with_instance_update randomly fails

Reviewed:  https://review.openstack.org/424574
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=189a4a7c76d224a227c09f2b34b56ef91c1680c1
Submitter: Jenkins
Branch:master

commit 189a4a7c76d224a227c09f2b34b56ef91c1680c1
Author: Balazs Gibizer 
Date:   Tue Jan 24 11:38:59 2017 +0100

Fix race condition in instance.update sample test

The test case test_create_delete_server_with_instance_update failed randomly
because the last expected instance.update notification was not received due
to a race condition.

The test polls the REST API and waits for the instance to reach ACTIVE 
state.
However the last instance.update is sent from the instance.save after the
state of the instance is updated in the DB. Therefore it is possible that
the test saw ACTIVE instance state before the last instance.update
notification is emitted.

This patch introduce an extra wait call to receive the last notification
as well.

Closes-Bug: #1657087
Change-Id: I438bbb6de0733d0c3fd8361fdc4149c88abb53aa


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

Title:
  Functional versioned notification test
  test_create_delete_server_with_instance_update randomly fails

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  We have some non-deterministic failures in this functional test for
  versioned notifications:

  http://logs.openstack.org/32/420132/3/check/gate-nova-tox-db-
  functional-ubuntu-
  xenial/0ecd455/console.html#_2017-01-17_03_22_08_097927

  2017-01-17 03:22:08.097927 | 
nova.tests.functional.notification_sample_tests.test_instance.TestInstanceNotificationSample.test_create_delete_server_with_instance_update
  2017-01-17 03:22:08.097978 | 
---
  2017-01-17 03:22:08.097991 | 
  2017-01-17 03:22:08.098008 | Captured traceback:
  2017-01-17 03:22:08.098026 | ~~~
  2017-01-17 03:22:08.098048 | Traceback (most recent call last):
  2017-01-17 03:22:08.098098 |   File 
"nova/tests/functional/notification_sample_tests/test_instance.py", line 166, 
in test_create_delete_server_with_instance_update
  2017-01-17 03:22:08.098124 | self.assertEqual(7, 
len(instance_updates))
  2017-01-17 03:22:08.098183 |   File 
"/home/jenkins/workspace/gate-nova-tox-db-functional-ubuntu-xenial/.tox/functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 411, in assertEqual
  2017-01-17 03:22:08.098223 | self.assertThat(observed, matcher, 
message)
  2017-01-17 03:22:08.098283 |   File 
"/home/jenkins/workspace/gate-nova-tox-db-functional-ubuntu-xenial/.tox/functional/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 498, in assertThat
  2017-01-17 03:22:08.098302 | raise mismatch_error
  2017-01-17 03:22:08.098328 | testtools.matchers._impl.MismatchError: 7 != 
6
  2017-01-17 03:22:08.098341 | 
  2017-01-17 03:22:08.098353 | 
  2017-01-17 03:22:08.098371 | Captured pythonlogging:
  2017-01-17 03:22:08.098388 | ~~~
  2017-01-17 03:22:08.098838 | 2017-01-17 03:20:02,061 INFO 
[nova.api.openstack] Loaded extensions: ['extensions', 'flavors', 
'image-metadata', 'image-size', 'images', 'ips', 'limits', 'os-admin-actions', 
'os-admin-password', 'os-agents', 'os-aggregates', 
'os-assisted-volume-snapshots', 'os-attach-interfaces', 'os-availability-zone', 
'os-baremetal-nodes', 'os-block-device-mapping', 'os-cells', 'os-certificates', 
'os-cloudpipe', 'os-config-drive', 'os-console-auth-tokens', 
'os-console-output', 'os-consoles', 'os-create-backup', 'os-deferred-delete', 
'os-evacuate', 'os-extended-availability-zone', 
'os-extended-server-attributes', 'os-extended-status', 'os-extended-volumes', 
'os-fixed-ips', 'os-flavor-access', 'os-flavor-extra-specs', 
'os-flavor-manage', 'os-flavor-rxtx', 'os-floating-ip-dns', 
'os-floating-ip-pools', 'os-floating-ips', 'os-floating-ips-bulk', 'os-fping', 
'os-hide-server-addresses', 'os-hosts', 'os-hypervisors', 
'os-instance-actions', 'os-instance-usage-audit-log', '
 os-keypairs', 'os-lock-server', 'os-migrate-server', 'os-migrations', 
'os-multinic', 'os-multiple-create', 'os-networks', 'os-networks-associate', 
'os-pause-server', 'os-quota-class-sets', 'os-quota-sets', 
'os-remote-consoles', 'os-rescue', 'os-scheduler-hints', 
'os-security-group-default-rules', 'os-security-groups', 
'os-server-diagnostics', 'os-server-external-events', 'os-server-groups', 
'os-server-password', 'os-server-tags', 'os-server-usage', 'os-services', 
'os-shelve', 'os-simple-tenant-usage', 'os-suspend-server', 
'os-tenant-networks', 'os-used-limits',

[Yahoo-eng-team] [Bug 1660088] Re: Huge number of deprecation warnings in oslo.context 2.12.0

2017-01-30 Thread Graham Hayes

** Also affects: oslo.context
   Importance: Undecided
   Status: New

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

Title:
  Huge number of deprecation warnings in oslo.context 2.12.0

Status in neutron:
  Fix Released
Status in oslo.context:
  New

Bug description:
  I found in Neutron's functional tests (like 
http://logs.openstack.org/29/426429/3/check/gate-neutron-dsvm-functional-ubuntu-xenial/7079dc5/console.html)
 huge number of deprecation warning which comes from oslo.context module.
  It causes troubles with finish of tests (because of reach timeouts) and is 
very "noisy" in logs.
  I described it also in 
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg99752.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1660088/+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 1328853] Re: can not access hyper-v console from horizon dashboard(icehouse)

Marking invalid; it's not an issue I am still aware of, and its an
extremely old horizon version.

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
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/1328853

Title:
  can not access hyper-v console from horizon dashboard(icehouse)

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Environment:

  
  Request Method: GET
  Request URL: 
http://ip/project/instances/01441164-6811-4f5a-8cdb-e71bed1fcc2f/?tab=instance_details__console

  Django Version: 1.6.5
  Python Version: 2.7.3
  Installed Applications:
  ['openstack_dashboard.dashboards.project',
   'openstack_dashboard.dashboards.admin',
   'openstack_dashboard.dashboards.settings',
   'openstack_dashboard',
   'django.contrib.contenttypes',
   'django.contrib.auth',
   'django.contrib.sessions',
   'django.contrib.messages',
   'django.contrib.staticfiles',
   'django.contrib.humanize',
   'compressor',
   'horizon',
   'openstack_auth']
  Installed Middleware:
  ('django.middleware.common.CommonMiddleware',
   'django.middleware.csrf.CsrfViewMiddleware',
   'django.contrib.sessions.middleware.SessionMiddleware',
   'django.contrib.auth.middleware.AuthenticationMiddleware',
   'django.contrib.messages.middleware.MessageMiddleware',
   'horizon.middleware.HorizonMiddleware',
   'django.middleware.doc.XViewMiddleware',
   'django.middleware.locale.LocaleMiddleware',
   'django.middleware.clickjacking.XFrameOptionsMiddleware')

  
  Traceback:
  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py" in 
get_response
112. response = wrapped_callback(request, 
*callback_args, **callback_kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec
36. return view_func(request, *args, **kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec
52. return view_func(request, *args, **kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py" in dec
36. return view_func(request, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py" in 
view
69. return self.dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py" in 
dispatch
87. return handler(request, *args, **kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tabs/views.py" in get
71. context = self.get_context_data(**kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/views.py"
 in get_context_data
249. context = super(DetailView, self).get_context_data(**kwargs)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tabs/views.py" in 
get_context_data
56. exceptions.handle(self.request)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tabs/views.py" in 
get_context_data
54. context["tab_group"].load_tab_data()
  File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tabs/base.py" 
in load_tab_data
120. exceptions.handle(self.request)
  File "/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/tabs/base.py" 
in load_tab_data
117. tab._data = tab.get_context_data(self.request)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/tabs.py"
 in get_context_data
65. console_url = console.get_console(request, console_type, 
instance)
  File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/instances/console.py"
 in get_console
50. except nova_exception.HTTPNotImplemented:

  Exception Type: AttributeError at 
/project/instances/01441164-6811-4f5a-8cdb-e71bed1fcc2f/
  Exception Value: 'module' object has no attribute 'HTTPNotImplemented'

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1328853/+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 1220744] Re: no size check when using http to create an image

2017-01-30 Thread Ian Cordasco

This seems to have been fixed server-side and there are too many cases
to handle on the client side to fix this there. I'm marking this as
invalid. If there's renewed interest in this, we can always reopen it.

** Changed in: python-glanceclient
   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/1220744

Title:
  no size check when using http to create an image

Status in Glance:
  Fix Released
Status in Glance Client:
  Invalid

Bug description:
  if I create an image from file and use --size which is smaller than
  the image on file we would fail with the below error:

  root@opens- ~(keystone_admin)]# glance image-create --name rhevm_image 
--disk-format qcow2 --container-format bare --file 
/tmp/39f89a6a-7fbb-43c0-a5ea-19b271f51829 --size 1
  Request returned failure status.
  400 Bad Request
  Supplied size (1) and size generated from uploaded image (1440612352) did not 
match. Setting image status to 'killed'.
  (HTTP 400)

  but if I create an image from http and use a smaller size the image is
  created:

  [root@opens-XXX ~(keystone_admin)]# glance image-create --name human
  --disk-format qcow2 --container-format bare --location http://XXX
  --human-readable --size 1

  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | bare |
  | created_at   | 2013-09-04T14:18:05  |
  | deleted  | False|
  | deleted_at   | None |
  | disk_format  | qcow2|
  | id   | 55d45384-6b4b-40c6-b399-639b03c06c3b |
  | is_public| False|
  | min_disk | 0|
  | min_ram  | 0|
  | name | human|
  | owner| ad326a6c11a742c6bfdf4ad63be0c889 |
  | protected| False|
  | size | 1B   |
  | status   | active   |
  | updated_at   | 2013-09-04T14:18:05  |
  +--+--+

  
  [root@opens- ~(keystone_admin)]# glance image-list
  
+--+-+-+--+++
  | ID   | Name| Disk Format | 
Container Format | Size   | Status |
  
+--+-+-+--+++
  | 55d45384-6b4b-40c6-b399-639b03c06c3b | human   | qcow2   | bare 
| 1  | active |
  
|+--+-+-+--+++

  if size is too small we should not allow the create of the image from
  http as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1220744/+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 1517839] Re: Make CONF.set_override with parameter enforce_type=True by default

2017-01-30 Thread Ian Cordasco

** No longer affects: glance-store

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

Title:
  Make CONF.set_override with parameter enforce_type=True by default

Status in Cinder:
  In Progress
Status in cloudkitty:
  Fix Released
Status in Designate:
  Fix Released
Status in Freezer:
  In Progress
Status in Glance:
  Invalid
Status in heat:
  Fix Released
Status in Ironic:
  Triaged
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in kolla:
  Confirmed
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Won't Fix
Status in OpenStack Compute (nova):
  Fix Released
Status in octavia:
  New
Status in oslo.config:
  In Progress
Status in oslo.messaging:
  Fix Released
Status in Quark: Money Reinvented:
  New
Status in Rally:
  Fix Released
Status in senlin:
  Fix Released
Status in tacker:
  In Progress
Status in watcher:
  Fix Released

Bug description:
  1. Problems :
     oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
     By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
     override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
     In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
     parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.

     [1]
  https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173

  2. Proposal
     1) Fix violations when enforce_type=True in each project.

    2) Make method CONF.set_override with  enforce_type=True by default
  in oslo_config

   You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

  3. How to find violations in your projects.

     1. Run tox -e py27

     2. then modify oslo.config with enforce_type=True
    cd .tox/py27/lib64/python2.7/site-packages/oslo_config
    edit cfg.py with enforce_type=True

  -def set_override(self, name, override, group=None, enforce_type=False):
  +def set_override(self, name, override, group=None, enforce_type=True):

    3. Run tox -e py27 again, you will find violations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1517839/+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 1467890] Re: Session timeout on huge image uploads

As of Newton with the new Images work, this should no longer be an issue

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
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/1467890

Title:
  Session timeout on huge image uploads

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When user tries to upload an image(via horizon) which is huge in size
  while uploading the image if the session expires the process will be
  stopped in between and image upload fails.

  So when ever the user tries to upload a huge image or file then there
  should be a mechansim which will make sure the session time out did
  not occurs and make user will not losse any data

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1467890/+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 1584057] Re: Some horizon integration tests take considerable longer time / fail more often that others

No longer a problem because we removed the integration tests :(

** Changed in: horizon
   Status: Confirmed => Invalid

-- 
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/1584057

Title:
  Some horizon integration tests take considerable longer time / fail
  more often that others

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  It would be better for the overall community's mental health, if those
  flaky tests were temporarily disabled until the source of their
  flakiness becomes more evident.

  The list of tests to be disabled:

  TestStacks
    test_create_delete_stack

  TestVolumeSnapshotsAdmin
    test_create_edit_delete_volume_snapshot
    test_volume_snapshots_pagination

  TestVolumesAdvanced
test_manage_volume_attachments

  TestVolumesActions
    test_volume_upload_to_image

  TestDownloadRCFile
    test_download_rc_v3_file

  TestImagesAdmin
    test_image_create_delete

  TestInstances
test_instances_pagination

  TestAdminInstances
test_instances_pagination_and_filtration

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1584057/+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 1597677] Re: Failed to delete server from network topology view

Reviewed:  https://review.openstack.org/366498
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=73f867514864954cca49e957e15011ab8b6e90aa
Submitter: Jenkins
Branch:master

commit 73f867514864954cca49e957e15011ab8b6e90aa
Author: MinSun 
Date:   Wed Sep 7 13:14:42 2016 +0800

Support to delete instance from network topology view

When try to delete an instance in network topology view, horizon would
try to load project/instance table in background, then do the delete
row action to the instance.
But the project instance table was paginated, it only load the first
page instances. The delete action would not work if you try to delete
an instance that are not in the first page.
The patch try to fix the bug.

Change-Id: I317bd1ee418d19c075ae3ac8d39563a0514b1795
Closes-Bug: #1597677


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

Title:
  Failed to delete server from network topology view

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  When I try to terminate(delete) an instance in the network topology view, it 
seems do nothing at all.
  As check with the code, when click "terminate/delete" button, it will try to 
load project/instance table in background, then do the delete row action of the 
sever. But, the project instance table was paginated. And if you try to 
terminate/delete an instance that are not in first page of project/instance 
table, the terminate/delete action would take no action at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1597677/+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 1655281] Re: race in router delete with ha port creation

Reviewed:  https://review.openstack.org/418281
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=4c636bd1e62394025cc118f19c7b0fa2d65fe444
Submitter: Jenkins
Branch:master

commit 4c636bd1e62394025cc118f19c7b0fa2d65fe444
Author: Kevin Benton 
Date:   Tue Jan 10 02:28:46 2017 -0700

Retry on routerport delete race

After deleting the router interfaces, another concurrent
process (e.g. HA port creation) could happen before the actual
router is deleted, which would lead to an SQLAlchemy error due
to the relationship being violated.

This patch fixes the issue by bumping the router revision before
deleting the router to check for concurrent interface additions.
A race will trigger a staledataerror which will be retried by
the decorator

Closes-Bug: #1655281
Change-Id: I465e9a2f9b216991afa26c16271854fb88068006


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

Title:
  race in router delete with ha port creation

Status in neutron:
  Fix Released

Bug description:
  http://logs.openstack.org/54/417854/1/check/gate-neutron-dsvm-
  fullstack-ubuntu-xenial/a0330f8/logs/dsvm-fullstack-
  logs/TestHAL3Agent.test_ha_router/neutron-server--2017-01-10--
  06-36-00-438766.txt.gz#_2017-01-10_06_36_13_353

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1655281/+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 1660317] [NEW] NotImplementedError for detach_interface in nova-compute during instance deletion

2017-01-30 Thread George Shuklin

Public bug reported:

When baremetal instance deleted there is a harmless but annoying trace
in nova-compute output.

nova.compute.manager[26553]: INFO [instance: 
e265be67-9e87-44ea-95b6-641fc2dcaad8] Terminating instance 
[req-5f1eba69-239a-4dd4-8677-f28542b190bc 5a08515f35d749068a6327e387ca04e2 
7d450ecf00d64399aeb93bc122cb6dae - - -]
nova.compute.resource_tracker[26553]: INFO Auditing locally available compute 
resources for node d02c7361-5e3a-4fdf-89b5-f29b3901f0fc 
[req-d34e2b7b-386f-4a3c-ae85-16860a4a9c28 - - - - -]
nova.compute.resource_tracker[26553]: INFO Final resource view: 
name=d02c7361-5e3a-4fdf-89b5-f29b3901f0fc phys_ram=0MB used_ram=8096MB 
phys_disk=0GB used_disk=480GB total_vcpus=0 used_vcpus=0 pci_stats=[] 
[req-d34e2b7b-386f-4a3c-ae85-16860a4a9c28 - - - - -]
nova.compute.resource_tracker[26553]: INFO Compute_service record updated for 
bare-compute1:d02c7361-5e3a-4fdf-89b5-f29b3901f0fc 
[req-d34e2b7b-386f-4a3c-ae85-16860a4a9c28 - - - - -]
nova.compute.manager[26553]: INFO [instance: 
e265be67-9e87-44ea-95b6-641fc2dcaad8] Neutron deleted interface 
6b563aa7-64d3-4105-9ed5-c764fee7b536; detaching it from the instance and 
deleting it from the info cache [req-fdfeee26-a860-40a5-b2e3-2505973ffa75 
11b95cf353f74788938f580e13b652d8 93c697ef6c2649eb9966900a8d6a73d8 - - -]
oslo_messaging.rpc.server[26553]: ERROR Exception during message handling 
[req-fdfeee26-a860-40a5-b2e3-2505973ffa75 11b95cf353f74788938f580e13b652d8 
93c697ef6c2649eb9966900a8d6a73d8 - - -]
oslo_messaging.rpc.server[26553]: TRACE Traceback (most recent call last):
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 133, in 
_process_incoming
oslo_messaging.rpc.server[26553]: TRACE res = 
self.dispatcher.dispatch(message)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 150, 
in dispatch
oslo_messaging.rpc.server[26553]: TRACE return self._do_dispatch(endpoint, 
method, ctxt, args)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 121, 
in _do_dispatch
oslo_messaging.rpc.server[26553]: TRACE result = func(ctxt, **new_args)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/nova/exception_wrapper.py", line 75, in 
wrapped
oslo_messaging.rpc.server[26553]: TRACE function_name, call_dict, binary)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
oslo_messaging.rpc.server[26553]: TRACE self.force_reraise()
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
oslo_messaging.rpc.server[26553]: TRACE six.reraise(self.type_, self.value, 
self.tb)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/nova/exception_wrapper.py", line 66, in 
wrapped
oslo_messaging.rpc.server[26553]: TRACE return f(self, context, *args, **kw)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6691, in 
external_instance_event
oslo_messaging.rpc.server[26553]: TRACE event.tag)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6660, in 
_process_instance_vif_deleted_event
oslo_messaging.rpc.server[26553]: TRACE 
self.driver.detach_interface(instance, vif)
oslo_messaging.rpc.server[26553]: TRACE   File 
"/usr/lib/python2.7/dist-packages/nova/virt/driver.py", line 524, in 
detach_interface
oslo_messaging.rpc.server[26553]: TRACE raise NotImplementedError()
oslo_messaging.rpc.server[26553]: TRACE NotImplementedError
oslo_messaging.rpc.server[26553]: TRACE


Affected version:
nova 14.0.3
neutron 6.0.0
ironic 6.2.1

configuration for nova-compute:
compute_driver = ironic.IronicDriver

Ironic is configured to use neutron networks with generic switch as
mechanism driver for ML2 pluging.

** Affects: ironic
 Importance: Undecided
 Status: New

** Affects: neutron
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: ironic (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: ironic (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu

-- 
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/1660317

Title:
  NotImplementedError for detach_interface in nova-compute during
  instance deletion

Status in Ironic:
  New
Status in

[Yahoo-eng-team] [Bug 1659874] Re: Install and configure in Installation Guide

2017-01-30 Thread Alexandra Settle

Hi Mircea,

>From what I can see, this might be a Horizon bug, but the doc correct in
disabling routers.

I will redirect this bug to the horizon team. And close this for
openstack-manuals for now.

Thank you.

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

** Changed in: openstack-manuals
   Status: In Progress => Invalid

-- 
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/1659874

Title:
  Install and configure in Installation Guide

Status in OpenStack Dashboard (Horizon):
  New
Status in openstack-manuals:
  Invalid

Bug description:
  - [ ] This doc is inaccurate in this way: __

  in 
  http://docs.openstack.org/newton/install-guide-rdo/horizon-install.html
  section 
  if you chose networking option 1, disable support for layer-3 networking 
services:

  if 'enable_router': False, I always get this error:
  /var/log/httpd/error_log:[Fri Jan 27 15:29:32.804086 2017] [:error] [pid 
14936] TemplateSyntaxError: u'routers' is not a registered namespace inside 
'horizon:admin'

  
  if 'enable_router': True,
   all work fine.




  ---
  Release: 0.1 on 2017-01-26 10:44
  SHA: b31e549708a48752e24a55f1c9c373dd4fa64b21
  Source: 
http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/horizon-install.rst
  URL: http://docs.openstack.org/newton/install-guide-rdo/horizon-install.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1659874/+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 1660305] [NEW] DVR multinode job fails over 20 tests

2017-01-30 Thread Oleg Bondarev

Public bug reported:

Example: http://logs.openstack.org/39/426339/2/check/gate-tempest-dsvm-
neutron-dvr-multinode-full-ubuntu-xenial-
nv/b31bdd2/logs/testr_results.html.gz

Mostly  connectivity failures: cannot ssh to instance, floating IP not
ACTIVE, etc.

** Affects: neutron
 Importance: High
 Assignee: Oleg Bondarev (obondarev)
 Status: Confirmed


** Tags: gate-failure l3-dvr-backlog

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

Title:
  DVR multinode job fails over 20 tests

Status in neutron:
  Confirmed

Bug description:
  Example: http://logs.openstack.org/39/426339/2/check/gate-tempest-
  dsvm-neutron-dvr-multinode-full-ubuntu-xenial-
  nv/b31bdd2/logs/testr_results.html.gz

  Mostly  connectivity failures: cannot ssh to instance, floating IP not
  ACTIVE, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1660305/+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 1659919] Re: dhcp agent race with port update and network create

Reviewed:  https://review.openstack.org/426339
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=38de22bf2d4c0879a84db4fbc9fa030f181affc0
Submitter: Jenkins
Branch:master

commit 38de22bf2d4c0879a84db4fbc9fa030f181affc0
Author: Kevin Benton 
Date:   Fri Jan 27 10:35:44 2017 -0800

Always acquire network.id lock in dhcp port update

Looking at the cache before aqcuiring a lock may cause the
agent to mistakenly think the network doesn't exist when it
is actually being wired in parallel.

Always acquiring the network-based semaphore will ensure that
the network isn't currently being setup in another coroutine.

Closes-Bug: #1659919
Change-Id: I99ae71e3c5b1cd91dca3f6c80b04d2ecb79de64f


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

Title:
  dhcp agent race with port update and network create

Status in neutron:
  Fix Released

Bug description:
  Root cause analysis of http://logs.openstack.org/01/410501/5/gate
  /gate-tempest-dsvm-neutron-full-ubuntu-xenial/3f7b603/ race condition:

  * shows that port for VM did not go to ACTIVE because DHCP agent didn't 
notify server that it setup the DHCP reservation.
  * DHCP agent didn't setup the reservation because it didn't have the network 
in its cache yet when it received the port update but it had already started 
wiring the network in another thread
  * the port didn't exist on the server when the network setup thread asked the 
server for all ports on the network

  
  So fix is that port_update needs to acquire network lock even if network 
doesn't appear to be in cache.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1659919/+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 1651626] Re: Shared checkbox in networks should not be shown if non-admin users are not allowed to touch.

Reviewed:  https://review.openstack.org/413380
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=c9034ec7ae2155db3e746818537bdd4932cb44d1
Submitter: Jenkins
Branch:master

commit c9034ec7ae2155db3e746818537bdd4932cb44d1
Author: hanchao 
Date:   Wed Dec 21 11:00:46 2016 +0800

Remove shared checkbox for non-admin users when doing network things.

Non-admin users are not allowed to touch the 'shared' checkbox when
creating or updating networks. It is better to make this invisible
to non-admin users instead of presenting it but not allowed to touch.

Change-Id: Ia5ed186b22f8658866c3a2b2acdde8053d176d81
Closes-Bug: #1651626


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

Title:
  Shared checkbox in networks should not be shown if non-admin users are
  not allowed to touch.

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Currently, an admin user is allowed by the policy to create or update
  a network with the attribute of 'shared' checkbox during the creating
  workflow or the updating form. However, a non-admin user is not
  allowed by the policy to create or update the 'shared' attribute for
  the network.

  The current implementation for non-admin users of this process is to
  present the 'shared' checkbox. This checkbox is disabled, namely not
  allowed to touch, and with help text of 'Non admin users are not
  allowed to set shared option.'.

  By function point of view, this is correct with no problem. But from
  my opinion, non-admin users would try to tick the checkbox and then
  see that it is not allowed by the help text. This makes non-admin
  users confused. If this is not allowed to use by non-admin users, why
  not just make it invisible to non-admin users.

  This is my concern to improve the use case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1651626/+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 1659753] Re: Neutron-server is not capable of verifying that a router has a external gateway set or not.

2017-01-30 Thread Reedip

It doesnt seem valid that Neutron needs to report an error message to
clear something which is not set.


** Project changed: neutron => python-neutronclient

** Changed in: python-neutronclient
   Status: New => Invalid

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

Title:
  Neutron-server is not capable of verifying that a router has a
  external gateway set or not.

Status in python-neutronclient:
  Invalid

Bug description:
  When a user tries to clear a gateway using  "router-gateway-clear
  " for a router for which there is no external gateway set,
  the CLI sends a success message "Removed gateway from router " without checking if the gateway exists or not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1659753/+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 1567009] Re: Remove flavor seeding from the base migration