[Yahoo-eng-team] [Bug 1670236] Re: upload image crashed on dashboard

[Launchpad Bug Tracker]

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

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

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

Title:
  upload image crashed on dashboard

Status in OpenStack Dashboard (Horizon):
  Expired

Bug description:
  hi，i upload a image(size is 1.1G) failed by dashboard,but it works by shell 
command.
  in website,it promoted :  
  TypeError: Cannot read property 'data' of undefined in website;

  in /var/log/httpd/error_log,it promoted:
  [Mon Mar 06 02:29:19.109643 2017] [:error] [pid 30667] Could not process 
panel theme_preview: Dashboard with slug "developer" is not registered.
  [Mon Mar 06 02:29:19.120199 2017] [:error] [pid 30667] Could not process 
panel resource_browser: Dashboard with slug "developer" is not registered.
  [Mon Mar 06 02:30:03.916597 2017] [:error] [pid 30667] Login successful for 
user "admin".
  [Mon Mar 06 10:30:03.940660 2017] [authz_core:error] [pid 25365] [client 
10.10.xx.xx:4342] AH01630: client denied by server configuration: 
/usr/bin/keystone-wsgi-public, referer: 
http://10.10.xx.xx/dashboard/auth/login/?next=/dashboard/
  [Mon Mar 06 10:32:14.731862 2017] [:error] [pid 25889] (70007)The timeout 
specified has expired: [client 10.10.106.85:4386] mod_wsgi (pid=25889): Unable 
to get bucket brigade for request., referer: 
http://10.10.210.52/dashboard/admin/images
  [Mon Mar 06 02:32:14.773884 2017] [:error] [pid 30667] Internal Server Error: 
/dashboard/api/glance/images/
  [Mon Mar 06 02:32:14.773908 2017] [:error] [pid 30667] Traceback (most recent 
call last):
  [Mon Mar 06 02:32:14.773912 2017] [:error] [pid 30667]   File 
"/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in 
get_response
  [Mon Mar 06 02:32:14.773916 2017] [:error] [pid 30667] response = 
wrapped_callback(request, *callback_args, **callback_kwargs)
  [Mon Mar 06 02:32:14.773919 2017] [:error] [pid 30667]   File 
"/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in 
view
  [Mon Mar 06 02:32:14.773922 2017] [:error] [pid 30667] return 
self.dispatch(request, *args, **kwargs)
  [Mon Mar 06 02:32:14.773925 2017] [:error] [pid 30667]   File 
"/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in 
dispatch
  [Mon Mar 06 02:32:14.773928 2017] [:error] [pid 30667] return 
handler(request, *args, **kwargs)
  [Mon Mar 06 02:32:14.773932 2017] [:error] [pid 30667]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/rest/utils.py",
 line 187, in wrapper
  [Mon Mar 06 02:32:14.773935 2017] [:error] [pid 30667] return func(self, 
request)
  [Mon Mar 06 02:32:14.773938 2017] [:error] [pid 30667]   File 
"/usr/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 58, in 
wrapped_view
  [Mon Mar 06 02:32:14.773941 2017] [:error] [pid 30667] return 
view_func(*args, **kwargs)
  [Mon Mar 06 02:32:14.773945 2017] [:error] [pid 30667]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/rest/glance.py",
 line 181, in post
  [Mon Mar 06 02:32:14.773948 2017] [:error] [pid 30667] meta = 
create_image_metadata(request.DATA)
  [Mon Mar 06 02:32:14.773951 2017] [:error] [pid 30667]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/rest/glance.py",
 line 345, in create_image_metadata
  [Mon Mar 06 02:32:14.773955 2017] [:error] [pid 30667] 
handle_visibility(data.get('visibility'), meta)
  [Mon Mar 06 02:32:14.773958 2017] [:error] [pid 30667]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/rest/glance.py",
 line 381, in handle_visibility
  [Mon Mar 06 02:32:14.773969 2017] [:error] [pid 30667] 'invalid 
visibility option: %s' % e.args[0])
  [Mon Mar 06 02:32:14.773972 2017] [:error] [pid 30667] AjaxError: invalid 
visibility option: None
  [Mon Mar 06 02:32:14.796818 2017] [:error] [pid 30667] [remote 
10.10.xx.xx:92] mod_wsgi (pid=30667): Exception occurred processing WSGI script 
'/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi'.
  [Mon Mar 06 02:32:14.805523 2017] [:error] [pid 30667] [remote 
10.10.xx.xx:92] IOError: failed to write data

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1670236/+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 1681339] Re: Image name not populated against an Instance

[Launchpad Bug Tracker]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

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

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

Title:
  Image name not populated against an Instance

Status in OpenStack Dashboard (Horizon):
  Expired
Status in OpenStack Compute (nova):
  Expired

Bug description:
  Newton Openstack:
  ---
  On launching an instance using an image, once the image is created, no image 
name is populated against it the instance list or instance details. 

  
  Mitaka Openstack:
  ---
  On the Mitaka dashboard, Source panel on Launch instance window gives the 
option to create and attach a new volume of desired size along with the image 
used to create an instance. However, when I try to create an instance with an 
image and along with a new volume attached, the instance gets created 
successfully but does not show the image details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1681339/+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 1681339] Re: Image name not populated against an Instance

[Launchpad Bug Tracker]

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

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

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

Title:
  Image name not populated against an Instance

Status in OpenStack Dashboard (Horizon):
  Expired
Status in OpenStack Compute (nova):
  Expired

Bug description:
  Newton Openstack:
  ---
  On launching an instance using an image, once the image is created, no image 
name is populated against it the instance list or instance details. 

  
  Mitaka Openstack:
  ---
  On the Mitaka dashboard, Source panel on Launch instance window gives the 
option to create and attach a new volume of desired size along with the image 
used to create an instance. However, when I try to create an instance with an 
image and along with a new volume attached, the instance gets created 
successfully but does not show the image details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1681339/+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 1696403] Re: pep8 job (pylint) fails due to version mismatch between pylint and astroid

[OpenStack Infra]

Reviewed:  https://review.openstack.org/471763
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=17ed89cbc12db9d9c8882f1e4162547725d030ec
Submitter: Jenkins
Branch:master

commit 17ed89cbc12db9d9c8882f1e4162547725d030ec
Author: Akihiro Motoki 
Date:   Wed Jun 7 13:01:03 2017 +

Update pylint disable list to pass pylint 1.7.1 checks

Recenly pylint version was bumped to 1.7.1 in global-requirements.txt.
Pylint 1.7.1 adds more checks and breaks the neutron pep8 job.

This commit adds new checks to the disabled list to avoid the gate
breakage. Individual disabled tests can be fixed later.

The new disabled list is compatible with pylint 1.4.5,
so we can merge this regardless of pylint bump is reverted or not.

Closes-Bug: #1696403
Change-Id: If6228d0626413049b82f9d75bcdf3bea7ddacde5


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

Title:
  pep8 job (pylint) fails due to version mismatch between pylint and
  astroid

Status in neutron:
  Fix Released

Bug description:
  2017-06-07 09:29:49.968889 | Traceback (most recent call last):
  2017-06-07 09:29:49.968921 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/bin/pylint", 
line 11, in 
  2017-06-07 09:29:49.968933 | sys.exit(run_pylint())
  2017-06-07 09:29:49.968974 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/__init__.py",
 line 23, in run_pylint
  2017-06-07 09:29:49.968986 | Run(sys.argv[1:])
  2017-06-07 09:29:49.969025 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py",
 line 1332, in __init__
  2017-06-07 09:29:49.969037 | linter.check(args)
  2017-06-07 09:29:49.969074 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py",
 line 747, in check
  2017-06-07 09:29:49.969090 | self._do_check(files_or_modules)
  2017-06-07 09:29:49.969129 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py",
 line 869, in _do_check
  2017-06-07 09:29:49.969152 | self.check_astroid_module(ast_node, walker, 
rawcheckers, tokencheckers)
  2017-06-07 09:29:49.969193 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py",
 line 946, in check_astroid_module
  2017-06-07 09:29:49.969206 | walker.walk(ast_node)
  2017-06-07 09:29:49.969245 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/utils.py",
 line 874, in walk
  2017-06-07 09:29:49.969255 | self.walk(child)
  2017-06-07 09:29:49.969294 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/utils.py",
 line 871, in walk
  2017-06-07 09:29:49.969304 | cb(astroid)
  2017-06-07 09:29:49.969349 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/checkers/imports.py",
 line 249, in visit_import
  2017-06-07 09:29:49.969368 | importedmodnode = 
