[Yahoo-eng-team] [Bug 1666827] Re: Backport fixes for Rename Network return 403 Error

[Frode Nordahl]

** Changed in: horizon
   Status: New => 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/1666827

Title:
  Backport fixes for Rename Network return 403 Error

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  New
Status in horizon source package in Trusty:
  Invalid
Status in horizon source package in Xenial:
  Triaged
Status in horizon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Non-admin users are not allowed to change the name of a network using the 
OpenStack Dashboard GUI

  [Test Case]
  1. Deploy trusty-mitaka or xenial-mitaka OpenStack Cloud
  2. Create demo project
  3. Create demo user
  4. Log into OpenStack Dashboard using demo user
  5. Go to Project -> Network and create a network
  6. Go to Project -> Network and Edit the just created network
  7. Change the name and click Save
  8. Observe that your request is denied with an error message

  [Regression Potential]
  Minimal.

  We are adding a patch already merged into upstream stable/mitaka for
  the horizon call to policy_check before sending request to Neutron
  when updating networks.

  The addition of rule "update_network:shared" to horizon's copy of
  Neutron policy.json is our own due to upstream not willing to back-
  port this required change. This rule is not referenced anywhere else
  in the code base so it will not affect other policy_check calls.

  Upstream bug: https://bugs.launchpad.net/horizon/+bug/1609467

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1666827/+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 1659760] Re: General scale issue on neutron-fwaas due to RPC broadcast usage (fanout)

[OpenStack Infra]

Reviewed:  https://review.openstack.org/444081
Committed: 
https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=bc33639d02a6d6a64aec63d2c15eafbb54247d61
Submitter: Jenkins
Branch:master

commit bc33639d02a6d6a64aec63d2c15eafbb54247d61
Author: YAMAMOTO Takashi 
Date:   Fri Mar 10 12:14:22 2017 +0900

fwaas: Add "host" argument for agent_rpc methods

This is a prepartion for the neutron-fwaas change. [1]

[1] I68cbf7403a17ddba49cc5943fb110c1d772e8834

Closes-Bug: #1659760
Change-Id: I710c7dc0f07781e5ed8deb0b91ad4889c865ce59


** Changed in: networking-midonet
   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/1659760

Title:
  General scale issue on neutron-fwaas due to RPC broadcast usage
  (fanout)

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

Bug description:
  Actually on all CRUDs methods used on FWaaS resources (Firewall, 
FirewallPolicy, FirewallRule, Firewallgroup, ...) an AMQP fanout cast is sent 
to all L3 agents.
  This is a wrong design, AMPQ cast should be send only to L3Agents managing 
routers with firewalls related to the tenant.

  This wrong design result in many bugs already reported:

  1) FirewallNotFound during firewall_deleted
  https://bugs.launchpad.net/neutron/+bug/1622460
  https://bugs.launchpad.net/neutron/+bug/1658060

  Explanation using 2 L3agents:
  agent1: host router with firewall for tenant
  agent2: doesn't host tenant router

    1. neutron firewall-delete 
    2. neutron-server send an AMQP call "delete_firewall" to agent1 and agent2
    3. agent1 clean router firewall and send back "firewall_deleted" to 
neutron-server
    4. neutron-server delete firewall resource from database
    5. agent2 has nothing to clean and send back firewall_deleted to 
neutron-server
    6. neutron-server get an exception "FirewallNotFound"
   http://paste.openstack.org/raw/94663/

    But this is not ended :(
    7. agent2 get back the "FirewallNotfound" exception
    8. on RPC error it will performed a kind of "full synchronisation" 
(process_services_sync)
   send an AMQP call "get_tenants_with_firewalls"
    9. neutron-server will respond back with a ALL tenants (even if it's not 
related to this agents)
    10 FOR each tenant agent2 will sent a AMQP call:
   get_firewalls_for_tenant()

  Full sync bug is already reported here:
  https://bugs.launchpad.net/neutron/+bug/1618244

  2) Intermittent failed on Tempest check is probably link:
  https://bugs.launchpad.net/neutron/+bug/1649703

  3) More generally on FWaaS CRUDs operations neutron-server flood and is 
flooded by many AMQP requests.
  => this result in neutron-server RPC worker fully busy
  => AMQP messages accumulated in q-firewall-plugin queue
  => RPC Timeout appears on agents after (60s)
  => full synchronisation triggered
  => etc, etc...

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1659760/+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 1668223] Re: subnet create is not working with --use-default-subnet-pool

[Dr. Jens Rosenboom]

** Changed in: python-openstackclient
   Status: In Progress => Fix Released

** Changed in: python-openstacksdk
 Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)

** Changed in: python-openstackclient
 Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)

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

Title:
  subnet create is not working with --use-default-subnet-pool

Status in neutron:
  Confirmed
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released

Bug description:
  Seems like the option is not passed properly to the API:

  $ openstack --debug subnet create --ip-version 6 --use-default-subnet-pool 
--ipv6-address-mode slaac --ipv6-ra-mode slaac --network mynet mysubnet
  ...
  REQ: curl -g -i -X POST http://10.42.1.126:9696/v2.0/subnets -H "User-Agent: 
openstacksdk/0.9.13 keystoneauth1/2.18.0 python-requests/2.12.5 CPython/2.7.12" 
-H "Content-Type: application/json" -H "X-Auth-Token: 
{SHA1}c61b74f7c026e385b8953576101f854d86cb0d48" -d '{"subnet": {"network_id": 
"1f20da97-ddd4-40f8-b8d3-6321de8671a0", "ipv6_ra_mode": "slaac", "ip_version": 
6, "name": "mysubnet", "ipv6_address_mode": "slaac"}}'
  http://10.42.1.126:9696 "POST /v2.0/subnets HTTP/1.1" 400 146
  RESP: [400] Content-Type: application/json Content-Length: 146 
X-Openstack-Request-Id: req-299d7f52-d5ce-4873-979d-f63626f380ab Date: Mon, 27 
Feb 2017 10:30:31 GMT Connection: keep-alive 
  RESP BODY: {"NeutronError": {"message": "Bad subnets request: a subnetpool 
must be specified in the absence of a cidr.", "type": "BadRequest", "detail": 
""}}
  ...
  HttpException: HttpException: Bad Request, Bad subnets request: a subnetpool 
must be specified in the absence of a cidr.

  END return value: 1
  $

  Running the same command using the neutron CLI is working fine:

  $ neutron --debug subnet-create --name subnet6 --ip_version 6 
--use-default-subnetpool --ipv6-address-mode slaac --ipv6-ra-mode slaac mynet
  ...
  DEBUG: keystoneauth.session REQ: curl -g -i -X POST 
http://10.42.1.126:9696/v2.0/subnets.json -H "User-Agent: python-neutronclient" 
-H "Content-Type: application/json" -H "Accept: application/json" -H 
"X-Auth-Token: {SHA1}dd78a0939a35913dad4181aaf5f68e0c9277d74e" -d '{"sub
  net": {"use_default_subnetpool": true, "network_id": 
"1f20da97-ddd4-40f8-b8d3-6321de8671a0", "ipv6_ra_mode": "slaac", "ip_version": 
6, "ipv6_address_mode": "slaac", "name": "subnet6"}}'
  DEBUG: keystoneauth.session RESP: [201] Content-Type: application/json 
Content-Length: 735 X-Openstack-Request-Id: 
req-13f0bc2a-e4e5-43dc-b048-e63acef8f131 Date: Mon, 27 Feb 2017 10:46:32 GMT 
Connection: keep-alive 
  RESP BODY: {"subnet": {"service_types": [], "description": "", "enable_dhcp": 
true, "tags": [], "network_id": "1f20da97-ddd4-40f8-b8d3-6321de8671a0", 
"tenant_id": "6de6f29dcf904ab8a12e8ca558f532e9", "created_at": 
"2017-02-27T10:46:31Z", "dns_nameservers": [], "updated_at":
   "2017-02-27T10:46:31Z", "gateway_ip": "2001:db8:1234::1", "ipv6_ra_mode": 
"slaac", "allocation_pools": [{"start": "2001:db8:1234::2", "end": 
"2001:db8:1234:0::::"}], "host_routes": [], "revision_number": 
2, "ip_version": 6, "ipv6_address_mode": "slaac", "c
  idr": "2001:db8:1234::/64", "project_id": "6de6f29dcf904ab8a12e8ca558f532e9", 
"id": "ebb07be0-3f8d-4219-afbd-f81ca352954d", "subnetpool_id": 
"4c1661ba-b24c-4fda-8815-3f1fd29281af", "name": "subnet6"}}
  ...

  So somehow this attribute is missing from the OSC's request:

  "use_default_subnetpool": true

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1668223/+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 1671604] Re: KeyError with Volumes panel

[Radomir Dopieralski]

** Changed in: horizon
   Status: In Progress => Invalid

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

Title:
  KeyError with Volumes panel

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Horizon now raises this error:

  Traceback (most recent call last):
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 164, in get_response
  response = response.render()
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/response.py",
 line 158, in render
  self.content = self.rendered_content
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/response.py",
 line 135, in rendered_content
  content = template.render(context, self._request)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/backends/django.py",
 line 74, in render
  return self.template.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 210, in render
  return self._render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 202, in _render
  return self.nodelist.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 905, in render
  bit = self.render_node(node, context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/debug.py",
 line 79, in render_node
  return node.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/loader_tags.py",
 line 135, in render
  return compiled_parent._render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 202, in _render
  return self.nodelist.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 905, in render
  bit = self.render_node(node, context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/debug.py",
 line 79, in render_node
  return node.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/loader_tags.py",
 line 65, in render
  result = block.nodelist.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 905, in render
  bit = self.render_node(node, context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/debug.py",
 line 79, in render_node
  return node.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/loader_tags.py",
 line 65, in render
  result = block.nodelist.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 905, in render
  bit = self.render_node(node, context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/debug.py",
 line 79, in render_node
  return node.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/loader_tags.py",
 line 159, in render
  return template.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 212, in render
  return self._render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 202, in _render
  return self.nodelist.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 905, in render
  bit = self.render_node(node, context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/debug.py",
 line 79, in render_node
  return node.render(context)
File 
"/home/rdopiera/dev/horizon/.tox/py27/lib/python2.7/site-packages/django/template/base.py",
 line 1273, in render
  _dict = func(*resolved_args, **resolved_kwargs)
File "/home/rdopiera/dev/horizon/horizon/templatetags/horizon.py", line 67, 
in horizon_nav
  panel_groups = dash.get_panel_groups()
File "/home/rdopiera/dev/horizon/horizon/base.py", line 502, in 
get_panel_groups
  registered.pop(panel.__class__)
  KeyError: 

  In addition, Django fails to display this properly, raising:

  Traceback (most recent call last):
File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
  self.result = application(self.environ, self.start_response)
File 

[Yahoo-eng-team] [Bug 1671815] [NEW] Can not use custom network interfaces with stable/newton Ironic

[Sam Betts]

Public bug reported:

When using network interfaces in Ironic, nova shouldn't bind the port
that it creates so that the ironic network interface can do it later in
the process. Nova should only bind the port for the flat network
interface for backwards compatibility with stable/mitaka. The logic for
this in the ironic virt driver is incorrect, and will bind the port for
any ironic network interface except the neutron one.

** Affects: ironic
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

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

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

Title:
  Can not use custom network interfaces with stable/newton Ironic

Status in Ironic:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  When using network interfaces in Ironic, nova shouldn't bind the port
  that it creates so that the ironic network interface can do it later
  in the process. Nova should only bind the port for the flat network
  interface for backwards compatibility with stable/mitaka. The logic
  for this in the ironic virt driver is incorrect, and will bind the
  port for any ironic network interface except the neutron one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1671815/+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 1671847] [NEW] Incorrect set deprecated flag for notify_on_state_change

[Ionuț Bîru]

Public bug reported:

grep notify_on_state_change /var/log/nova/nova-api-os-compute.log
2017-03-10 16:26:51.974 13421 DEBUG oslo_service.service 
[req-f7d5880a-5c31-491b-b821-45666eddc10a - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
2017-03-10 16:30:19.035 13435 DEBUG oslo_service.service 
[req-8c2f196d-5cac-430c-8194-1cc560e73636 - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
2017-03-10 16:34:34.418 13510 DEBUG oslo_service.service 
[req-310dc3b3-db07-4290-acec-f758d246452b - - - - -] 
notifications.notify_on_state_change = vm_and_task_state log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744

No warning return. The 3rd line has the correct value after setting in
[notifications] section.

I'll submit the patch

** Affects: nova
 Importance: High
 Assignee: Ionuț Bîru (ionut-3)
 Status: In Progress

** Affects: nova/ocata
 Importance: High
 Status: Confirmed


** Tags: config

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

Title:
  Incorrect set deprecated flag for notify_on_state_change

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  grep notify_on_state_change /var/log/nova/nova-api-os-compute.log
  2017-03-10 16:26:51.974 13421 DEBUG oslo_service.service 
[req-f7d5880a-5c31-491b-b821-45666eddc10a - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
  2017-03-10 16:30:19.035 13435 DEBUG oslo_service.service 
[req-8c2f196d-5cac-430c-8194-1cc560e73636 - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
  2017-03-10 16:34:34.418 13510 DEBUG oslo_service.service 
[req-310dc3b3-db07-4290-acec-f758d246452b - - - - -] 
notifications.notify_on_state_change = vm_and_task_state log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744

  No warning return. The 3rd line has the correct value after setting in
  [notifications] section.

  I'll submit the patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1671847/+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 1663570] Re: Remove usage of config option verbose

[OpenStack Infra]

Reviewed:  https://review.openstack.org/432271
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=6b73c281bcbde20acb00386bbe4c0d4d1c501a04
Submitter: Jenkins
Branch:master

commit 6b73c281bcbde20acb00386bbe4c0d4d1c501a04
Author: ChangBo Guo(gcb) 
Date:   Fri Feb 10 19:54:54 2017 +0800

Remove usage of config option verbose

oslo.log deprecate config option verbose since aug 1, 2015 in review:
in https://review.openstack.org/#/c/206437/

That was a long time ago so it should be possible to remove it now. This
was already merged once but had to be reverted because some projects
were still relying on it. Oslo team plan to remove it, so we need clean
up its usage before removing it.

Closes-Bug: #1663570

Change-Id: I072e1078486f50cebea92695ff46c1af879eb23d


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

Title:
  Remove usage of config option verbose

Status in Cinder:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  oslo.log deprecate config option verbose since aug 1, 2015 in review:
  in https://review.openstack.org/#/c/206437/

  That was a long time ago so it should be possible to remove it now.
  This was already merged once but had to be reverted because some
  projects were still relying on it. so we need clean up usage of it
  before removing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1663570/+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 1511775] Re: Revoking a role revokes the unscoped token for a user

[Lance Bragstad]

I've attempted to recreate this locally after we merged a fix [0] for a
similar bug [1]. I was not able to recreate this with the latest code in
master (eed29f236e251007093ae1fe29185eddbef8497d).

I'm going to close this, but feel free to continue using this report for
discussion as necessary.


[0] 
https://github.com/openstack/keystone/commit/a103486efeefca821ac722cbad6fc31b2e3f133b
[1] https://bugs.launchpad.net/keystone/+bug/1662514

** Changed in: keystone
   Status: In Progress => 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/1511775

Title:
  Revoking a role revokes the unscoped token for a user

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  In Juno and Kilo, when a role is revoked from a user on a project, a
  callback is triggered that invalidates all of that user's tokens.  I
  can see why we'd want to do that for scoped tokens. But by revoking
  the unscoped token as well, the user is forced to log out and log back
  in.  It seems like the unscoped token should be left alone, since
  revoking a role is an authorization change, and the unscoped token is
  an authentication issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1511775/+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 1671847] Re: Incorrect set deprecated flag for notify_on_state_change

[Matt Riedemann]

Yeah we confirmed that the code is setting deprecated_group='default'
which doesn't error but doesn't do the passthrough for DEFAULT. This is
a bug on a few options that were moved between groups in ocata, so we
should fix all of them in the same patch.

** Summary changed:

- Incorect set deprecated flag for notify_on_state_change
+ Incorrect set deprecated flag for notify_on_state_change

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

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

** Tags added: config

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

** Changed in: nova/ocata
   Status: New => Confirmed

** Changed in: nova/ocata
   Importance: Undecided => High

** Changed in: nova
 Assignee: (unassigned) => Ionuț Bîru (ionut-3)

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

Title:
  Incorrect set deprecated flag for notify_on_state_change

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  grep notify_on_state_change /var/log/nova/nova-api-os-compute.log
  2017-03-10 16:26:51.974 13421 DEBUG oslo_service.service 
[req-f7d5880a-5c31-491b-b821-45666eddc10a - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
  2017-03-10 16:30:19.035 13435 DEBUG oslo_service.service 
[req-8c2f196d-5cac-430c-8194-1cc560e73636 - - - - -] 
notifications.notify_on_state_change = None log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744
  2017-03-10 16:34:34.418 13510 DEBUG oslo_service.service 
[req-310dc3b3-db07-4290-acec-f758d246452b - - - - -] 
notifications.notify_on_state_change = vm_and_task_state log_opt_values 
/openstack/venvs/nova-15.0.0/lib/python2.7/site-packages/oslo_config/cfg.py:2744

  No warning return. The 3rd line has the correct value after setting in
  [notifications] section.

  I'll submit the patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1671847/+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 1671883] [NEW] chpasswd regression

[Joshua Powers]

Public bug reported:

Last night's integration tests failed on a regression to the chpasswd
value. All three tested releases with the same failures:

set_password
set_password_expire
set_password_list

Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

set_password.yaml:  
  chpasswd: { expire: False }

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
plist = plist.spitlines()
AttributeError: 'str' object has no attribute 'spitlines'


set_password_expire.yaml:  
  chpasswd: { expire: True }

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
if isinstance(chfg['list'], list):
KeyError: 'list'


set_password_list.yaml:
  chpasswd:
list: |
  tom:mypassword123!
  dick:R
  harry:Random

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
plist = plist.spitlines()
AttributeError: 'str' object has no attribute 'spitlines'

** Affects: cloud-init
 Importance: High
 Status: Fix Committed

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

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

Title:
  chpasswd regression

Status in cloud-init:
  Fix Committed

Bug description:
  Last night's integration tests failed on a regression to the chpasswd
  value. All three tested releases with the same failures:

  set_password
  set_password_expire
  set_password_list

  Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
  
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

  set_password.yaml:  
chpasswd: { expire: False }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

  
  set_password_expire.yaml:  
chpasswd: { expire: True }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
  if isinstance(chfg['list'], list):
  KeyError: 'list'

  
  set_password_list.yaml:
chpasswd:
  list: |
tom:mypassword123!
dick:R
harry:Random

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  

[Yahoo-eng-team] [Bug 1671887] [NEW] Revocation API is used in places where where it doesn't need to be

[Lance Bragstad]

Public bug reported:

Since keystone now validates UUID and Fernet tokens the same way - by
rebuilding the token context at validation time, we no longer need to
persist certain types of revocation events.

For example, a revocation event is persisted when a role is deleted.
This is no longer needed because the invalidation happens by design of
the token provider.

Opening this bug so that we can track those cases and remove them.

** Affects: keystone
 Importance: Low
 Assignee: Richard (csravelar)
 Status: In Progress

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

** Changed in: keystone
   Importance: Undecided => Low

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

Title:
  Revocation API is used in places where where it doesn't need to be

Status in OpenStack Identity (keystone):
  In Progress

Bug description:
  Since keystone now validates UUID and Fernet tokens the same way - by
  rebuilding the token context at validation time, we no longer need to
  persist certain types of revocation events.

  For example, a revocation event is persisted when a role is deleted.
  This is no longer needed because the invalidation happens by design of
  the token provider.

  Opening this bug so that we can track those cases and remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1671887/+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 1671937] [NEW] chpasswd list fails

[Joshua Powers]

Public bug reported:

While trying to write an intergration test for the new method of
chpasswd via a list, cloud-init fails while attempting to change the
password for a user called ["['tom"]. It appears the list based method
is not being read correctly:

2017-03-10 20:25:43,934 - cc_set_passwords.py[DEBUG]: Changing password
for ["['tom"]:

cloud-conifg:
https://paste.ubuntu.com/24153626/

result:
https://paste.ubuntu.com/24153632/

** Affects: cloud-init
 Importance: Undecided
 Status: New

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

Title:
  chpasswd list fails

Status in cloud-init:
  New

Bug description:
  While trying to write an intergration test for the new method of
  chpasswd via a list, cloud-init fails while attempting to change the
  password for a user called ["['tom"]. It appears the list based method
  is not being read correctly:

  2017-03-10 20:25:43,934 - cc_set_passwords.py[DEBUG]: Changing
  password for ["['tom"]:

  cloud-conifg:
  https://paste.ubuntu.com/24153626/

  result:
  https://paste.ubuntu.com/24153632/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671937/+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 1540983] Re: Gate failures for neutron in test_dualnet_multi_prefix_slaac

[Ihar Hrachyshka]

** Changed in: neutron
 Assignee: Oleg Bondarev (obondarev) => (unassigned)

** Changed in: openstack-gate
   Status: Expired => Incomplete

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

Title:
  Gate failures for neutron in test_dualnet_multi_prefix_slaac

Status in neutron:
  Incomplete
Status in OpenStack-Gate:
  Incomplete

Bug description:
  24 hits in 7 days for logstash query : message:"in
  test_dualnet_multi_prefix_slaac" AND voting:1

  2016-02-02 14:35:49.054 | Captured traceback:
  2016-02-02 14:35:49.054 | ~~~
  2016-02-02 14:35:49.054 | Traceback (most recent call last):
  2016-02-02 14:35:49.054 |   File "tempest/test.py", line 113, in wrapper
  2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 246, in test_dualnet_multi_prefix_slaac
  2016-02-02 14:35:49.055 | dualnet=True)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 155, in _prepare_and_test
  2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = 
self.prepare_server(networks=net_list)
  2016-02-02 14:35:49.055 |   File "tempest/scenario/test_network_v6.py", 
line 128, in prepare_server
  2016-02-02 14:35:49.055 | username=username)
  2016-02-02 14:35:49.056 |   File "tempest/scenario/manager.py", line 390, 
in get_remote_client
  2016-02-02 14:35:49.056 | linux_client.validate_authentication()
  2016-02-02 14:35:49.056 |   File 
"tempest/common/utils/linux/remote_client.py", line 63, in 
validate_authentication
  2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth()
  2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 172, in test_connection_auth
  2016-02-02 14:35:49.056 | connection = self._get_ssh_connection()
  2016-02-02 14:35:49.056 |   File 
"/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py",
 line 87, in _get_ssh_connection
  2016-02-02 14:35:49.057 | password=self.password)
  2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection 
to the 172.24.5.141 via SSH timed out.
  2016-02-02 14:35:49.057 | User: cirros, Password: None

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540983/+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 1640319] Re: AttributeError: 'module' object has no attribute 'convert_to_boolean'

[Ihar Hrachyshka]

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

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

Title:
  AttributeError: 'module' object has no attribute 'convert_to_boolean'

Status in networking-midonet:
  Fix Released
Status in neutron:
  Fix Released
Status in openstack-ansible:
  Fix Released
Status in vmware-nsx:
  Fix Committed

Bug description:
  With latest neutron master code, neutron service q-svc could start due to the 
following error:
  2016-11-08 21:54:39.435 DEBUG oslo_concurrency.lockutils [-] Lock "manager" 
released by "neutron.manager._create_instance" :: held 1.467s from (pid=18534) 
inner /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:282
  2016-11-08 21:54:39.435 ERROR neutron.service [-] Unrecoverable error: please 
check log for details.
  2016-11-08 21:54:39.435 TRACE neutron.service Traceback (most recent call 
last):
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 87, in serve_wsgi
  2016-11-08 21:54:39.435 TRACE neutron.service service.start()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 63, in start
  2016-11-08 21:54:39.435 TRACE neutron.service self.wsgi_app = 
_run_wsgi(self.app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/service.py", line 289, in _run_wsgi
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
config.load_paste_app(app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/common/config.py", line 125, in load_paste_app
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
loader.load_app(app_name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/oslo_service/wsgi.py", line 353, in 
load_app
  2016-11-08 21:54:39.435 TRACE neutron.service return 
deploy.loadapp("config:%s" % self.config_path, name=name)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in 
loadapp
  2016-11-08 21:54:39.435 TRACE neutron.service return loadobj(APP, uri, 
name=name, **kw)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in 
loadobj
  2016-11-08 21:54:39.435 TRACE neutron.service return context.create()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in 
create
  2016-11-08 21:54:39.435 TRACE neutron.service return 
self.object_type.invoke(self)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in 
invoke
  2016-11-08 21:54:39.435 TRACE neutron.service **context.local_conf)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in 
fix_call
  2016-11-08 21:54:39.435 TRACE neutron.service val = callable(*args, **kw)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 31, in 
urlmap_factory
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
loader.get_app(app_name, global_conf=global_conf)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
  2016-11-08 21:54:39.435 TRACE neutron.service name=name, 
global_conf=global_conf).create()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in 
create
  2016-11-08 21:54:39.435 TRACE neutron.service return 
self.object_type.invoke(self)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in 
invoke
  2016-11-08 21:54:39.435 TRACE neutron.service **context.local_conf)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/util.py", line 55, in 
fix_call
  2016-11-08 21:54:39.435 TRACE neutron.service val = callable(*args, **kw)
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/opt/stack/neutron/neutron/auth.py", line 71, in pipeline_factory
  2016-11-08 21:54:39.435 TRACE neutron.service app = 
loader.get_app(pipeline[-1])
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
  2016-11-08 21:54:39.435 TRACE neutron.service name=name, 
global_conf=global_conf).create()
  2016-11-08 21:54:39.435 TRACE neutron.service   File 
"/usr/local/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in 

[Yahoo-eng-team] [Bug 1628377] Re: test_stack_update_replace_with_ip_rollback filure

[Ihar Hrachyshka]

** No longer affects: neutron

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

Title:
  test_stack_update_replace_with_ip_rollback filure

Status in heat:
  New

Bug description:
  heat integration tests test_stack_update_replace_with_ip_rollback
  failed with below error. Though there no previous occurrences of this
  error, I can see db errors in neutron logs[1].

  http://logs.openstack.org/39/377439/2/gate/gate-heat-dsvm-functional-
  convg-mysql-lbaasv2/8b93a55/console.html

  2016-09-28 04:06:13.600724 | 2016-09-28 04:06:13.600 | Captured traceback:
  2016-09-28 04:06:13.601965 | 2016-09-28 04:06:13.601 | ~~~
  2016-09-28 04:06:13.603681 | 2016-09-28 04:06:13.603 | Traceback (most 
recent call last):
  2016-09-28 04:06:13.605168 | 2016-09-28 04:06:13.604 |   File 
"/opt/stack/new/heat/heat_integrationtests/functional/test_create_update_neutron_port.py",
 line 119, in test_stack_update_replace_with_ip_rollback
  2016-09-28 04:06:13.607511 | 2016-09-28 04:06:13.606 | 
self.assertEqual(_id, new_id)
  2016-09-28 04:06:13.608660 | 2016-09-28 04:06:13.608 |   File 
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
  2016-09-28 04:06:13.611349 | 2016-09-28 04:06:13.611 | 
self.assertThat(observed, matcher, message)
  2016-09-28 04:06:13.613880 | 2016-09-28 04:06:13.613 |   File 
"/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
  2016-09-28 04:06:13.616079 | 2016-09-28 04:06:13.615 | raise 
mismatch_error
  2016-09-28 04:06:13.617343 | 2016-09-28 04:06:13.617 | 
testtools.matchers._impl.MismatchError: !=:
  2016-09-28 04:06:13.619135 | 2016-09-28 04:06:13.618 | reference = 
u'04c2e178-5c96-4f22-9072-faea92fa6560'
  2016-09-28 04:06:13.620321 | 2016-09-28 04:06:13.620 | actual= 
u'0255770f-e6a5-45de-b604-10c06f12d42c'

  [1]

  http://logs.openstack.org/39/377439/2/gate/gate-heat-dsvm-functional-
  convg-mysql-
  lbaasv2/8b93a55/logs/screen-q-svc.txt.gz#_2016-09-28_04_06_01_173

  2016-09-28 04:06:01.173 4912 DEBUG neutron.callbacks.manager 
[req-f70ab80e-2870-4bbe-aad0-1841203355d8 demo -] Notify callbacks 
[('neutron.db.l3_db._notify_routers_callback-8748586454487', ), 
('neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api.DhcpAgentNotifyAPI._native_event_send_dhcp_notification--9223372036829987228',
 >), 
('neutron.db.l3_dvrscheduler_db._notify_port_delete-8748585805241', )] for port, after_delete _notify_loop 
/opt/stack/new/neutron/neutron/callbacks/manager.py:142
  2016-09-28 04:06:01.173 4914 DEBUG neutron.db.api 
[req-dfcdfd65-63b9-45cd-913c-43f6287e2e37 - -] Retry wrapper got retriable 
exception: Traceback (most recent call last):
    File "/opt/stack/new/neutron/neutron/db/api.py", line 119, in wrapped
  return f(*dup_args, **dup_kwargs)
    File "/opt/stack/new/neutron/neutron/plugins/ml2/plugin.py", line 1733, in 
update_port_status
  context.session.flush()
    File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", 
line 2019, in flush
  self._flush(objects)
    File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", 
line 2137, in _flush
  transaction.rollback(_capture_exception=True)
    File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 
60, in __exit__
  compat.reraise(exc_type, exc_value, exc_tb)
    File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", 
line 2101, in _flush
  flush_context.execute()
    File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", 
line 373, in execute
  rec.execute(self)
    File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", 
line 532, in execute
  uow
    File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
170, in save_obj
  mapper, table, update)
    File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