self.get_imported_module(node, name)
  2017-06-07 09:29:49.969411 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/checkers/imports.py",
 line 288, in get_imported_module
  2017-06-07 09:29:49.969428 | return importnode.do_import_module(modname)
  2017-06-07 09:29:49.969469 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/mixins.py",
 line 119, in do_import_module
  2017-06-07 09:29:49.969484 | relative_only=level and level >= 1)
  2017-06-07 09:29:49.969525 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/scoped_nodes.py",
 line 415, in import_module
  2017-06-07 09:29:49.969542 | return MANAGER.ast_from_module_name(modname)
  2017-06-07 09:29:49.969584 |   File 
"/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/manager.py",
 line 161, in ast_from_module_name
  2017-06-07 09:29:49.969592 | raise e
  2017-06-07 09:29:49.969620 | astroid.exceptions.AstroidImportError: Failed to 
import module six.moves.urllib.parse with error:
  2017-06-07 09:29:49.969636 | No module named six.moves.urllib.parse.
  2017-06-07 09:29:50.688358 | ERROR: InvocationError: '/bin/sh 
./tools/coding-checks.sh --pylint '
  2017-06-07 09:29:50.688923 | ___ summary 

  

[Yahoo-eng-team] [Bug 1694420] Re: AttributeError: 'NoneType' object has no attribute 'port_security_enabled

[OpenStack Infra]

Reviewed:  https://review.openstack.org/469327
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=817f39e49599c3308b5d619163a2426269633067
Submitter: Jenkins
Branch:master

commit 817f39e49599c3308b5d619163a2426269633067
Author: Kevin Benton 
Date:   Tue May 30 21:38:45 2017 -0700

Provide fallback for disabled port security extension

The push notification logic always assumed the port security object
would exist but it is not present on the port when the extension is
disabled. This defaults it to true like the server side code.[1]

1.

https://github.com/openstack/neutron/blob/c430e9b8d41c139284e840be37629afcdbc96b37/neutron/plugins/ml2/rpc.py#L142

Change-Id: Ice89ad9dd486ad5fcac534ef5f7d8aae3b6b0f97
Closes-Bug: #1694420


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

Title:
  AttributeError: 'NoneType' object has no attribute
  'port_security_enabled

Status in kolla-ansible:
  Confirmed
Status in neutron:
  Fix Released

Bug description:
  Hi, I'm seeing in kolla gates failing with this error:
  AttributeError: 'NoneType' object has no attribute 'port_security_enabled'

  Instances fail to deploy while retrieving the port in
  openvswitch_agent.

  I think may be related to this recent change
  https://review.openstack.org/#/c/466158/

  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc 
[req-3d80325e-9430-46d2-ace7-b5a6ad358d77 - - - - -] Failed to get details for 
device c22edc09-6451-4b78-9160-399fd549314e
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc Traceback (most recent call 
last):
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/rpc.py", line 
219, in get_devices_details_list_and_failed_devices
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc 
self.get_device_details(context, device, agent_id, host))
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc   File 
"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/rpc.py", line 
257, in get_device_details
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc 
'port_security_enabled': port_obj.security.port_security_enabled,
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc AttributeError: 'NoneType' 
object has no attribute 'port_security_enabled'
  2017-05-30 10:05:23.865 7 ERROR neutron.agent.rpc

  http://logs.openstack.org/93/463593/17/check/gate-kolla-dsvm-deploy-
  centos-source-centos-7-nv/f61667d/logs/kolla/neutron/neutron-
  openvswitch-agent.txt.gz#_2017-05-30_10_05_23_865

  
  Environment:

  Source code from master
  Distributions affected: centos, ubuntu, oraclelinux

  
  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1694420/+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 1684519] Re: Add missing unittests in segment db

[OpenStack Infra]

Reviewed:  https://review.openstack.org/462386
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8595a017028450ba1c5f7cd0da4e6a9bd624666e
Submitter: Jenkins
Branch:master

commit 8595a017028450ba1c5f7cd0da4e6a9bd624666e
Author: Dongcan Ye 
Date:   Thu May 4 14:02:05 2017 +0800

Add missing unit test for segment db

This patch add test for get_dynamic_segment.

Change-Id: Icf676059a0dd24ad18b8632563c4de81190f0d04
Closes-Bug: #1684519


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

Title:
  Add missing unittests in segment db

Status in neutron:
  Fix Released

Bug description:
  Most of unit tests in segment db[1] are missing.
  [1] 
https://github.com/openstack/neutron/blob/master/neutron/tests/unit/db/test_segments_db.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1684519/+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 1696874] Re: unsafe set reference in neutron iptables code

[OpenStack Infra]

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

commit e51ae07aecd14b8270f5e14175f943a5abc8caa6
Author: Kevin Benton 
Date:   Thu Jun 8 16:10:45 2017 -0700

Don't iterate updated_rule_sg_ids or updated_sg_members

updated_rule_sg_ids and updated_sg_members can be updated
concurrently by an RPC security_group_updated cast from the
server which will result in a RuntimeError due to set
size changing during iteration.

This adjusts the logic to just iterate over a copy of the set.

Change-Id: I0a7cf13157de256403cfd6196f64fafdfa65f180
Closes-Bug: #1696874


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

Title:
  unsafe set reference in neutron iptables code

Status in neutron:
  Fix Released

Bug description:
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
[req-21b216b4-9e00-4f16-aa90-fc05f875e23f - - - - -] Error while processing VIF 
ports
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most 
recent call last):
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1825, in rpc_loop
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
ovs_restarted)
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
 line 1574, in process_network_ports
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
port_info.get('updated', set()))
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/securitygroups_rpc.py", line 
303, in setup_port_filters
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.refresh_firewall(updated_devices)
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/securitygroups_rpc.py", line 
142, in decorated_function
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent *args, 
**kwargs)
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/securitygroups_rpc.py", line 
257, in refresh_firewall
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.firewall.update_port_filter(device)
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/contextlib.py", line 24, in __exit__
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.gen.next()
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/firewall.py", line 110, in 
defer_apply
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self.filter_defer_apply_off()
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_firewall.py", 
line 844, in filter_defer_apply_off
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self._remove_conntrack_entries_from_sg_updates()
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_firewall.py", 
line 829, in _remove_conntrack_entries_from_sg_updates
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent 
self._clean_deleted_sg_rule_conntrack_entries()
  :2017-06-01 14:26:28.528 13973 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_firewall.py", 
line 779, in _clean_deleted_sg_rule_conntrack_entries
  :2017-06-01 14:26:28.528 13973 ERROR 

[Yahoo-eng-team] [Bug 1697092] [NEW] Working Toll Free * 1800 (213) 2171 avg antivirus tech support phone number free in usa

[ashnaaashnaa]

Private bug reported:

Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number 
free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  
phone number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa 
Contact Microsoft Office 365 Support Phone Number
Contact Number For Microsoft Office 365
Microsoft Office 365 800 Number
Microsoft Office 365 Contact Number
Microsoft Office 365 Customer Service Number
Microsoft Office 365 Customer Service Phone Number
Microsoft Office 365 Customer Support Phone Number
Microsoft Office 365 Help Number
Microsoft Office 365 Help Phone Number
Microsoft Office 365 Helpline Number 
Microsoft Office 365 Home Premium Support Phone Number
Microsoft Office 365 Phone Number
Microsoft Office 365 Support Contact Number
Microsoft Office 365 Support Number
Microsoft Office 365 Support Phone Number
Microsoft Office 365 Support Telephone Number
Microsoft Office 365 Support Phone Number
Microsoft Office 365 Tech Support Phone Number
Microsoft Office 365 Technical Support Number
Microsoft Office 365 Technical Support Phone Number
Microsoft Support Phone Number Office 365
Ms-Office 2007 Office 365 Help Number
Office 365 Business Support Phone Number