728, in _emit_update_statements
  (table.description, len(records), rows))
  StaleDataError: UPDATE statement on table 'standardattributes' expected to 
update 1 row(s); 0 were matched.
   wrapped /opt/stack/new/neutron/neutron/db/api.py:124

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1628377/+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 1671921] [NEW] Boot from Volume invalid BDM

[Logan V]

Public bug reported:

Booting from volume in the new launch panel causes the following BDM:
{"server": {"name": "test", "imageRef": "", "availability_zone
  ": "us-dfw-1", "key_name": "test", "flavorRef": 
"9340639a-2883-48ca-811f-01519e527648", "block_device_mapping": [{"volume_id": 
"94426a92-5409-428d-8a26-81f94395d9ad", "delete_on_termination": "false", 
"device_name": "sda"}], "OS-DCF:diskConfig": "AUTO", "max_count": 1, 
"min_count": 1, "networks": [{"uuid
  ": "82ac236e-384a-420b-aa2c-3003f44cf782"}], "security_groups": [{"name": 
"4df780bf-b2c5-4c0e-acba-64b9b2f08eaa"}]}}

Nova rejects it with:
{"badRequest": {"message": "Block Device Mapping is Invalid: Boot sequence for 
the instance and image/block device mapping combin
  ation is not valid.", "code": 400}}}

It seems like it is missing a boot_index?

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Boot from Volume invalid BDM

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Booting from volume in the new launch panel causes the following BDM:
  {"server": {"name": "test", "imageRef": "", "availability_zone
": "us-dfw-1", "key_name": "test", "flavorRef": 
"9340639a-2883-48ca-811f-01519e527648", "block_device_mapping": [{"volume_id": 
"94426a92-5409-428d-8a26-81f94395d9ad", "delete_on_termination": "false", 
"device_name": "sda"}], "OS-DCF:diskConfig": "AUTO", "max_count": 1, 
"min_count": 1, "networks": [{"uuid
": "82ac236e-384a-420b-aa2c-3003f44cf782"}], "security_groups": [{"name": 
"4df780bf-b2c5-4c0e-acba-64b9b2f08eaa"}]}}

  Nova rejects it with:
  {"badRequest": {"message": "Block Device Mapping is Invalid: Boot sequence 
for the instance and image/block device mapping combin
ation is not valid.", "code": 400}}}

  It seems like it is missing a boot_index?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1671921/+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 1605278] Re: Merge python-django 1:1.10.3 from Debian unstable

[Jeremy Bicha]

** Also affects: python-django (Ubuntu Aa-series)
   Importance: Undecided
   Status: New

** Changed in: python-django (Ubuntu Aa-series)
   Status: New => In Progress

** Changed in: python-django (Ubuntu Aa-series)
   Importance: Undecided => Wishlist

** Changed in: python-django (Ubuntu Aa-series)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: python-django (Ubuntu Zesty)
   Status: In Progress => Won't Fix

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

Title:
  Merge python-django 1:1.10.3 from Debian unstable

Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in MAAS:
  Triaged
Status in python-django package in Ubuntu:
  In Progress
Status in python-django source package in Zesty:
  Won't Fix
Status in python-django source package in aa-series:
  In Progress

Bug description:
  Please merge python-django 1:1.9.8-1 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: XSS in admin's add/change related popup
  - debian/patches/CVE-2016-6186.patch: change to text in
django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js,
django/views/debug.py, added to tests in tests/admin_views/admin.py,
tests/admin_views/models.py, tests/admin_views/tests.py.
  - CVE-2016-6186
* Backport b1afebf882db5296cd9dcea26ee66d5250922e53 for ticket 26204 from
  upstream (1.8.10) to allow dashes in TLDs again (in the URL validator.)
  LP: #1528710
* Backport b1afebf882db5296cd9dcea26ee66d5250922e53 for ticket 26204 from
  upstream (1.8.10) to allow dashes in TLDs again (in the URL validator.)
  LP: #1528710
* SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251)
  - debian/patches/CVE-2016-2512-regression.patch: updated to final
upstream fix.
  - CVE-2016-2512
* SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251)
  - debian/patches/CVE-2016-2512-regression.patch: force url to unicode
in django/utils/http.py, added test to
tests/utils_tests/test_http.py.
  - CVE-2016-2512
* SECURITY UPDATE: malicious redirect and possible XSS attack via
  user-supplied redirect URLs containing basic auth
  - debian/patches/CVE-2016-2512.patch: prevent spoofing in
django/utils/http.py, added test to tests/utils_tests/test_http.py.
  - CVE-2016-2512
* SECURITY UPDATE: user enumeration through timing difference on password
  hasher work factor upgrade
  - debian/patches/CVE-2016-2513.patch: fix timing in
django/contrib/auth/hashers.py, added note to
docs/topics/auth/passwords.txt, added tests to
tests/auth_tests/test_hashers.py.
  - CVE-2016-2513
* Merge from Debian unstable. Remaining changes:
  - debian/patches/pymysql-replacement.patch: Use pymysql as drop in
replacement for MySQLdb.
  - debian/control: Drop python-mysqldb in favor of python-pymysql.
* Dropped changes:
  - debian/patches/99_skip_tests_due_python35.diff: no longer required,
python 3.5 is now officially supported in 1.8.6+.

  All of that was applied in the new Debian version except for the
  pymysql replacement.

  Changelog entries since current yakkety version 1.8.7-1ubuntu6:

  python-django (1:1.9.8-1) unstable; urgency=high

* New upstream security release:
  https://www.djangoproject.com/weblog/2016/jul/18/security-releases/
  - CVE-2016-6186: XSS in admin's add/change related popup

   -- Luke Faraone   Tue, 19 Jul 2016 14:15:24
  +

  python-django (1:1.9.7-2) unstable; urgency=medium

* Re-upload 1.9.7 to unstable with epoch.

   -- Chris Lamb   Sun, 26 Jun 2016 09:58:19 +0200

  python-django (1.10~beta1-1) unstable; urgency=medium

[ Chris Lamb ]
* New upstream beta release.
* Drop fix-25761-add-traceback-attribute.patch; applied upstream.

[ Raphaël Hertzog ]
* Remove obsolete /etc/bash_completion.d/django_bash_completion on upgrade.
  Closes: #801744

   -- Chris Lamb   Sat, 25 Jun 2016 19:17:49 +0200

  python-django (1.9.7-1) unstable; urgency=medium

[ Raphaël Hertzog ]
* New upstream bugfix release.
* Bump python-sphinx build dependency to >= 1.3. Closes: #824108
* Drop build dependency on locales. C.UTF-8 that we currently use is part of
  libc-bin.

[ Chris Lamb ]
* Remove duplicated "of of" in python-django's README.Debian.

   -- Raphaël Hertzog   Tue, 14 Jun 2016 00:05:22
  +0200

  python-django (1.9.6-1) unstable; urgency=medium

* New upstream bugfix release.

   -- Chris Lamb   Sat, 07 May 2016 07:01:17 +0100

  python-django (1.9.5-2) unstable; urgency=medium

* Drop the 

[Yahoo-eng-team] [Bug 1656781] Re: api-ref: wrong parameters and missing parameters in os-keypairs.inc

[OpenStack Infra]

Reviewed:  https://review.openstack.org/420626
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=2800b53836b9ce13f3806e488f63c096fda2141c
Submitter: Jenkins
Branch:master

commit 2800b53836b9ce13f3806e488f63c096fda2141c
Author: Takashi NATSUME 
Date:   Mon Jan 16 18:42:21 2017 +0900

api-ref: Fix keypair API parameters

Fix parameter types and the order of parameters.
Add missing parameters.
Add a period at the end of a parameter description.
Replace sample files with v2.10 files.

Change-Id: I9d8d20b42c7d32e11af479e79c9c9e8475421302
Closes-Bug: #1656781


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

Title:
  api-ref: wrong parameters and missing parameters in os-keypairs.inc

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  http://developer.openstack.org/api-ref/compute/#keypairs-keypairs

  There are wrong parameters and missing parameters in Keypairs API
  Reference (os-keypairs.inc).

  * List Keypairs
- Missing "keypair" object parameter
  * Create Or Import Keypair
- 'type' parameter in request should be 'body' parameter instead of 'query' 
parameter.
-  'private_key' parameter in response shoud be after required parameters 
and before microverion parameters.
  * Show Keypair Details
- 'use_id' parameter should be 'query' parameter instead of 'body' 
parameter.
- 'type' parameter in reponse should be at the end because it is 
microversion parameter.
- Missing parameters(created_at, deleted, deleted_at, updated_at, id)
  * Delete Keypair
- 'use_id' parameter should be 'query' parameter instead of 'body' 
parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1656781/+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 1665263] Re: instance.delete notification is missing for unscheduled instance

[OpenStack Infra]

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

commit f9ac9531fb3259fe83642dce92d0d1901d0f067e
Author: Balazs Gibizer 
Date:   Thu Mar 9 17:28:02 2017 +0100

Fix missing instance.delete notification

The I8742071b55f018f864f5a382de20075a5b444a79 introduced cases when an
instance object is destroyed without the instance.delete notification
being emitted.

This patch adds the necessary notification to restore legacy
behaviour.

Closes-Bug: #1665263
Change-Id: I55ce90ca34c927c5dcd340fa5bdb0607a4ad4971


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

Title:
  instance.delete notification is missing for unscheduled instance

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  Description
  ===
  It seems that the Move instance creation to conductor commit [1] changed when 
and how the instance.delete notification is emitted for an unscheduled 
instance. Unfortunately the legacy notification doesn't have test coverage and 
the versioned notification coverage are still on review [2] for this case.

  Before [1] the instance.delete for an unscheduled instance is emitted from 
here [3]. But after [1] the execution of the same delete operation goes to a 
new direction [4] and never reaches [3].
  Before [1] the new test coverage in [2] was passing but now after [1] is 
merged the test_create_server_error fails as the instance.delete notification 
is not emitted.

  [1] https://review.openstack.org/#/c/319379
  [2] https://review.openstack.org/#/c/410297
  [3] https://review.openstack.org/#/c/410297/9/nova/compute/api.py@1860
  [4] https://review.openstack.org/#/c/319379/84/nova/compute/api.py@1790

  
  Steps to reproduce
  ==

  Run the nova functional test in patch [2] before and after commit [1].
  The test_create_server_error will pass before and fail after commit
  [1] due to missing instance.delete notification.

  
  Environment
  ===

  Nova functional test env with based on commit
  f9d7b383a7cb12b6cd3e6117daf69b08620bf40f

  Logs & Configs
  ==

  http://logs.openstack.org/97/410297/9/check/gate-nova-tox-functional-
  ubuntu-xenial/5875492/console.html#_2017-02-15_16_21_06_668774

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1665263/+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 1671911] [NEW] Modified project information and members but unable to modify project quotas when modifying volume quota in horizon admin identity view