** Affects: null-and-void
 Importance: Undecided
 Status: Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1697092

Title:
  Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone
  number free in usa

Status in NULL Project:
  Invalid

Bug description:
  Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number 
free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  
phone number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa 
  Contact Microsoft Office 365 Support Phone Number
  Contact Number For Microsoft Office 365
  Microsoft Office 365 800 Number
  Microsoft Office 365 Contact Number
  Microsoft Office 365 Customer Service Number
  Microsoft Office 365 Customer Service Phone Number
  Microsoft Office 365 Customer Support Phone Number
  Microsoft Office 365 Help Number
  Microsoft Office 365 Help Phone Number
  Microsoft Office 365 Helpline Number 
  Microsoft Office 365 Home Premium Support Phone Number
  Microsoft Office 

[Yahoo-eng-team] [Bug 1697092] Re: Working Toll Free * 1800 (213) 2171 avg antivirus tech support phone number free in usa

[William Grant]

** Project changed: nova => null-and-void

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1697092

Title:
  Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone
  number free in usa

Status in NULL Project:
  Invalid

Bug description:
  Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number 
free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  
phone number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa Working Toll Free * 
1800 (213) 2171 avg antivirus tech support  phone number free in usa Working 
Toll Free * 1800 (213) 2171 avg antivirus tech support  phone number free in 
usa Working Toll Free * 1800 (213) 2171 avg antivirus tech support  phone 
number free in usa Working Toll Free * 1800 (213) 2171 avg antivirus tech 
support  phone number free in usa Working Toll Free * 1800 (213) 2171 avg 
antivirus tech support  phone number free in usa Working Toll Free * 1800 (213) 
2171 avg antivirus tech support  phone number free in usa 
  Contact Microsoft Office 365 Support Phone Number
  Contact Number For Microsoft Office 365
  Microsoft Office 365 800 Number
  Microsoft Office 365 Contact Number
  Microsoft Office 365 Customer Service Number
  Microsoft Office 365 Customer Service Phone Number
  Microsoft Office 365 Customer Support Phone Number
  Microsoft Office 365 Help Number
  Microsoft Office 365 Help Phone Number
  Microsoft Office 365 Helpline Number 
  Microsoft Office 365 Home Premium Support Phone Number
  Microsoft Office 365 Phone Number
  Microsoft Office 365 Support Contact Number
  Microsoft Office 365 Support Number
  Microsoft Office 365 Support Phone Number
  Microsoft Office 365 Support Telephone Number
  Microsoft Office 365 Support Phone Number
  Microsoft Office 365 Tech Support Phone Number
  Microsoft Office 365 Technical Support Number
  Microsoft Office 365 Technical Support Phone Number
  Microsoft Support Phone Number Office 365
  Ms-Office 2007 Office 365 Help Number
  Office 365 Business Support Phone Number

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1697092/+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 1693917] Re: test_user_account_lockout failed in gate because authN attempts took longer than usual

[Lance Bragstad]

I'm not sure how much keystone can do to fix this. Keystone seems to be
doing what is expected, but request latency could be causing skew to
account for this case. One thing we might be able to do is bump up the
user_lockout_duration from 5 to something greater. While that specific
test will run slower, it will be isolated to that specific test.


[0] 
https://github.com/openstack/tempest/blob/b9b03484e50024112bd325182165945656be9f55/tempest/config.py#L182-L185

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1693917

Title:
  test_user_account_lockout failed in gate because authN attempts took
  longer than usual

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  http://logs.openstack.org/99/460399/2/check/gate-tempest-dsvm-neutron-
  full-ubuntu-xenial/f7eb334/logs/testr_results.html.gz

  ft1.2: 
tempest.api.identity.v3.test_users.IdentityV3UsersTest.test_user_account_lockout[id-a7ad8bbf-2cff-4520-8c1d-96332e151658]_StringException:
 pythonlogging:'': {{{
  2017-05-24 21:05:50,147 32293 INFO [tempest.lib.common.rest_client] 
Request (IdentityV3UsersTest:test_user_account_lockout): 201 POST 
https://15.184.66.148/identity/v3/auth/tokens
  2017-05-24 21:05:50,147 32293 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Accept': 'application/json', 'Content-Type': 
'application/json'}
  Body: 
  Response - Headers: {u'vary': 'X-Auth-Token', 'content-location': 
'https://15.184.66.148/identity/v3/auth/tokens', u'connection': 'close', 
u'content-length': '344', u'x-openstack-request-id': 
'req-11e47cfa-6b25-47d4-977a-94f3e6d95665', 'status': '201', u'server': 
'Apache/2.4.18 (Ubuntu)', u'date': 'Wed, 24 May 2017 21:05:50 GMT', 
u'x-subject-token': '', u'content-type': 'application/json'}
  Body: {"token": {"issued_at": "2017-05-24T21:05:50.00Z", 
"audit_ids": ["GQR0RZcDSWC_bslZSUzpGg"], "methods": ["password"], "expires_at": 
"2017-05-24T22:05:50.00Z", "user": {"password_expires_at": null, "domain": 
{"id": "default", "name": "Default"}, "id": "415e3f0e215f44a586bdf62e7ea6e02d", 
"name": "tempest-IdentityV3UsersTest-343470382"}}}
  2017-05-24 21:05:50,237 32293 INFO [tempest.lib.common.rest_client] 
Request (IdentityV3UsersTest:test_user_account_lockout): 401 POST 
https://15.184.66.148/identity/v3/auth/tokens
  2017-05-24 21:05:50,238 32293 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Accept': 'application/json', 'Content-Type': 
'application/json'}
  Body: 
  Response - Headers: {u'vary': 'X-Auth-Token', 'content-location': 
'https://15.184.66.148/identity/v3/auth/tokens', u'connection': 'close', 
u'content-length': '114', u'x-openstack-request-id': 
'req-0a45b9b8-4c7c-409c-9c8d-f6b2661c234f', 'status': '401', u'server': 
'Apache/2.4.18 (Ubuntu)', u'date': 'Wed, 24 May 2017 21:05:50 GMT', 
u'content-type': 'application/json', u'www-authenticate': 'Keystone 
uri="https://15.184.66.148/identity;'}
  Body: {"error": {"message": "The request you have made requires 
authentication.", "code": 401, "title": "Unauthorized"}}
  2017-05-24 21:05:54,909 32293 INFO [tempest.lib.common.rest_client] 
Request (IdentityV3UsersTest:test_user_account_lockout): 401 POST 
https://15.184.66.148/identity/v3/auth/tokens
  2017-05-24 21:05:54,910 32293 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Accept': 'application/json', 'Content-Type': 
'application/json'}
  Body: 
  Response - Headers: {u'vary': 'X-Auth-Token', 'content-location': 
'https://15.184.66.148/identity/v3/auth/tokens', u'connection': 'close', 
u'content-length': '114', u'x-openstack-request-id': 
'req-3dbd065f-826b-497d-86bc-2bc78a0de997', 'status': '401', u'server': 
'Apache/2.4.18 (Ubuntu)', u'date': 'Wed, 24 May 2017 21:05:50 GMT', 
u'content-type': 'application/json', u'www-authenticate': 'Keystone 
uri="https://15.184.66.148/identity;'}
  Body: {"error": {"message": "The request you have made requires 
authentication.", "code": 401, "title": "Unauthorized"}}
  2017-05-24 21:05:55,106 32293 INFO [tempest.lib.common.rest_client] 
Request (IdentityV3UsersTest:test_user_account_lockout): 201 POST 
https://15.184.66.148/identity/v3/auth/tokens
  2017-05-24 21:05:55,106 32293 DEBUG[tempest.lib.common.rest_client] 
Request - Headers: {'Accept': 'application/json', 'Content-Type': 
'application/json'}
  Body: 
  Response - Headers: {u'vary': 'X-Auth-Token', 'content-location': 
'https://15.184.66.148/identity/v3/auth/tokens', u'connection': 'close', 
u'content-length': '344', u'x-openstack-request-id': 
'req-1d367c81-2ffa-4812-904a-16be33d12fc0', 'status': '201', u'server': 
'Apache/2.4.18 (Ubuntu)', u'date': 'Wed, 24 May 2017 21:05:54 GMT', 
u'x-subject-token': '', u'content-type': 'application/json'}
  

[Yahoo-eng-team] [Bug 1696125] Re: Detach interface failed - Unable to detach from guest transient domain (pike)

[Dan Smith]

** Changed in: nova
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1696125

Title:
  Detach interface failed - Unable to detach from guest transient domain
  (pike)

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Seeing this in Tempest runs on master (pike):

  http://logs.openstack.org/24/471024/2/check/gate-tempest-dsvm-neutron-
  linuxbridge-ubuntu-
  xenial/6b98d38/logs/screen-n-cpu.txt.gz?level=TRACE#_Jun_06_02_16_02_855503

  Jun 06 02:16:02.855503 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
WARNING nova.compute.manager [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 
tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] 
[instance: 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8] Detach interface failed, 
port_id=3843caa3-ab04-45f1-94d8-f330390e40fe, reason: Device detach failed for 
fa:16:3e:ab:e3:3f: Unable to detach from guest transient domain.: 
DeviceDetachFailed: Device detach failed for fa:16:3e:ab:e3:3f: Unable to 
detach from guest transient domain.
  Jun 06 02:16:02.884007 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 
tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] 
Exception during message handling: InterfaceDetachFailed: Failed to detach 
network adapter device from 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8
  Jun 06 02:16:02.884180 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server Traceback (most recent call last):
  Jun 06 02:16:02.884286 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
157, in _process_incoming
  Jun 06 02:16:02.884395 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
  Jun 06 02:16:02.884538 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
213, in dispatch
  Jun 06 02:16:02.884669 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, 
ctxt, args)
  Jun 06 02:16:02.884777 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
183, in _do_dispatch
  Jun 06 02:16:02.884869 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
  Jun 06 02:16:02.884968 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 77, in wrapped
  Jun 06 02:16:02.885069 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server function_name, call_dict, binary)
  Jun 06 02:16:02.885171 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Jun 06 02:16:02.885272 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server self.force_reraise()
  Jun 06 02:16:02.885367 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Jun 06 02:16:02.885461 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb)
  Jun 06 02:16:02.885554 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/exception_wrapper.py", line 68, in wrapped
  Jun 06 02:16:02.885649 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw)
  Jun 06 02:16:02.885755 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 214, in decorated_function
  Jun 06 02:16:02.885856 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info())
  Jun 06 02:16:02.885950 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
  Jun 06 02:16:02.886053 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 