[Andreas Karis]

Public bug reported:

Description of problem:
Modified project information and members but unable to modify project quotas 
when modifying volume quota in horizon admin identity view

Go to Identity -> Identity -> Projects, modify the quotas of a project
and set volumes to another value.

Spot check shows that:
- vCPUs and instances **do** update, but the error message still shows
- volumes do **not** update


Version-Release number of selected component (if applicable):
[root@overcloud-controller-0 ~]# rpm -qf 
/usr/share/openstack-dashboard/openstack_dashboard/dashboards/identity/projects/workflows.py
openstack-dashboard-10.0.1-5.el7ost.noarch

Actual results:
volumes quotas do not update, error message shows

Expected results:
update volume quotas, no error message

Additional info:

The problem in the code with integer / string conversion: 
~~~
==> /var/log/cinder/api.log <==
2017-03-09 17:55:41.871 103796 DEBUG eventlet.wsgi.server [-] (103796) accepted 
('172.16.2.4', 45808) server 
/usr/lib/python2.7/site-packages/eventlet/wsgi.py:867
2017-03-09 17:55:41.878 103796 INFO cinder.api.openstack.wsgi 
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a 
d809ec86f152486981e1782e94fa7b2d - default default] PUT 
http://10.0.0.4:8776/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
2017-03-09 17:55:41.879 103796 DEBUG cinder.api.openstack.wsgi 
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a 
d809ec86f152486981e1782e94fa7b2d - default default] Action: 'update', calling 
method: >, body: 
{"quota_set": {"gigabytes": null, "tenant_id": 
"d809ec86f152486981e1782e94fa7b2d", "volumes": 21, "snapshots": null}} 
_process_stack /usr/lib/python2.7/site-packages/cinder/api/openstack/wsgi.py:868
2017-03-09 17:55:41.977 103796 INFO cinder.api.openstack.wsgi 
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a 
d809ec86f152486981e1782e94fa7b2d - default default] HTTP exception thrown: 
gigabytes must be an integer.
2017-03-09 17:55:41.978 103796 INFO cinder.api.openstack.wsgi 
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a 
d809ec86f152486981e1782e94fa7b2d - default default] 
http://10.0.0.4:8776/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
 returned with HTTP 400
2017-03-09 17:55:41.980 103796 INFO eventlet.wsgi.server 
[req-2e2563df-a8f4-436a-83b5-93f6a483a826 aaafa6c0557b4ed89b2803af8149743a 
d809ec86f152486981e1782e94fa7b2d - default default] 172.16.2.4 "PUT 
/v2/d809ec86f152486981e1782e94fa7b2d/os-quota-sets/d809ec86f152486981e1782e94fa7b2d
 HTTP/1.1" status: 400  len: 335 time: 0.1074338
~~~

When saving the quotas from the web interface, the following happens:
~~~
POST /dashboard/identity/53f4466c084145e0b91296f68be517a6/update/ HTTP/1.1
Host: 10.0.0.4
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:51.0) Gecko/20100101 
Firefox/51.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
Referer: http://10.0.0.4/dashboard/identity/
Content-Length: 1616
Cookie: login_region="http://172.16.2.10:5000/v2.0;; login_domain=; 
SERVERID=overcloud-controller-0; csrftoken=8DM2AJOQIfjEN9rHBic3BzZrxoPYvnnP; 
sessionid=wk7y07jc7938xe6zu0ushg3micrq3aus
Connection: keep-alive

csrfmiddlewaretoken=8DM2AJOQIfjEN9rHBic3BzZrxoPYvnnP_id=default_name=Default=service=Tenant+for+the+openstack+services=on_update_members_filter=_members_members_filter=_update_members_role=9fe2ff9ee4384b1894a90878d3e92bab_members_role_64f3a3e25453466cac4325df17b64694=1de8b8db8a224b4f972853d4787d7a63_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=b5104f5fc1f844979ddd7023d3ed38e2_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=8c6c981aa56f4ae1ad1b999bc94575a7_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=930ff1e6c81a4fedab4e61c5286c6667_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=043ea3a59f9f4f539866e4171f0dced8_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=cc6f8622d68644d8a02d915ecb731fa2_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=7028ebf145a34803826916968e68253a_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=1de8b8db8a224b4f972853d4787d7a63_members_role_cd3a
 