ERROR oslo_messaging.rpc.server self.force_reraise()
  Jun 06 02:16:02.886143 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: 

[Yahoo-eng-team] [Bug 1695995] Re: of_interface=native makes openvswitch agents fail when run on the same node

[Trevor McCasland]

Oh really? I'm a genius! Marking as invalid.

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

** Tags removed: needs-attention

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

Title:
  of_interface=native makes openvswitch agents fail when run on the same
  node

Status in neutron:
  Invalid

Bug description:
  For eval purpose I used to run several openvswitch agents on the same machine.
  Kolla-ansible proposes such a thing 
(https://docs.openstack.org/developer/kolla-ansible/nova-fake-driver.html) but 
this feature is nowaday broken.
  In this context each openvswitch agent are running on its own dedicated 
  docker container and are configured to use a different ovs bridge (br-int-1, 
br-int-2, …).

  Some preliminary tests shows that using the default
  `of_interface=native` led to some troubles.

  Environment : 
  -

  $) docker exec -ti neutron_openvswitch_agent_1 pip freeze | grep neutron
  neutron==11.0.0.0b2.dev408
  neutron-fwaas==11.0.0.0b2.dev25
  neutron-lib==1.7.0
  python-neutronclient==6.2.0

  $) docker exec -ti neutron_openvswitch_agent_1 ovs-vsctl --version
  ovs-vsctl (Open vSwitch) 2.6.1
  DB Schema 7.14.0

  Observation with of_interface=native
  -

  On the nodes where several openvswitch agents run only one runs correctly. 
  The others fail (3 agents in this example) showing the following log :

  2017-06-05 20:24:16.056 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:17.117 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:21.061 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:22.123 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:26.064 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:27.125 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:31.065 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:32.128 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:36.072 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:37.131 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:41.077 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:42.136 7 DEBUG ovsdbapp.backend.ovs_idl.vlog [-] [POLLIN] on 
fd 8 __log_wakeup 
/var/lib/kolla/venv/lib/python2.7/site-packages/ovs/poller.py:246
  2017-06-05 20:24:42.163 7 ERROR 
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ofswitch [-] 
Switch connection timeout

  
  $) openstack network agent list
  
+--+++---+---+---+---+
  | ID   | Agent Type | Host
   | Availability Zone | Alive | State | Binary 
   |
  
+--+++---+---+---+---+
  | 143b3b54-0f5e-4a2a-a441-fed5e5cc496f | L3 agent   | 
enos-126-neutron-l3-agent  | nova  | True  | UP| 
neutron-l3-agent  |
  | a6d5e1d9-3102-4395-bd52-977372b0cfeb | Open vSwitch agent | 
enos-125-neutron-openvswitch-agent | None  | True | UP| 
neutron-openvswitch-agent |
  | cd8d49c6-aaa6-4de7-a07f-68ef3b117e36 | Open vSwitch agent | 
enos-126-neutron-openvswitch-agent | None  | True  | UP| 
neutron-openvswitch-agent |
  | d951874e-d449-459e-bf47-bd746a45b16a | Metadata agent | 
enos-126-neutron-metadata-agent| None  | True  | UP| 
neutron-metadata-agent|
  | fe2cf638-ff26-4662-969e-5f49e6b57d4d | DHCP agent | 
enos-126-neutron-dhcp-agent| nova  | True  | UP| 

[Yahoo-eng-team] [Bug 1686921] Re: There are wrong unit tests about config option usage

[Lance Bragstad]

This should have been released with pike-2 [0].

[0]
https://github.com/openstack/releases/commit/ee30897b69d42ffe75f2a10dbd305be7da5e2f9e

** Changed in: keystone
Milestone: None => pike-2

** Changed in: keystone
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1686921

Title:
  There are wrong unit tests about config option usage

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  We enforce config option type check in oslo.config [1][2]. Some unit tests
  failed in KeyStone[3]. Failures are listed in 
https://etherpad.openstack.org/p/keystone_enforce_type_issues

  [1] https://review.openstack.org/328692
  [2] https://review.openstack.org/#/c/455522/
  [3] 
http://logs.openstack.org/periodic/periodic-keystone-py27-with-oslo-master/0868d74/testr_results.html.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1686921/+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 1684820] Re: GET /role_assignments?include_names API is blocked with 404 error when a user doesn't exists in identity backend

[Lance Bragstad]

** Changed in: keystone/ocata
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1684820

Title:
  GET /role_assignments?include_names API is blocked with 404 error when
  a user doesn't exists in identity backend

Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) ocata series:
  Fix Released