65a0a92f4fdc8badb7d1c87395fe=31b239bbb61d421c8636a8a03343f1cc_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=b77fb7185f0b479abd286702e359953c_members_role_cd3a65a0a92f4fdc8badb7d1c87395fe=586416a8b2c34a94a88ee73035fb92e8_update_group_members_role=9fe2ff9ee4384b1894a90878d3e92bab==_ips=_ips=_groups=_group_rules==_networks=_items=128=20=10_files=5_file_content_bytes=10240=11=51200_group=10_group_rule=100=50=10=50=10=10
~~~

Which means that, e.g. 'gigabytes=' which then gets set to NULL.

The answer to this post request is:
~~~
HTTP/1.1 200 OK
Date: Thu, 09 Mar 2017 18:19:26 GMT
Server: Apache
X-Horizon-Location: /dashboard/identity/
Vary: Cookie
Set-Cookie: 

[Yahoo-eng-team] [Bug 1630257] Re: DBDeadlock occurs during test_dualnet_multi_prefix_dhcpv6_stateless

[Ihar Hrachyshka]

*** This bug is a duplicate of bug 1509004 ***
https://bugs.launchpad.net/bugs/1509004

** This bug is no longer a duplicate of bug 1533194
   Gate failures for neutron in TestGettingAddress
** This bug has been marked a duplicate of bug 1509004
   "test_dualnet_dhcp6_stateless_from_os" failures seen in the gate

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

Title:
  DBDeadlock occurs during test_dualnet_multi_prefix_dhcpv6_stateless

Status in neutron:
  New

Bug description:
  The test test_dualnet_multi_prefix_dhcpv6_stateless
  
(tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless[compute
  ,id-cf1c4425-766b-45b8-be35-e2959728eb00,network]) failed with error
  on python-openstackclient gates:

  2016-10-04 13:59:59.811433 | Captured traceback:
  2016-10-04 13:59:59.811450 | ~~~
  2016-10-04 13:59:59.811471 | Traceback (most recent call last):
  2016-10-04 13:59:59.811513 |   File "tempest/test.py", line 107, in 
wrapper
  2016-10-04 13:59:59.811558 | return f(self, *func_args, **func_kwargs)
  2016-10-04 13:59:59.811616 |   File 
"tempest/scenario/test_network_v6.py", line 256, in 
test_dualnet_multi_prefix_dhcpv6_stateless
  2016-10-04 13:59:59.811640 | dualnet=True)
  2016-10-04 13:59:59.811672 |   File 
"tempest/scenario/test_network_v6.py", line 203, in _prepare_and_test
  2016-10-04 13:59:59.811696 | self.subnets_v6[i]['gateway_ip'])
  2016-10-04 13:59:59.811728 |   File 
"tempest/scenario/test_network_v6.py", line 213, in _check_connectivity
  2016-10-04 13:59:59.811751 | (dest, source.ssh_client.host)
  2016-10-04 13:59:59.811794 |   File 
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py",
 line 702, in assertTrue
  2016-10-04 13:59:59.811818 | raise self.failureException(msg)
  2016-10-04 13:59:59.811857 | AssertionError: False is not true : Timed 
out waiting for 2003::1 to become reachable from 172.24.5.14

  http://logs.openstack.org/11/376311/3/check/gate-tempest-dsvm-neutron-
  src-python-openstackclient/04dabcd/console.html

  At this time in neutron-server logs DBDeadlock occurs:

  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers Traceback 
(most recent call last):
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/opt/stack/new/neutron/neutron/plugins/ml2/managers.py", line 433, in 
_call_on_drivers
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
getattr(driver.obj, method_name)(context)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py", line 60, in 
create_port_precommit
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
self._insert_provisioning_block(context)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py", line 83, in 
_insert_provisioning_block
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
provisioning_blocks.L2_AGENT_ENTITY)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/opt/stack/new/neutron/neutron/db/api.py", line 159, in wrapped
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers return 
method(*args, **kwargs)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/opt/stack/new/neutron/neutron/db/provisioning_blocks.py", line 74, in 
add_provisioning_component
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
context.session.add(record)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 490, 
in __exit__
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
self.rollback()
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 
60, in __exit__
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
compat.reraise(exc_type, exc_value, exc_tb)
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 487, 
in __exit__
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
self.commit()
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 392, 
in commit
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers 
self._prepare_impl()
  2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", 

[Yahoo-eng-team] [Bug 1617282] Re: functional gate failed with git clone timeout on fetching ovs from github

[Ihar Hrachyshka]

Fixed by https://review.openstack.org/#/c/437041

** Changed in: neutron
   Status: Confirmed => 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/1617282

Title:
  functional gate failed with git clone timeout on fetching ovs from
  github

Status in neutron:
  Fix Released
Status in openvswitch package in Ubuntu:
  Confirmed

Bug description:
  http://logs.openstack.org/68/351368/23/check/gate-neutron-dsvm-
  functional/0d68031/console.html

  2016-08-25 10:06:34.915685 | fatal: unable to access 
'https://github.com/openvswitch/ovs.git/': Failed to connect to github.com port 
443: Connection timed out
  2016-08-25 10:06:34.920456 | + functions-common:git_timed:603   :   
[[ 128 -ne 124 ]]
  2016-08-25 10:06:34.921769 | + functions-common:git_timed:604   :   
die 604 'git call failed: [git clone' https://github.com/openvswitch/ovs.git 
'/opt/stack/new/ovs]'
  2016-08-25 10:06:34.922982 | + functions-common:die:186 :   
local exitcode=0
  2016-08-25 10:06:34.924373 | + functions-common:die:187 :   
set +o xtrace
  2016-08-25 10:06:34.924404 | [Call Trace]
  2016-08-25 10:06:34.924430 | 
/opt/stack/new/neutron/neutron/tests/contrib/gate_hook.sh:53:compile_ovs
  2016-08-25 10:06:34.924447 | 
/opt/stack/new/neutron/devstack/lib/ovs:57:git_timed
  2016-08-25 10:06:34.924463 | /opt/stack/new/devstack/functions-common:604:die
  2016-08-25 10:06:34.926689 | [ERROR] 
/opt/stack/new/devstack/functions-common:604 git call failed: [git clone 
https://github.com/openvswitch/ovs.git /opt/stack/new/ovs]

  I guess we should stop pulling OVS from github. Instead, we could use
  Xenial platform that already provides ovs == 2.5 from .deb packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1617282/+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 1671883] Re: chpasswd regression

[Joshua Powers]

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

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

Title:
  chpasswd regression

Status in cloud-init:
  Fix Released

Bug description:
  Last night's integration tests failed on a regression to the chpasswd
  value. All three tested releases with the same failures:

  set_password
  set_password_expire
  set_password_list

  Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
  
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

  set_password.yaml:  
chpasswd: { expire: False }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

  
  set_password_expire.yaml:  
chpasswd: { expire: True }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
  if isinstance(chfg['list'], list):
  KeyError: 'list'

  
  set_password_list.yaml:
chpasswd:
  list: |
tom:mypassword123!
dick:R
harry:Random

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671883/+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 1671927] [NEW] init local crash - unknown subnet type 'loopback'

[Dan Peschman]

Public bug reported:

cloud-init-0.7.8-5.fc25.noarch on Fedora 25
Data source: ConfigDrive
Cloud provider: Openstack

Local init ($ cloud-init init -l) crashes with error [Unknown subnet
type 'loopback' found for interface 'lo'].  Stack trace attached.

I have a config drive w/ Ubuntu-style interface file at
sr0/openstack/content/, and network_data.json at
sr0/openstack/latest/.  Only  defines the loopback device.
Screenshots of these files are at http://imgur.com/a/qEElh.

Expected outcome is to render ifcfg-eth0 in /etc/sysconfig/network-
scripts, but leave ifcfg-lo in that directory untouched as per previous
versions, for instance cloud-init-0.7.6-5.20140218bzr1060.fc23.noarch on
Fedora 23.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Attachment added: "callstack.png"
   
https://bugs.launchpad.net/bugs/1671927/+attachment/4835495/+files/callstack.png

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

Title:
  init local crash - unknown subnet type 'loopback'

Status in cloud-init:
  New

Bug description:
  cloud-init-0.7.8-5.fc25.noarch on Fedora 25
  Data source: ConfigDrive
  Cloud provider: Openstack

  Local init ($ cloud-init init -l) crashes with error [Unknown subnet
  type 'loopback' found for interface 'lo'].  Stack trace attached.

  I have a config drive w/ Ubuntu-style interface file at
  sr0/openstack/content/, and network_data.json at
  sr0/openstack/latest/.  Only  defines the loopback device.
  Screenshots of these files are at http://imgur.com/a/qEElh.

  Expected outcome is to render ifcfg-eth0 in /etc/sysconfig/network-
  scripts, but leave ifcfg-lo in that directory untouched as per
  previous versions, for instance cloud-
  init-0.7.6-5.20140218bzr1060.fc23.noarch on Fedora 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671927/+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 1629097] Re: neutron-rootwrap processes not getting cleaned up