Bug description:
  In an environment like ldap server as identity backend, where users
  are assigned roles it insert records in keystone.assignment table.
  After a while if an admin removes one of the user say "user1" from
  identity backend, role assignment still persists in
  keystone.assignment table for "user1".

  So when a someone invokes [0], it fetches all role assignments at [1],
  then tries to get usernames at [2] by iterating though each of the
  user_id in resultant role assignments at [3]. since "user1" doesn't
  exits, it is throwing "Could not find user: user1." with 404 error
  which we need to handle it.

  
  [0] GET /v3/role_assignments?effective_names=proj1
  [1] 
https://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L918
  [2] 
https://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L928
  [3] 
https://github.com/openstack/keystone/blob/master/keystone/assignment/core.py#L941

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1684820/+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 1696759] Re: Inconsistent notifications after subnet update

[Sylvain Bauza]

Reassigning to the Neutron project as the notification is emitted by it.

** Summary changed:

- Inconsistent RabbitMQ messages after subnet update
+ Inconsistent notifications after subnet update

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

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

** Tags removed: rabbitmq

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

Title:
  Inconsistent notifications after subnet update

Status in neutron:
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===

  When I use horizon UI to update name of an existing subnet (through
  "Edit Subnet" dialog), the relevant message that gets posted to nova
  message queue (RabbitMQ) is inconsistent in both "event_type" field
  and structure in general.

  
  Steps to reproduce
  ==
  Prerequisite: Project should contain a network.

  In Horizon UI:
  1. In sidebar go to Project -> Network -> Networks.
  2. In Subnets list click "Create subnet", fill the details and bind it to an 
existing network, click Next -> Create.
  3. On networks screen click "Edit Subnet" button next to newly created subnet.
  4. Change name to a new value, click Next -> Save.
  Repeat steps 3-4 at least 3 times (preferably, each time use a previously 
unused name).

  For "Expected/actual result" sections I'll refer to the subnet as 
"test-subnet". The sequence of updated names is the following:
  "test-subnet" -> "test-subnet1" -> "test-subnet2" -> "test-subnet3" -> 
"test-subnet4" -> "test-subnet5" -> "test-subnet6"

  
  Expected result
  ===

  For each update a message is posted to RabbitMQ of the following
  structure (only important fields specified):

  {
"event_type": "subnet.update.end",
"payload": {
  "subnet": {
"id": uuid of subnet,
"name": updated subnet name 
  }
}
  }

  
  Actual result
  =
  For these consequential updates the pattern observed is the following:

  1) "test-subnet" -> "test-subnet1"
  {
"event_type": "subnet.update.end",
"payload": {
  "subnet": {
"id": uuid of subnet,
"name": "test-subnet1"
  }
}
  }

  2) "test-subnet1" -> "test-subnet2"
  {
"event_type": "subnet.update.start" (different event type),
"payload": {
  "id": uuid of subnet (note the location of field)
  "subnet": {
"name": "test-subnet2" (note the absence of id on this level)
  }
}
  }

  
  3) "test-subnet2" -> "test-subnet3"
  No message was caught at all

  4) "test-subnet3" -> "test-subnet4"
  {
"event_type": "subnet.update.end",
"payload": {
  "subnet": {
"id": uuid of subnet,
"name": "test-subnet4"
  }
}
  }
  // The same as in p.1, except for the new name
  5) "test-subnet4" -> "test-subnet5"
  // The same as in p.2, except for the new name
  6) "test-subnet5" -> "test-subnet6"
  // The same as in p.3

  This cycle repeats in this very order indefinitely.

  
  Environment
  ===
  1. Mirantis-Mitaka (nova version 13.1.2)
  2. libvirt+KVM
  3. LVM
  4. neutron with OVS
  5. Python AMQP listener - kombu 4.0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696759/+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 1695965] Re: "nova-manage db online_data_migrations" exit code is strange

[Sylvain Bauza]

Chris, I'm not seeing this as a bug, rather some possible code
improvement. Closing it as Invalid/Wishlist and just open a change for
reviews, that's it :-)

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

** Changed in: nova
   Importance: Undecided => Wishlist

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

Title:
  "nova-manage db online_data_migrations" exit code is strange

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  If I'm reading the code right, the return value for "nova-manage db
  online_data_migrations" will be 1 if we actually performed some
  migrations and 0 if we performed no migrations, either because there
  were no remaining migrations or because the migration code raised an
  exception.

  This seems less than useful for someone attempting to script repeated
  calls to this with --max-count set.  The caller needs to parse the
  output to determine whether or not it was successful.

  I think it would make more sense to have the return code as follows:

  0 -- no errors and completed
  1 -- one of the migrations raised an exception, needs manual action
  2 -- no errors but not yet complete, need to call again

  since it would allow for an automated retry based solely on the exit
  code.

  At the very least, the return code should be nonzero for the case
  where one of the migrations raised an exception, and 0 for the case
  where no exception was raised.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1695965/+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 1696664] Re: Order of the interfaces is not honored when using virt and SR-IOV interfaces

[Sylvain Bauza]

so, after thinking more of the problem, I just feel that the current
codepath is making promises that it can't sustain. To be clear, NIC
ordering on a VM can sometimes be undeterministic depending on the OS.

For that precise reason, a new feature recently merged in Newton about allowing 
NICs to be tagged :
https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/virt-device-role-tagging.html

That way, you can query the metadata service in order to know which NIC
is corresponding to which port/network you passed.

See https://developer.openstack.org/api-ref/compute/?expanded=create-
server-detail and lookup for the 'networks' parameter, you'll see
mentioned a 'tag' attribute that is available since 2.32 API
microversion.

Closing the bug as WontFix since the community agreed on that direction.

** Changed in: nova
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1696664

Title:
  Order of the interfaces is not honored when using virt and SR-IOV
  interfaces

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  When launching an instance using the following:
  # nova boot --flavor m1.small --image  --nic net-id= --nic 
port-id= vm1

  Where the first interface is a non SR-IOV port and the second one is
  SR-IOV port the order is not preserved ,i.e. The first interface of
  the instance is the SR-IOV port.

  Version:
  openstack-nova-compute-15.0.3-3.el7ost.noarch

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696664/+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 1693670] Re: Fix doc generation for Python3

[gordon chung]

** No longer affects: panko

** No longer affects: aodh

** No longer affects: ceilometer

** No longer affects: oslo.messaging

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Cue:
  In Progress
Status in Designate:
  Fix Released
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  Fix Released
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Security Advisory:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1696690] Re: neutron fails to connect to q-agent-notifier-port-delete_fanout exchange

[milan k]

Ah so inspector was already mentioned, maybe I needn't also-affect it

** Also affects: ironic-inspector
   Importance: Undecided
   Status: New

** No longer affects: ironic-inspector

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

Title:
  neutron fails to connect to q-agent-notifier-port-delete_fanout
  exchange

Status in neutron:
  Confirmed

Bug description:
  logstash query (>70 hits for last 7 days)
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22NotFound%3A%20Basic.publish%3A%20(404)%20NOT_FOUND%20-%20no%20exchange%20'q-agent-notifier-port-'%5C%22%20AND%20build_status%3AFAILURE

  example of the failed log
  
http://logs.openstack.org/27/469627/8/check/gate-grenade-dsvm-ironic-ubuntu-xenial/bffe275/logs/new/screen-q-svc.txt.gz#_2017-06-08_08_23_28_906

  after 3 attempts neutron seems to give up.
  The actual tempest tests failing are seemingly random (most probably 
whichever tries to cleanup a port created during test), failing on 500 from 
Neutron.

  interestingly enough, this mostly affects single-node standard grenade
  jobs for ironic and ironic-inspector (which also installs ironic).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696690/+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 1696996] [NEW] H405 hacking rule (multi-line docstring)

[Akihiro Motoki]

Public bug reported:

H405 "multi line docstring summary not separated with an empty line" is
now disabled in horizon flake8 (pep8 job). We sometimes(?) have comments
on docstring format. It is useful to enable this rule.

** Affects: horizon
 Importance: Low
 Assignee: Akihiro Motoki (amotoki)
 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/1696996

Title:
  H405 hacking rule (multi-line docstring)

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  H405 "multi line docstring summary not separated with an empty line"
  is now disabled in horizon flake8 (pep8 job). We sometimes(?) have
  comments on docstring format. It is useful to enable this rule.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1696996/+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 1694207] Re: Resource count displayed at the above of each table will not be changed according to UpdateRow result

[OpenStack Infra]

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

commit 5b2fe409edb6ffc3b03f28eab71aa6cb141a33d6
Author: Keiichi Hikita 
Date:   Wed May 31 09:18:04 2017 +0900

There is problem in UpdateRow of Horizon page.

If we do some resource action(e.g. create/update/delete ...),
UpdateRow will be started.
And then resource status will be updated automatically in front-end.
But in case removing resource, number of resource that displayed
on both above and bottom of table will not be updated correctly.

I fixed update_footer_count function in horizon.tables.js.
This function only updates number of resource in footer field.
(tfoot span.table_count)
But we also need to update header field. (thead span.table_count)
So I add header update logic into this file.

Change-Id: Idc4330fe779b62607ada39a9db3637de82d014f7
Closes-Bug: #1694207


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

Title:
  Resource count displayed at the above of each table will not be
  changed according to UpdateRow result

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  There is problem in UpdateRow of Horizon page.

  If we do some resource action(e.g. create/update/delete ...), UpdateRow will 
be started.
  And then resource status will be updated automatically in front-end.

  But in case removing resource, number of resource that displayed on
  both above and bottom of table will not be updated correctly.

  For example, in case we have two resource, table has label like "Displaying 2 
items".
  Then if we remove one resource, after UpdateRow finished, number of resource 
becomes following status.
  - Bottom one becomes "Displaying 1 item".
  - Above one keeps display "Displaying 2 items". (Not modified depending on 
resource count changing)

  
  As other example, in case we have only one resource, table has label like 
"Displaying 1 item" first.
  And if we remove this resource, number of resource becomes following status.
  - Bottom one is hidden. (Nothing is displayed)
  - Above one keeps display "Displaying 1 items". (Also not modified)

  I think we should fix this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1694207/+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 1696983] [NEW] ovs-fw: flows on br-int are overlapping with dvr flows

[Jakub Libosvar]

Public bug reported:

DVR flows use normal action in table 0 on br-int. In ovs firewall, table
0 is used as a detector for ingress and egress VM traffic, sending
packets for further filtering in the pipeline. As DVR flows have lower
priority, DVR flows are not matched and mac translation doesn't work.

** Affects: neutron
 Importance: Undecided
 Assignee: Jakub Libosvar (libosvar)
 Status: New


** Tags: l3-dvr-backlog ovs-fw

** Changed in: neutron
 Assignee: (unassigned) => Jakub Libosvar (libosvar)

** Tags added: l3-dvr-backlog ovs-fw

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

Title:
  ovs-fw: flows on br-int are overlapping with dvr flows

Status in neutron:
  New

Bug description:
  DVR flows use normal action in table 0 on br-int. In ovs firewall,
  table 0 is used as a detector for ingress and egress VM traffic,
  sending packets for further filtering in the pipeline. As DVR flows
  have lower priority, DVR flows are not matched and mac translation
  doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1696983/+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 1693670] Re: Fix doc generation for Python3

[OpenStack Infra]

Reviewed:  https://review.openstack.org/470677
Committed: 
https://git.openstack.org/cgit/openstack/designate/commit/?id=c7b3030d8980c5107a06f0c321c5856642ee8179
Submitter: Jenkins
Branch:master

commit c7b3030d8980c5107a06f0c321c5856642ee8179
Author: melissaml 
Date:   Sun Jun 4 14:07:29 2017 +0800

Fix doc generation for Python3

Fix the Sphinx html_last_updated_fmt for Python3.
The html_last_updated_fmt option is interpreted as a
byte string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.

Change-Id: Ia8274b7db7ff0f4e45acc778f7061c2add93c65f
Closes-Bug:#1693670


** Changed in: designate
   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/1693670

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  Fix Released
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  Fix Released
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in OpenStack Security Advisory:
  In Progress
Status in Panko:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1694417] Re: dhcp_domain used when use_neutron is not set

[Eduardo Gonzalez]

The root cause of this issue was not nova, it was CentOS image defaults
to domain .novalocal, then cloud-init apply that value on startup. With
ubuntu or cirros this don't happen.

Will mark the bug as invalid.

Thanks for your work.

Regards

** Changed in: nova
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1694417

Title:
  dhcp_domain used when use_neutron is not set

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===

  While configuring nova with neutron and designate to provide DNS to
  instances, found that if use_neutron is not explicitly set to True in
  nova.conf it gets ignored and dhcp_domain setting is used (novalocal
  by default). I think designate does nothing here and the issue is
  between nova and neutron configuration because if nova option is not
  used, neutron default dns_domain would be openstacklocal.

  network_opts = [
  cfg.BoolOpt('use_neutron',
  default=True,
  deprecated_for_removal=True,
  deprecated_since='15.0.0',
  deprecated_reason="""
  nova-network is deprecated, as are any related configuration options.
  """,
  help="""
  Enable neutron as the backend for networking.
  Determine whether to use Neutron or Nova Network as the back end. Set to true
  to use neutron.
  """),

  From what I understand from [0] is if use_neutron is True(default
  value, see above), dhcp_domain option is not used and uses neutron
  settings.

  cfg.StrOpt("dhcp_domain",
  default="novalocal",
  deprecated_for_removal=True,
  deprecated_since='15.0.0',
  deprecated_reason="""
  nova-network is deprecated, as are any related configuration options.
  """,
  help="""
  This option allows you to specify the domain for the DHCP server.
  Possible values:
  * Any string that is a valid domain name.
  Related options:
  * ``use_neutron``
  """),

  Steps to reproduce
  ==

  No set use_neutron=True at nova.conf (is default)
  Set dns_domain = sample.openstack.org. in neutron.conf
  Boot an instance and check fqdn

  Expected results
  

  Instance have fqdn .sample.openstack.org

  Actual results
  ==

  Instance have fqdn .novalocal

  
  Environment
  ===

  CentOS
  Source code from master
  Deployed with kolla-ansible
  neutron + ml2 + ovs
  nova==16.0.0.0b2.dev511
  Latest commit: 
https://github.com/openstack/nova/commit/98b8e39ac5f7b3f2bb06ca415bbb806705461d74

  If manually set use_neutron=True in nova.conf instance gets domain
  based on dns_domain setting from neutron.

  [0] https://github.com/openstack/nova/blob/master/nova/conf/network.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1694417/+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 1696830] Re: nova-placement-api default config files is too strict

[Chris Dent]

As I said in response to you on the review, the goal is to be able to
express more than one place to look for the config, which the
environment variable currently does not do.

** Changed in: nova
   Status: Opinion => Triaged

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

Title:
  nova-placement-api default config files is too strict

Status in OpenStack Compute (nova):
  Triaged
Status in Nova Snap:
  New

Bug description:
  If nova.conf doesn't exist in the typical location of
  /etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
  placement-api's wsgi application will fail. In our case with the
  OpenStack snap, we have two possible paths we may pick nova.conf up
  from, based on what --config-file specifies. I think the right answer
  here is to be a bit more flexible and not set the default config file
  if it's path doesn't exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696830/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: panko
   Status: New => In Progress

** Changed in: panko
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  Fix Released
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in OpenStack Security Advisory:
  In Progress
Status in Panko:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1696972] [NEW] host type 'm1.nano' not found when lanch instance

[zhenhua.zhao]

Public bug reported:

I lanch an instance according to doc:https://docs.openstack.org/ocata
/install-guide-rdo/launch-instance-selfservice.html; Dependce has been
matched:


openstack flavor list
++-+-+--+---+---+---+
| ID | Name| RAM | Disk | Ephemeral | VCPUs | Is Public |
++-+-+--+---+---+---+
| 0  | m1.nano |  64 |1 | 0 | 1 | True  |
++-+-+--+---+---+---+