[Billy Olsen]

I saw this last night, and can indeed confirm its related to DNS issues.
It was suggested by a colleague that it may be related to the sudo call
returning an error indicating that the hostname could not be found,
though I spent no time exploring this option today. Restarting the
openvswitch-switch service closes all the existing processes but it
seems more that the service can't stop cleanly. Also of note is that the
service stop took a very long time, whereas with working DNS it took a
few seconds at worst.

** Changed in: neutron
   Status: Expired => Confirmed

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

Title:
  neutron-rootwrap processes not getting cleaned up

Status in neutron:
  Confirmed

Bug description:
  neutron-rootwrap processes aren't getting cleaned up on Newton.  I'm
  testing with Newton rc3.

  I was noticing memory exhaustion on my neutron gateway units, which turned 
out to be due to compounding neutron-rootwrap processes:
  sudo /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovsdb-client 
monitor Interface name,ofport,external_ids --format=json

  $ top -n1 -b -o VIRT
  http://paste.ubuntu.com/23252407/

  $ ps aux|grep ovsdb-client
  http://paste.ubuntu.com/23252658/

  Restarting openvswitch cleans up the processes but they just start piling 
again up soon after:
  sudo systemctl restart openvswitch-switch

  At first I thought this was an openvswitch issue, however I reverted
  the code in get_root_helper_child_pid() and neutron-rootwrap processes
  started getting cleaned up. See corresponding commit for code that
  possibly introduced this at [1].

  This can be recreated with the openstack charms using xenial-newton-
  staging.  On newton deploys, neutron-gateway and nova-compute units
  will exhaust memory due to compounding ovsdb-client processes.

  [1]
  commit fd93e19f2a415b3803700fc491749daba01a4390
  Author: Assaf Muller 
  Date:   Fri Mar 18 16:29:26 2016 -0400

  Change get_root_helper_child_pid to stop when it finds cmd

  get_root_helper_child_pid recursively finds the child of pid,
  until it can no longer find a child. However, the intention is
  not to find the deepest child, but to strip away root helpers.
  For example 'sudo neutron-rootwrap x' is supposed to find the
  pid of x. However, in cases 'x' spawned quick lived children of
  its own (For example: ip / brctl / ovs invocations),
  get_root_helper_child_pid returned those pids if called in
  the wrong time.

  Change-Id: I582aa5c931c8bfe57f49df6899445698270bb33e
  Closes-Bug: #1558819

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1629097/+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 1439645] Re: nova can't schedule instance with libvirt-xen driver

[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/1439645

Title:
  nova can't schedule instance  with libvirt-xen driver

Status in OpenStack Compute (nova):
  Expired
Status in nova package in Ubuntu:
  Expired

Bug description:
  This issue is closely related to bug
  https://bugs.launchpad.net/nova/+bug/1425115.

  Applying patch 
  $ git fetch https://review.openstack.org/openstack/nova 
refs/changes/06/159106/5 && git checkout FETCH_HEAD
  in /opt/stack/nova

  I was able to shutdown and restart system via ./rejoin-stack.sh with
  nova-compute up and running

  ubuntu@ubuntu-wks:~/devstack$ nova service-list
  
++--++--+-+---++-+
  | Id | Binary   | Host   | Zone | Status  | State | 
Updated_at | Disabled Reason |
  
++--++--+-+---++-+-
  | 1  | nova-conductor| ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 2  | nova-cert   | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 3  | nova-scheduler | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 4  | nova-consoleauth | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 5  | nova-compute   | ubuntu-wks | nova | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  
++--++--+-+---++--

  However, attempt to launch instance fails, n-sch.log reports :-

  2015-04-02 06:16:51.248 ^[[00;36mINFO nova.filters
  [^[[00;36m-^[[00;36m] ^[[01;35m^[[00;36mFilter RetryFilter returned 0
  hosts^[[00m^M

  My local.conf

  [[local|localrc]]
  HOST_IP=192.168.1.50
  ADMIN_PASSWORD=secret
  DATABASE_PASSWORD=$ADMIN_PASSWORD
  RABBIT_PASSWORD=$ADMIN_PASSWORD
  SERVICE_PASSWORD=$ADMIN_PASSWORD
  SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50

  FLOATING_RANGE=192.168.10.0/24
  FLAT_INTERFACE=eth0
  Q_FLOATING_ALLOCATION_POOL=start=192.168.10.150,end=192.168.10.254
  PUBLIC_NETWORK_GATEWAY=192.168.10.15

  # Useful logging options for debugging:
  DEST=/opt/stack
  LOGFILE=$DEST/logs/stack.sh.log
  SCREEN_LOGDIR=$DEST/logs/screen

  # The default fixed range (10.0.0.0/24) conflicted with an address
  # range I was using locally.
  FIXED_RANGE=10.254.1.0/24
  NETWORK_GATEWAY=10.254.1.1

  # Services
  disable_service n-net
  enable_service q-svc
  enable_service q-agt
  enable_service q-dhcp
  enable_service q-l3
  enable_service q-meta
  enable_service horizon
  disable_service tempest

  # This is a Xen Project host:
  LIBVIRT_TYPE=xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1439645/+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 1439645] Re: nova can't schedule instance with libvirt-xen driver

[Launchpad Bug Tracker]

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

** Changed in: nova (Ubuntu)
   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/1439645

Title:
  nova can't schedule instance  with libvirt-xen driver

Status in OpenStack Compute (nova):
  Expired
Status in nova package in Ubuntu:
  Expired

Bug description:
  This issue is closely related to bug
  https://bugs.launchpad.net/nova/+bug/1425115.

  Applying patch 
  $ git fetch https://review.openstack.org/openstack/nova 
refs/changes/06/159106/5 && git checkout FETCH_HEAD
  in /opt/stack/nova

  I was able to shutdown and restart system via ./rejoin-stack.sh with
  nova-compute up and running

  ubuntu@ubuntu-wks:~/devstack$ nova service-list
  
++--++--+-+---++-+
  | Id | Binary   | Host   | Zone | Status  | State | 
Updated_at | Disabled Reason |
  
++--++--+-+---++-+-
  | 1  | nova-conductor| ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 2  | nova-cert   | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 3  | nova-scheduler | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 4  | nova-consoleauth | ubuntu-wks | internal | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  | 5  | nova-compute   | ubuntu-wks | nova | enabled | up| 
2015-04-02T11:06:02.00 | -   |
  
++--++--+-+---++--

  However, attempt to launch instance fails, n-sch.log reports :-

  2015-04-02 06:16:51.248 ^[[00;36mINFO nova.filters
  [^[[00;36m-^[[00;36m] ^[[01;35m^[[00;36mFilter RetryFilter returned 0
  hosts^[[00m^M

  My local.conf

  [[local|localrc]]
  HOST_IP=192.168.1.50
  ADMIN_PASSWORD=secret
  DATABASE_PASSWORD=$ADMIN_PASSWORD
  RABBIT_PASSWORD=$ADMIN_PASSWORD
  SERVICE_PASSWORD=$ADMIN_PASSWORD
  SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50

  FLOATING_RANGE=192.168.10.0/24
  FLAT_INTERFACE=eth0
  Q_FLOATING_ALLOCATION_POOL=start=192.168.10.150,end=192.168.10.254
  PUBLIC_NETWORK_GATEWAY=192.168.10.15

  # Useful logging options for debugging:
  DEST=/opt/stack
  LOGFILE=$DEST/logs/stack.sh.log
  SCREEN_LOGDIR=$DEST/logs/screen

  # The default fixed range (10.0.0.0/24) conflicted with an address
  # range I was using locally.
  FIXED_RANGE=10.254.1.0/24
  NETWORK_GATEWAY=10.254.1.1

  # Services
  disable_service n-net
  enable_service q-svc
  enable_service q-agt
  enable_service q-dhcp
  enable_service q-l3
  enable_service q-meta
  enable_service horizon
  disable_service tempest

  # This is a Xen Project host:
  LIBVIRT_TYPE=xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1439645/+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 1653221] Re: availability_zone field is missing from the service.update notification payload

[OpenStack Infra]

Reviewed:  https://review.openstack.org/415857
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=655942069aa77abad90a742cd47690a81987e9d7
Submitter: Jenkins
Branch:master

commit 655942069aa77abad90a742cd47690a81987e9d7
Author: Balazs Gibizer 
Date:   Fri Jan 13 11:00:25 2017 +0100

handle uninited fields in notification payload

Due to the not strict handling of uninitialized fields during
notification payload population it is possible that the emitted
notification missing some of the fields defined in the schema.

There are two problematic cases:
1) no load tirggered for lazy loaded fields. If the field was not
   loaded it is not added to the payload.
2) uninitialized, not lazy loadable fields are not added to the
   payload.

This patch makes sure that lazy load is triggered. If the field is
not lazy loadable and also not initialized then related payload
field will be set to None. If the payload field is not nullable
the code will fail to make sure that the inconsistency is detected.

The following changes cannot be split to different commits because
as soon as the generic schema population code is fixed every listed
notification starts behaving differently.

In some cases the availability_zone field of the Service object is left
unitialized by both the constructor and the obj_load_attr function this
caused that the availability_zone field of the service.update
notification was missing from the emitted notification payload.

The extra_specs field of the Flavor object is not lazy loadable and not
initialized in the Flavor destroy case. So the extra_specs field of the
FlavorPayload needed to be made nullable.

The projects field of the Flavor object is lazy loaded but when the
Flavor object is loaded as part of an Instance object Flavor is
orphaned and no lazy load is allowed on that Flavor object. In this
case the projects field of the FlavorPayload will be set to None to
signal that the information is not available. This also means that
the projects field of the FlavorPayload needed to be changed to
nullable.

The hosts and id fields of the Aggregate object is not initialized
during the create of the Aggregate before the aggregate.create.start
needs to be sent. Therefore these fields needs to be nullable.

Closes-Bug: #1653221
Change-Id: Ib122cd98ee0cc31938d5ff1d5c753053267a3bd4


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

Title:
  availability_zone field is missing from the service.update
  notification payload

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===

  The payload of the service.update notification is defined to contain
  the availability_zone of the service however if there is no
  availability zone is associated to the service the field was missing
  from the notification payload.

  Steps to reproduce
  ==
  1) set up a devstack with log notification driver
  2) disable the state of one of the nova service with
  nova service disable
  3) check the log to see the content of the emitted service.update notification

  Expected result
  ===
  {
  "priority": "INFO",
  "payload": {
  "nova_object.namespace": "nova",
  "nova_object.name": "ServiceStatusPayload",
  "nova_object.version": "1.0",
  "nova_object.data": {
  "host": "host1",
  "disabled": false,
  "last_seen_up": "2012-10-29T13:42:05Z",
  "binary": "nova-compute",
  "topic": "compute",
  "disabled_reason": null,
  "report_count": 1,
  "forced_down": false,
  "version": 15
  "availability_zone": null
  }
  },
  "event_type": "service.update",
  "publisher_id": "nova-compute:host1"
  }

  
  Actual result
  =
  {
  "priority": "INFO",
  "payload": {
  "nova_object.namespace": "nova",
  "nova_object.name": "ServiceStatusPayload",
  "nova_object.version": "1.0",
  "nova_object.data": {
  "host": "host1",
  "disabled": false,
  "last_seen_up": "2012-10-29T13:42:05Z",
  "binary": "nova-compute",
  "topic": "compute",
  "disabled_reason": null,
  "report_count": 1,
  "forced_down": false,
  "version": 15
  }
  },
  "event_type": "service.update",
  "publisher_id": "nova-compute:host1"
  }

  Environment
  ===
  devstack with nova master a74d3ae4e815e3727961ef67bd801dada0267a0b

[Yahoo-eng-team] [Bug 1671373] Re: 'Invalid credentials with the provider'

[Andrey Volkov]

I believe it could be credentials indeed or configuration problem, not nova.
Please, see example: http://ix.io/oRj

** Changed in: nova
   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/1671373

Title:
  'Invalid credentials with the provider'

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Hi,

  I have some issues with libcloud library when trying to retrieve the
  openstack instance details. Please let me know if you have any idea on
  the below error. This error is not seen in kilo setup.

  --
  >>> driver.list_nodes()
  Traceback (most recent call last):
  File "/home/s.viswanathan/GV/lib/cloudlib.py", line 94, in show_instances
  ERROR 2017-03-07 04:04:20 nodes = sess.list_nodes()
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/compute/drivers/openstack.py", 
line 177, in list_nodes
  ERROR 2017-03-07 04:04:20 self.connection.request('/servers/detail', 
params=params).object)
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack.py", line 
227, in request
  ERROR 2017-03-07 04:04:20 raw=raw)
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/base.py", line 757, in 
request
  ERROR 2017-03-07 04:04:20 action = self.morph_action_hook(action)
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack.py", line 
294, in morph_action_hook
  ERROR 2017-03-07 04:04:20 self._populate_hosts_and_request_paths()
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack.py", line 
327, in _populate_hosts_and_request_paths
  ERROR 2017-03-07 04:04:20 osa = osa.authenticate(**kwargs)  # may throw 
InvalidCreds
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack_identity.py", 
line 855, in authenticate
  ERROR 2017-03-07 04:04:20 return self._authenticate_2_0_with_password()
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack_identity.py", 
line 880, in _authenticate_2_0_with_password
  ERROR 2017-03-07 04:04:20 return self._authenticate_2_0_with_body(reqbody)
  ERROR 2017-03-07 04:04:20   File 
"/usr/local/lib/python2.7/dist-packages/libcloud/common/openstack_identity.py", 
line 888, in _authenticate_2_0_with_body
  ERROR 2017-03-07 04:04:20 raise InvalidCredsError()
  ERROR 2017-03-07 04:04:20 InvalidCredsError: 'Invalid credentials with the 
provider' 
  --

  
  I have tried from python interpreter manually also, seen same problem.

  from libcloud.compute.types import Provider
  from libcloud.compute.providers import get_driver
  import libcloud.security
  OpenStack = get_driver(Provider.OPENSTACK)
  driver = OpenStack('sathya', 
'sathya',ex_force_auth_url='http://x.x.x.x:5000',ex_force_auth_version='2.0_password')
  driver.list_nodes()

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1671373/+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 1671785] [NEW] Missing router tab in Horizon Openstack Newton

[Viggo Ahl]

Public bug reported:

In Horizon, when clicking on the admin | System Information.

In the apache2.error log the following message appear

[Fri Mar 10 09:18:35.676770 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
 File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/tables/base.py",
 line 1500, in render_row_actions
[Fri Mar 10 09:18:35.676772 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
   bound_actions = self.get_row_actions(datum)
[Fri Mar 10 09:18:35.676774 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
 File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/tables/base.py",
 line 1452, in get_row_actions
[Fri Mar 10 09:18:35.676777 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
   bound_action.bound_url = bound_action.get_link_url(datum)
[Fri Mar 10 09:18:35.676779 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
 File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/info/tables.py",
 line 188, in get_link_url
[Fri Mar 10 09:18:35.676781 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
   args=(obj_id,))
[Fri Mar 10 09:18:35.676783 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
 File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 571, 
in reverse
[Fri Mar 10 09:18:35.676785 2017] [wsgi:error] [pid 23173:tid 139844567475968]  
   (key, ':'.join(resolved_path)))
[Fri Mar 10 09:18:35.676786 2017] [wsgi:error] [pid 23173:tid 139844567475968] 
TemplateSyntaxError: u'routers' is not a registered namespace inside 
'horizon:admin'

Also there is no choose in the admin tab: Router. Which seems to be
missing.

The installation is Openstack Newton on Ubuntu 16.04 LTS.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Missing router tab in Horizon Openstack Newton

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In Horizon, when clicking on the admin | System Information.

  In the apache2.error log the following message appear

  [Fri Mar 10 09:18:35.676770 2017] [wsgi:error] [pid 23173:tid 
139844567475968]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/tables/base.py",
 line 1500, in render_row_actions
  [Fri Mar 10 09:18:35.676772 2017] [wsgi:error] [pid 23173:tid 
139844567475968] bound_actions = self.get_row_actions(datum)
  [Fri Mar 10 09:18:35.676774 2017] [wsgi:error] [pid 23173:tid 
139844567475968]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../horizon/tables/base.py",
 line 1452, in get_row_actions
  [Fri Mar 10 09:18:35.676777 2017] [wsgi:error] [pid 23173:tid 
139844567475968] bound_action.bound_url = bound_action.get_link_url(datum)
  [Fri Mar 10 09:18:35.676779 2017] [wsgi:error] [pid 23173:tid 
139844567475968]   File 
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/info/tables.py",
 line 188, in get_link_url
  [Fri Mar 10 09:18:35.676781 2017] [wsgi:error] [pid 23173:tid 
139844567475968] args=(obj_id,))
  [Fri Mar 10 09:18:35.676783 2017] [wsgi:error] [pid 23173:tid 
139844567475968]   File 
"/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 571, in 
reverse
  [Fri Mar 10 09:18:35.676785 2017] [wsgi:error] [pid 23173:tid 
139844567475968] (key, ':'.join(resolved_path)))
  [Fri Mar 10 09:18:35.676786 2017] [wsgi:error] [pid 23173:tid 
139844567475968] TemplateSyntaxError: u'routers' is not a registered namespace 
inside 'horizon:admin'

  Also there is no choose in the admin tab: Router. Which seems to be
  missing.

  The installation is Openstack Newton on Ubuntu 16.04 LTS.

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