Environment:
openstack-nova-common-15.0.3-2.el7.noarch
Storage is local disk.

But I got the following exception,I'll be very appreceate if anyone can
fix it.

2017-06-09 18:11:34.384 2714 INFO nova.api.openstack.wsgi 
[req-3f03f365-939a-4f39-b3e9-486b85aaea18 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] HTTP 异常抛出：云主机类型 m1.nano 
没有找到。
2017-06-09 18:11:34.387 2714 INFO nova.osapi_compute.wsgi.server 
[req-3f03f365-939a-4f39-b3e9-486b85aaea18 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] 10.0.2.4 "GET 
/v2.1/flavors/m1.nano HTTP/1.1" status: 404 len: 470 time: 0.0577080
2017-06-09 18:11:34.442 2714 INFO nova.api.openstack.wsgi 
[req-135167cd-4698-4a92-82fd-3b6f3c74ed7d 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] HTTP 异常抛出：云主机类型 m1.nano 
没有找到。
2017-06-09 18:11:34.443 2714 INFO nova.osapi_compute.wsgi.server 
[req-135167cd-4698-4a92-82fd-3b6f3c74ed7d 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] 10.0.2.4 "GET 
/v2.1/flavors/m1.nano HTTP/1.1" status: 404 len: 470 time: 0.0523901
2017-06-09 18:11:34.494 2714 INFO nova.osapi_compute.wsgi.server 
[req-056f68e2-390d-4e08-84f2-026220dadd3e 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] 10.0.2.4 "GET /v2.1/flavors 
HTTP/1.1" status: 200 len: 520 time: 0.0470800
2017-06-09 18:11:34.537 2714 INFO nova.osapi_compute.wsgi.server 
[req-0f09f59e-950c-4913-944a-b04add664ed2 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] 10.0.2.4 "GET 
/v2.1/flavors/0 HTTP/1.1" status: 200 len: 686 time: 0.0316770
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions 
[req-30bc50f8-ee53-487b-8194-2849c517e274 516cf2cbbe7a46cebee2c50a7ff0764c 
0bd7f00e71f8494bb227621f058d926d - default default] 在API方法中发生未预料的异常
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, 
in wrapped
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 108, 
in wrapper
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 
642, in create
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions 
**create_kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/hooks.py", line 154, in inner
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions rv = 
f(*args, **kwargs)
2017-06-09 18:11:34.858 2714 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/compute/api.py", line 1613, in create
2017-06-09 

[Yahoo-eng-team] [Bug 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: ossa
   Status: New => In Progress

** Changed in: ossa
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  Fix Released
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in OpenStack Security Advisory:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1696830] Re: nova-placement-api default config files is too strict

[Sylvain Bauza]

Like I said in the review, after looking at PEP-, I think Nova already 
supports defining other places for nova.conf by defining the 
OS_PLACEMENT_CONFIG_DIR environment variable.
I don't really see why you couldn't want to set this specific envvar ?

** Changed in: nova
   Status: In Progress => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1696830

Title:
  nova-placement-api default config files is too strict

Status in OpenStack Compute (nova):
  Opinion
Status in Nova Snap:
  New

Bug description:
  If nova.conf doesn't exist in the typical location of
  /etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
  placement-api's wsgi application will fail. In our case with the
  OpenStack snap, we have two possible paths we may pick nova.conf up
  from, based on what --config-file specifies. I think the right answer
  here is to be a bit more flexible and not set the default config file
  if it's path doesn't exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696830/+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 1693679] Re: Stopped instance's disk sizes are not calculated for disk_available_least

[OpenStack Infra]

Reviewed:  https://review.openstack.org/468269
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=3342215034c7a7a938c497c39f6405763201a261
Submitter: Jenkins
Branch:master

commit 3342215034c7a7a938c497c39f6405763201a261
Author: Rikimaru Honjo 
Date:   Fri May 26 14:04:44 2017 +0900

Calculate stopped instance's disk sizes for disk_available_least

disk_available_least is a free disk size information of hypervisors.
This is calculated by the following fomula:

disk_available_least =  - 

But stopped instance's virtual disk sizes were not calculated
after merging following patch in Juno cycle:
https://review.openstack.org/#/c/105127

So disk_available_least might be larger than actual free disk size.
As a result, instances might be scheduled beyond the actual free
disk size if stopped instances were on a host.

This patch fix it.
Stopped instance's disks will be calculated after merging this patch.

Change-Id: I8abf6edfa80e3920539e4f6d4906c573f9543b91
Closes-Bug: #1693679


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

Title:
  Stopped instance's disk sizes are not calculated for
  disk_available_least

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===
  disk_available_least is a free disk size information of hypervisors.
  This is calculated by the following formula:

  disk_available_least =  - 

  But stopped instance's virtual disk sizes are not calculated now.
  So disk_available_least will be larger than actual free disk size.
  As a result, instances will be scheduled beyond the actual free disk size if 
stopped instances are on a host.

  I think that this is a bug.
  Because stopped instances are on a host unlike shelved instances.

  Steps to reproduce
  ==
  1. Call hyper visor show API for any hypervisor.
     And, check the value of disk_available_least.
  2. Create a instance with qcow2 image on 1's hypervisor.
  3. Wait for over 1 minute.
  4. Call hyper visor show API.
     And, check that disk_available_least is smaller than step 1's value.
  5. Call Stop Server API for the instance.
  6. Wait until instance's state is changed to STOPPED.
  7. Wait for over 1 minute.
  8. Call hyper visor show API.
     And, check the value of disk_available_least.

  Expected result
  ===
  disk_available_least value is same as step 8.
  Because stopped instance is still on the host.

  Actual result
  =
  disk_available_least value is bigger than step4's value in step 8.

  Environment
  ===
  * I used latest devstack.
  * I used libvirt + kvm.
  * I used qcow2 image.

  Logs & Configs
  ==
  I think that this bug affects for all settings.

  When was this bug made?
  ===
  Following patch made this bug:
  https://review.openstack.org/#/c/105127/

  Stopped instance's disk sizes were calculated until merging the above
  patch in Juno cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1693679/+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 1696843] Re: metadata: POST /openstack/2013-10-17/password fails with InstanceNotFound

[OpenStack Infra]

Reviewed:  https://review.openstack.org/472405
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=6739fa6110ea837da567ba8a40b17fe673bddef4
Submitter: Jenkins
Branch:master

commit 6739fa6110ea837da567ba8a40b17fe673bddef4
Author: Dan Smith 
Date:   Thu Jun 8 13:35:47 2017 -0700

Fix lookup of instance mapping in metadata set-password

The set-password function in metadata may try to lookup the instance
by uuid without proper cell targeting. This fixes that.

Change-Id: I8f27e4d89f0ec69b79e03a114570bedc37563cbe
Closes-Bug: #1696843


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

Title:
  metadata: POST /openstack/2013-10-17/password fails with
  InstanceNotFound

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  http://logs.openstack.org/94/436094/33/check/gate-tempest-dsvm-
  neutron-full-ubuntu-
  xenial/bed0e6a/logs/screen-n-api.txt.gz#_Jun_08_18_36_06_589590

  Jun 08 18:36:06.549748 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: DEBUG nova.api.metadata.handler [-] Using cached metadata for 
instance 6cd26f78-9c8a-4b37-8c62-38ad003a095f {{(pid=18770) 
get_metadata_by_instance_id 
/opt/stack/new/nova/nova/api/metadata/handler.py:78}}
  Jun 08 18:36:06.589590 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: INFO nova.metadata.wsgi.server [None 
req-97c06652-908d-4603-a84d-40f818726b5d None None] Traceback (most recent call 
last):
  Jun 08 18:36:06.589719 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 490, in 
handle_one_response
  Jun 08 18:36:06.589804 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: result = self.application(self.environ, start_response)
  Jun 08 18:36:06.589911 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File 
"/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 216, in __call__
  Jun 08 18:36:06.590006 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: return app(environ, start_response)
  Jun 08 18:36:06.590090 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", 
line 131, in __call__
  Jun 08 18:36:06.590179 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: resp = self.call_func(req, *args, **self.kwargs)
  Jun 08 18:36:06.590270 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", 
line 196, in call_func
  Jun 08 18:36:06.590351 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: return self.func(req, *args, **kwargs)
  Jun 08 18:36:06.590428 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File 
"/usr/local/lib/python2.7/dist-packages/oslo_middleware/base.py", line 125, in 
__call__
  Jun 08 18:36:06.590508 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: response = req.get_response(self.application)
  Jun 08 18:36:06.590585 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File 
"/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1316, in send
  Jun 08 18:36:06.590661 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: application, catch_exc_info=False)
  Jun 08 18:36:06.590742 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File 
"/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1280, in 
call_application
  Jun 08 18:36:06.590824 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: app_iter = application(self.environ, start_response)
  Jun 08 18:36:06.590906 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", 
line 131, in __call__
  Jun 08 18:36:06.590983 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: resp = self.call_func(req, *args, **self.kwargs)
  Jun 08 18:36:06.591060 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", 
line 196, in call_func
  Jun 08 18:36:06.591136 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: return self.func(req, *args, **kwargs)
  Jun 08 18:36:06.591212 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/opt/stack/new/nova/nova/api/metadata/handler.py", 
line 121, in __call__
  Jun 08 18:36:06.591287 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: return data(req, meta_data)
  Jun 08 18:36:06.591370 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]:   File "/opt/stack/new/nova/nova/api/metadata/password.py", 
line 70, in handle_password
  Jun 08 18:36:06.591446 ubuntu-xenial-osic-cloud1-s3700-9216660 
nova-api[18643]: instance = objects.Instance.get_by_uuid(ctxt, 

[Yahoo-eng-team] [Bug 1693670] Fix proposed to ldappool (master)

[OpenStack Infra]

Fix proposed to branch: master
Review: https://review.openstack.org/472604

** Changed in: oslo.messaging
   Status: New => In Progress

** Changed in: ldappool
   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/1693670

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  Fix Released
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[ZhangHongtao]

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

** Changed in: oslo.messaging
 Assignee: (unassigned) => ZhangHongtao (zhanghongtao)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  New
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: ldappool
   Status: New => In Progress

** Changed in: ldappool
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in ldappool:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in oslo.messaging:
  New
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: python-senlinclient
   Status: New => In Progress

** Changed in: python-senlinclient
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

** Changed in: cue
   Status: New => In Progress

** Changed in: cue
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[ZhangHongtao]

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

** Changed in: aodh
 Assignee: (unassigned) => ZhangHongtao (zhanghongtao)

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

Title:
   Fix doc generation for Python3

Status in Aodh:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Cue:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in python-senlinclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[luqitao]

** Also affects: glance-store
   Importance: Undecided
   Status: New

** Changed in: glance-store
 Assignee: (unassigned) => luqitao (qtlu)

** Changed in: glance-store
   Status: New => In Progress

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[ZhangHongtao]

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

** Changed in: tempest
 Assignee: (unassigned) => ZhangHongtao (zhanghongtao)

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1694753] Re: QosPolicyDbObjectTestCase.test_update_objects failed because it couldn't find a matching object

[OpenStack Infra]

Reviewed:  https://review.openstack.org/469602
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9b809fcc60d7e09b4f79fad0b992d0f27d2a100f
Submitter: Jenkins
Branch:master

commit 9b809fcc60d7e09b4f79fad0b992d0f27d2a100f
Author: Ihar Hrachyshka 
Date:   Wed May 31 10:15:16 2017 -0700

objects: exclude revision_number from updatable fields

Revision service plugin is the entity that updates the database model
attribute, and we don't allow to modify the attribute on API layer. We
should not allow to explicitly update it on OVO layer either.

This can help with spurious unit test failures that sometimes try to
update revision number and then reuse the same number to fetch the
object. If revision service plugin decides to bump the number during the
test case execution once more, using the old number may yield no
results.

Change-Id: I4666c672223ac38508738b739207f754847c62bc
Closes-Bug: #1694753


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

Title:
  QosPolicyDbObjectTestCase.test_update_objects failed because it
  couldn't find a matching object

Status in neutron:
  Fix Released

Bug description:
  2017-05-31 15:22:20.901842 | FAIL: 
neutron.tests.unit.objects.qos.test_policy.QosPolicyDbObjectTestCase.test_update_objects
  2017-05-31 15:22:20.901856 | tags: worker-4
  2017-05-31 15:22:20.901894 | 
--
  2017-05-31 15:22:20.901912 | Traceback (most recent call last):
  2017-05-31 15:22:20.901946 |   File "neutron/tests/base.py", line 115, in func
  2017-05-31 15:22:20.901964 | return f(self, *args, **kwargs)
  2017-05-31 15:22:20.901992 |   File 
"neutron/tests/unit/objects/test_base.py", line 1747, in test_update_objects
  2017-05-31 15:22:20.902013 | self.assertEqual(1, len(new_objs))
  2017-05-31 15:22:20.902066 |   File 
"/home/jenkins/workspace/neutron-coverage-ubuntu-xenial/.tox/cover/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 411, in assertEqual
  2017-05-31 15:22:20.902093 | self.assertThat(observed, matcher, message)
  2017-05-31 15:22:20.902139 |   File 
"/home/jenkins/workspace/neutron-coverage-ubuntu-xenial/.tox/cover/local/lib/python2.7/site-packages/testtools/testcase.py",
 line 498, in assertThat
  2017-05-31 15:22:20.902155 | raise mismatch_error
  2017-05-31 15:22:20.902175 | testtools.matchers._impl.MismatchError: 1 != 0

  http://logs.openstack.org/31/469231/2/check/neutron-coverage-ubuntu-
  xenial/98cd310/console.html

  Of all filters used to match the object that could change in flight is
  revision_number. Others cannot change between updates and fetches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1694753/+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 1693670] Re: Fix doc generation for Python3

[luqitao]

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

** No longer affects: swift (Ubuntu)

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: python-zaqarclient
   Status: New => In Progress

** Changed in: python-zaqarclient
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

** Changed in: meteos
   Status: New => In Progress

** Changed in: meteos
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

** Changed in: ceilometer
   Status: New => In Progress

** Changed in: ceilometer
 Assignee: (unassigned) => Pallavi (pallavi-s)

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Ceilometer:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in Meteos:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in Python client library for Zaqar:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[M V P Nitesh]

** Also affects: glance
   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/1693670

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

** Also affects: python-heatclient
   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/1693670

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in Glance:
  In Progress
Status in neutron:
  Fix Released
Status in python-heatclient:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: swift
 Assignee: (unassigned) => Pallavi (pallavi-s)

** Changed in: swift
   Status: New => In Progress

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: freezer
 Assignee: (unassigned) => Pallavi (pallavi-s)

** Changed in: freezer
   Status: New => In Progress

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in neutron:
  Fix Released
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1693670/+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 1693670] Re: Fix doc generation for Python3

[Pallavi]

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

** Changed in: designate
 Assignee: (unassigned) => Pallavi (pallavi-s)

** Changed in: designate
   Status: New => In Progress

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

Title:
   Fix doc generation for Python3

Status in Barbican:
  Fix Released
Status in Designate:
  In Progress
Status in OpenStack Backup/Restore and DR (Freezer):
  In Progress
Status in neutron:
  Fix Released
Status in tacker:
  Fix Released
Status in OpenStack DBaaS (Trove):
  In Progress
Status in zaqar:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  Fix the Sphinx html_last_updated_fmt for Python3.
  The html_last_updated_fmt option is interpeted as a
  byte string in python3, causing Sphinx build to break.
  This patch makes it utf-8 string.

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