[Yahoo-eng-team] [Bug 1457556] Re: [RFE] [LBaaS] ssh connection timeout

[Reedip]

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

** Changed in: python-neutronclient
 Assignee: (unassigned) => Reedip (reedip-banerjee)

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

Title:
  [RFE] [LBaaS] ssh connection timeout

Status in neutron:
  In Progress
Status in python-neutronclient:
  New

Bug description:
  In the V2 api, we need a way to tune the lb connection timeouts so
  that we can have a pool of ssh servers that have long running tcp
  connections. ssh sessions can last days to weeks and users get grumpy
  if the session times out if they are in the middle of doing something.
  Currently the timeouts are tuned to drop connections that are too long
  running regardless of if  there is traffic on the connection or not.
  This is good for http, but bad for ssh.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1457556/+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 1539179] [NEW] libvirt: live_snapshot can be enabled when RBD snapshot/clone is performed

[Frode Nordahl]

Public bug reported:

The recently merged functionality for making use of RBD snapshot/clone
when available is very valuable for the Ceph/RBD users out there!
(https://review.openstack.org/#/c/205282/)

However, it is also possible to enable live_snapshots when this feature
is used.

I have a proposed patch that allows to enable this.

** Affects: nova
 Importance: Undecided
 Assignee: Frode Nordahl (fnordahl)
 Status: In Progress

** Description changed:

- The recentlig merged functionality for making use of RBD snapshot/clone
+ The recently merged functionality for making use of RBD snapshot/clone
  when available is very valuable for the Ceph/RBD users out there!
  (https://review.openstack.org/#/c/205282/)
  
  However, it is also possible to enable live_snapshots when this feature
  is used.
  
  I have a proposed patch that allows to enable this.

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

Title:
  libvirt: live_snapshot can be enabled when RBD snapshot/clone is
  performed

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The recently merged functionality for making use of RBD snapshot/clone
  when available is very valuable for the Ceph/RBD users out there!
  (https://review.openstack.org/#/c/205282/)

  However, it is also possible to enable live_snapshots when this
  feature is used.

  I have a proposed patch that allows to enable this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539179/+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 1539140] [NEW] Current logging in Keystone does not enable operators to determine what is happening

[Henry Nash]

Public bug reported:

Our current logging is meant to provide different levels so that
operators can enable a suitable level (e.g. INFO) without going full
DEBUG (which operators consider potentially risky).  INFO doesn't,
however, give you anything consistent.

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  Current logging in Keystone does not enable operators to  determine
  what is happening

Status in OpenStack Identity (keystone):
  New

Bug description:
  Our current logging is meant to provide different levels so that
  operators can enable a suitable level (e.g. INFO) without going full
  DEBUG (which operators consider potentially risky).  INFO doesn't,
  however, give you anything consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1539140/+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 1224273] Re: Need a test to verify token's do not get data creep

[OpenStack Infra]

Reviewed:  https://review.openstack.org/253670
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=fe14d330c7a5528a7a78c0445567845d62d3b2c0
Submitter: Jenkins
Branch:master

commit fe14d330c7a5528a7a78c0445567845d62d3b2c0
Author: Lance Bragstad 
Date:   Mon Dec 7 22:41:57 2015 +

Add checks for project scoped data creep to tests

Previously, the assertValidProjectScopedTokenResponse method only ensured
specific attributes were in the token response. These checks didn't ensure
that the token scope never grew.

This change makes it so that the assertion will fail if extra attributes are
added to the token response. This should help us be more aware of changes 
that
have token response data creep by building the check into the tests.

Change-Id: I4ebb86af973ed6af001373756a69af9586bdefcf
Closes-Bug: 1224273


** Changed in: keystone
   Status: In Progress => Fix Released

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

Title:
  Need a test to verify token's do not get data creep

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Keystone needs a test that can verify that across the many changes we
  do not end up growing our token's data scope without explicit
  knowledge.  The basic reasoning is to ensure that we can keep track of
  all the elements in a given token version and easily see when that has
  changed.

  Currently there are checks to verify some token data is there, but
  there are no checks to verify that tokens don't end up with
  unknown/extra data.   There seems to be a lot of duplicate data in the
  tokens at this point.  This duplication of data should be kept to a
  minimum.

  This will also help us to define the token specification and keep that
  explicit specification up to date.  This specification can be used by
  developers to accurately predict what is guaranteed to be in every
  token and pull the data from the correct location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1224273/+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 1501740] Re: Creating a region without request parameters failed.

[OpenStack Infra]

Reviewed:  https://review.openstack.org/237448
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=ba7973b86992b4f8c9ee69c1d94ca4d9569eab4c
Submitter: Jenkins
Branch:master

commit ba7973b86992b4f8c9ee69c1d94ca4d9569eab4c
Author: Dave Chen 
Date:   Tue Oct 20 15:44:32 2015 +0800

Fix schema validation to use JSONSchema for empty entity

APIs such as region creation allow an empty entity (a random UUID will
be generated as the region in this case).

Keystone uses JSONShema for validation and will allow an empty entity
to be passed if the schema doesn't have `required` properties (as the
region creation schema allows).

The patch fixes the schema validation code to pass even an empty entity
to JSONSchema validation so that an API such as region create can pass
the validation and can be created successfully.

Change-Id: If3dd49af5e16bb3b741efa4573f9f8e9085ddd14
Closes-Bug: #1501740


** Changed in: keystone
   Status: In Progress => Fix Released

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

Title:
  Creating a region without request parameters failed.

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Use Identity API v3 (CURRENT)

  URL: http://developer.openstack.org/api-ref-
  identity-v3.html#createRegion

  Issu: Creating a region failed when optional parameters are not
  specified.

  "POST /v3/regions" has 3 parameters, which are "region", "description" and 
"parent_region_id".
  "description" and "parent_region_id" are optional.
  Although this API with only "region" parameter should succeed, it fails.

  I confirmed this issue by the following command:

  curl -s -X POST -H "X-Auth-Token: $TOKEN" -H "Content-type: application/json" 
http://localhost:5000/v3/regions -d '{ "region": {} }' | python -m json.tool
  {
  "error": {
  "code": 400,
  "message": "Expecting to find region in request body - the server 
could not comply with the request since it is either malformed or otherwise 
incorrect. The client is assumed to be in error.",
  "title": "Bad Request"
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1501740/+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 1535616] Re: XenAPI: Console logging race condition

[OpenStack Infra]

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

commit a40ee2ce1b887751a91cc373cdd6c3415fb3e2d7
Author: Bob Ball 
Date:   Tue Jan 19 10:11:10 2016 +

XenAPI: Fix race on rotate_xen_guest_logs

There is a race between where Xen creates the domain and starts logging
and when XAPI returns to say that the domain has started.

If the cronjob to rotate the guest logs runs in this period, it can
delete the console logs before we set the last_dom_id which is used to
preserve logs.

This change adds a fixed delay before deleting any log files, allowing
the VM start operation to return after the domain has been successfully
created.

Change-Id: I82ae3e008974f33b60256366f171abf1f0369e60
Closes-Bug: 1535616


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

Title:
  XenAPI: Console logging race condition

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Unexpected API Error in XenServer CI
  test_get_console_output_with_unlimited_size

  http://dd6b71949550285df7dc-
  
dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/22/267822/1/2904/index.html
  failed with a race condition getting the guest console logs:

  VM started:
  Jan 14 22:03:58 localhost xapi: [debug|localhost.localdomain|1158 INET 
0.0.0.0:80|VM.start_on R:98346b008094|audit] VM.start_on: VM = 
'9bbcbe52-ca94-37df-2791-e49d8dfae4c7 (instance-0042)'; host 
'd77c538b-afe9-4e0c-b5f1-223fed0f9728 (localhost.localdomain)'

  Cron job kicks in, identifies that domain 88 isn't "valid" and deletes the 
log file
  Jan 14 22:04:01 localhost rotate_xen_guest_logs: Valid dom IDs: 81 87 2 85 86 
83 0 82
  Jan 14 22:04:01 localhost rotate_xen_guest_logs: Deleting: 
/var/log/xen/guest/console.88

  VM start completed (XAPI returns):
  Jan 14 22:04:03 localhost xapi: [debug|localhost.localdomain|1158 INET 
0.0.0.0:80|VM.start_on R:98346b008094|xapi] Message.create VM_STARTED 5 VM 
9bbcbe52-ca94-37df-2791-e49d8dfae4c7

  Attempt to preserve the log file for domain 88 made:
  Jan 14 22:05:01 localhost xapi: [ info|localhost.localdomain|55940 UNIX 
/var/xapi/xapi||cli] xe vm-param-set uuid=9bbcbe52-ca94-37df-2791-e49d8dfae4c7 
other-config:last_dom_id=88 username=root password=(omitted)

  The console log exists _before_ XAPI has completed starting the
  domain, so we can't preserve the log file using the last_dom_id flag.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1535616/+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 1536281] Re: Missing super() call in some of the Model's subclasses

[OpenStack Infra]

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

commit b44955c35429def97627e925da2f4d0568c1ecdd
Author: Gábor Antal 
Date:   Wed Jan 20 18:42:47 2016 +0100

Added super() call in some of the Model's child

In model.py, there some subclasses of Model which are not calling the
parent's super() method in their own __init__() method.

The classes are:

VIF8021QbgParams (line 319)
VIF8021QbhParams (line 329)
NetworkInfoAsyncWrapper (line 489)

Change-Id: I7a85f4963889b997ae47f4efa4e94f5eae6f3fb2
Closes-Bug: #1536281


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

Title:
  Missing super() call in some of the Model's subclasses

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  In model.py, there some subclasses of Model which are not calling the
  parent's super() method in their own __init__() method.

  The classes are:

  VIF8021QbgParams (line 319)
  VIF8021QbhParams (line 329)
  NetworkInfoAsyncWrapper (line 489)

  We need to add super() call to these classes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536281/+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 1533741] Re: nova.rpc module is only indirectly unit tested

[OpenStack Infra]

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

commit 9a46586dcf96db567a999380dcaef02bdfd1592a
Author: Ryan Rossiter 
Date:   Thu Jan 14 00:21:02 2016 +

Add tests for nova.rpc module

This change adds test for the nova.rpc module, including the public
functions and 2 classes within the module.

Change-Id: I368ed5146210948c95de5a647097b98dcf8a3ca6
Closes-bug: #1533741


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

Title:
  nova.rpc module is only indirectly unit tested

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  It seems that there are no unit tests for the nova.rpc module. Because
  nova.rpc is used by many other modules, changes to it do cause UT
  failures. But it is possible to remove essential parts without failing
  any unit tests. An example of this is removing TRANSPORT.cleanup()
  from the cleanup function.

  Tests should be added for all of the public functions, along with
  tests for RequestContextSerializer for both a given base, and a null
  base.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533741/+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 1538952] Re: Creat a port with ip address which is not the address pool in subnet

[Cedric Brandily]

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

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

Title:
   Creat a port with ip address which is not the  address pool in subnet

Status in neutron:
  Opinion

Bug description:
  version: 2015.1.2

  step:
  * create a port by the restapi
  *  {
"port": {
  ..
  "fixed_ip": [
{
 "subnet_id": "***"
 "ip_address": "***"
 }
  ]
}
 
  *  create port is successful although the ip_address is not in the allocation 
pool

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538952/+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 1539226] [NEW] Stable branch version number needs to be updated in stable/kilo

[Shweta P]

Public bug reported:

Jenkins fails after complaining about the version number

2016-01-27 23:16:47.695 | You are using pip version 7.1.0, however version 
8.0.2 is available.
2016-01-27 23:16:47.695 | You should consider upgrading via the 'pip install 
--upgrade pip' command.
2016-01-27 23:16:47.946 | Collecting pbr
2016-01-27 23:16:48.051 |   Downloading 
http://pypi.IAD.openstack.org/packages/py2.py3/p/pbr/pbr-1.8.1-py2.py3-none-any.whl
 (89kB)
2016-01-27 23:16:48.085 | Installing collected packages: pbr
2016-01-27 23:16:48.158 | Successfully installed pbr-1.8.1
2016-01-27 23:16:48.179 | + sdist_check/bin/python setup.py sdist
2016-01-27 23:16:48.802 | ERROR:root:Error parsing
2016-01-27 23:16:48.802 | Traceback (most recent call last):
2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/core.py",
 line 109, in pbr
2016-01-27 23:16:48.802 | attrs = util.cfg_to_args(path)
2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/util.py",
 line 243, in cfg_to_args
2016-01-27 23:16:48.802 | pbr.hooks.setup_hook(config)
2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/hooks/__init__.py",
 line 25, in setup_hook
2016-01-27 23:16:48.802 | metadata_config.run()
2016-01-27 23:16:48.803 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/hooks/base.py",
 line 27, in run
2016-01-27 23:16:48.803 | self.hook()
2016-01-27 23:16:48.803 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/hooks/metadata.py",
 line 26, in hook
2016-01-27 23:16:48.803 | self.config['name'], self.config.get('version', 
None))
2016-01-27 23:16:48.803 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/packaging.py",
 line 659, in get_version
2016-01-27 23:16:48.803 | version = _get_version_from_git(pre_version)
2016-01-27 23:16:48.803 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/packaging.py",
 line 601, in _get_version_from_git
2016-01-27 23:16:48.803 | result = _get_version_from_git_target(git_dir, 
target_version)
2016-01-27 23:16:48.803 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/packaging.py",
 line 563, in _get_version_from_git_target
2016-01-27 23:16:48.803 | dict(new=new_version, target=target_version))
2016-01-27 23:16:48.803 | ValueError: git history requires a target version of 
pbr.version.SemanticVersion(2015.1.4), but target version is 
pbr.version.SemanticVersion(2015.1.3)
2016-01-27 23:16:48.804 | error in setup command: Error parsing 
/home/jenkins/workspace/gate-neutron-pep8/setup.cfg: ValueError: git history 
requires a target version of pbr.version.SemanticVersion(2015.1.4), but target 
version is pbr.version.SemanticVersion(2015.1.3)

** Affects: neutron
 Importance: Undecided
 Assignee: Shweta P (shweta-ap05)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => Shweta P (shweta-ap05)

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

Title:
  Stable branch version number needs to be updated in stable/kilo

Status in neutron:
  New

Bug description:
  Jenkins fails after complaining about the version number

  2016-01-27 23:16:47.695 | You are using pip version 7.1.0, however version 
8.0.2 is available.
  2016-01-27 23:16:47.695 | You should consider upgrading via the 'pip install 
--upgrade pip' command.
  2016-01-27 23:16:47.946 | Collecting pbr
  2016-01-27 23:16:48.051 |   Downloading 
http://pypi.IAD.openstack.org/packages/py2.py3/p/pbr/pbr-1.8.1-py2.py3-none-any.whl
 (89kB)
  2016-01-27 23:16:48.085 | Installing collected packages: pbr
  2016-01-27 23:16:48.158 | Successfully installed pbr-1.8.1
  2016-01-27 23:16:48.179 | + sdist_check/bin/python setup.py sdist
  2016-01-27 23:16:48.802 | ERROR:root:Error parsing
  2016-01-27 23:16:48.802 | Traceback (most recent call last):
  2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/core.py",
 line 109, in pbr
  2016-01-27 23:16:48.802 | attrs = util.cfg_to_args(path)
  2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/util.py",
 line 243, in cfg_to_args
  2016-01-27 23:16:48.802 | pbr.hooks.setup_hook(config)
  2016-01-27 23:16:48.802 |   File 
"/home/jenkins/workspace/gate-neutron-pep8/sdist_check/local/lib/python2.7/site-packages/pbr/hooks/__init__.py",
 line 25, in setup_hook
  2016-01-27 23:16:48.802 | metadata_config.run()
  2016-01-27 

[Yahoo-eng-team] [Bug 1229093] Re: the domain name is case insensitive with keystone v3

[OpenStack Infra]

Reviewed:  https://review.openstack.org/236103
Committed: 
https://git.openstack.org/cgit/openstack/keystone/commit/?id=33860b31fcbf7dc8a6ffdcbc1c0e131e652cdcff
Submitter: Jenkins
Branch:master

commit 33860b31fcbf7dc8a6ffdcbc1c0e131e652cdcff
Author: henriquetruta 
Date:   Fri Oct 16 18:02:10 2015 -0300

Improves domain name case sensitivity tests

The old domain name case sensitivity test only tested if we were able to
create a domain, but did not test the get_domain_by_name resource_api
call case sensitivity

Change-Id: I2df8611d4e4f983ad91b32c41168ffe2e082e532
Closes-Bug: 1229093


** Changed in: keystone
   Status: In Progress => Fix Released

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

Title:
  the domain name is case insensitive with keystone v3

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  
  I found the domain name is case insensitive when i use keystone 
/v3/auth/tokens which means 

  i can use the "default", "deFault" as domain name to get the valid
  token.

  When i checked the code , i found the keystone uses database query to
  get the domain by name  ,  if my database

  is mysql with default configuration then it is case insensitive, but
  the postgres is case sensitive by default.

  This is not a consistent API behavior. I would like to get the same
  output no matter what kind of db in backend.

  I  propose to use case sensitive due to security reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1229093/+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 1537617] Re: caching of the catalog does not invalidate across processes

[Steve Martinelli]

fixed by https://review.openstack.org/#/c/215715/

** Changed in: keystone
Milestone: None => mitaka-3

** Tags removed: liberty-backport-potential

** Changed in: keystone
   Status: In Progress => Fix Released

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

Title:
  caching of the catalog does not invalidate across processes

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  Due to the way dogpile.cache works, the region-wide invalidation used
  in the catalog caching backend is broken, since this will only
  invalidate the local in-memory region and is not shared across
  backends.

  This will produce odd effects when adding/removing endpoints if caching is 
enabled such as the endpoints needing to wait a significant period of time
  for the cache to expire on some workers while others will see the change 
immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1537617/+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 1539271] [NEW] Libvirt live migration stalls

[Dan Smith]

Public bug reported:

The following message in nova gate test logs shows that libvirt live
migration can stall on some sort of deadlock:

2016-01-28 16:53:20.878 INFO nova.virt.libvirt.driver [req-692a1f4f-
16aa-4d93-a694-1f7eef4df9f6 tempest-
LiveBlockMigrationTestJSON-1471114638 tempest-
LiveBlockMigrationTestJSON-1937054400] [instance:
7b1bc0e2-a6a9-4d85-a3f9-4568d52d1f1b] Migration running for 30 secs,
memory 100% remaining; (bytes processed=0, remaining=0, total=0)

Additionally, the libvirt logger thread seems to be deadlocked before
this happens.

** Affects: nova
 Importance: Undecided
 Status: New

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

Title:
  Libvirt live migration stalls

Status in OpenStack Compute (nova):
  New

Bug description:
  The following message in nova gate test logs shows that libvirt live
  migration can stall on some sort of deadlock:

  2016-01-28 16:53:20.878 INFO nova.virt.libvirt.driver [req-692a1f4f-
  16aa-4d93-a694-1f7eef4df9f6 tempest-
  LiveBlockMigrationTestJSON-1471114638 tempest-
  LiveBlockMigrationTestJSON-1937054400] [instance:
  7b1bc0e2-a6a9-4d85-a3f9-4568d52d1f1b] Migration running for 30 secs,
  memory 100% remaining; (bytes processed=0, remaining=0, total=0)

  Additionally, the libvirt logger thread seems to be deadlocked before
  this happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539271/+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 1294735] Re: Disable domain doesn't disable users in the domain

[Clenimar Filemon]

I couldn't reproduce Shota's procedure... the token revocation seems
pretty right from here. As Dolph noted in comment #4, the Disabled
attribute should not cascade, but its effect. In fact, users in a
disabled domain are blocked to get a token in token issuance time
(thanks Samuel for clarification!).

So I'm marking this as Invalid.

The token revocation can be treated in another topic.

** Changed in: keystone
   Status: Triaged => 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/1294735

Title:
  Disable domain doesn't disable users in the domain

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  If you disable a domain, the users in the domain are not disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1294735/+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 1539240] [NEW] create trust tests that exercise implied roles

[Steve Martinelli]

Public bug reported:

a trust can be created that delegates an implied role, but there is no
test for this.

create a bug so we don't forget

** Affects: keystone
 Importance: Low
 Status: New

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

Title:
  create trust tests that exercise implied roles

Status in OpenStack Identity (keystone):
  New

Bug description:
  a trust can be created that delegates an implied role, but there is no
  test for this.

  create a bug so we don't forget

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1539240/+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 1539332] [NEW] exception covered in test case: _test_process_routers_update_router_deleted

[yalei wang]

Public bug reported:

Testcase _test_process_routers_update_router_deleted directly tests the
update process.

It lacks of router creating process so remove_router be called but
add_router never be called before. That will trigger a TypeError
exception in remove_router callback function as it would get a router
NONE.

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  exception covered in test case:
  _test_process_routers_update_router_deleted

Status in neutron:
  New

Bug description:
  Testcase _test_process_routers_update_router_deleted directly tests
  the update process.

  It lacks of router creating process so remove_router be called but
  add_router never be called before. That will trigger a TypeError
  exception in remove_router callback function as it would get a router
  NONE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1539332/+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 1539333] [NEW] exception covered in test case: _test_process_routers_update_router_deleted

[yalei wang]

Public bug reported:

Testcase _test_process_routers_update_router_deleted directly tests the
update process.

It lacks of router creating process so remove_router be called but
add_router never be called before. That will trigger a TypeError
exception in remove_router callback function as it would get a router
NONE.

** Affects: neutron
 Importance: Undecided
 Assignee: yalei wang (yalei-wang)
 Status: New

** Changed in: neutron
 Assignee: (unassigned) => yalei wang (yalei-wang)

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

Title:
  exception covered in test case:
  _test_process_routers_update_router_deleted

Status in neutron:
  New

Bug description:
  Testcase _test_process_routers_update_router_deleted directly tests
  the update process.

  It lacks of router creating process so remove_router be called but
  add_router never be called before. That will trigger a TypeError
  exception in remove_router callback function as it would get a router
  NONE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1539333/+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 1534198] Re: neutron-lbaas minimal gate jobs should not build amphora image

[OpenStack Infra]

Reviewed:  https://review.openstack.org/267798
Committed: 
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=bb8e384ff1cc9a160bd2cc26232c61b477dda200
Submitter: Jenkins
Branch:master

commit bb8e384ff1cc9a160bd2cc26232c61b477dda200
Author: Michael Johnson 
Date:   Thu Jan 14 20:11:59 2016 +

Don't always run Octavia amphroa image build

Currently we are building the amphroa image for all gate jobs.
We need to limit this so we do not build the image for minimal
API tests.
This also disables un-needed services for all tests.

Change-Id: I4742d9cf38c7010e309cb1e56b07524217d2eac8
Closes-bug: #1534198


** Changed in: neutron
   Status: In Progress => Fix Released

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

Title:
  neutron-lbaas minimal gate jobs should not build amphora image

Status in neutron:
  Fix Released

Bug description:
  The neutron-lbaas minimal gate jobs are building the amphora image
  using diskimage- builder.  It should not be building the image for
  these checks as they are API tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1534198/+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 1539071] [NEW] tox -e docs fails due to faulty api sample

[Balazs Gibizer]

Public bug reported:

tox -e docs fails on master (df8216b2bcf3657b1c89797d4e3ecc456cf27054)
with

python -m json.tool doc/api_samples/servers/v2.19/server-put-req.json 
Expecting property name: line 5 column 5 (char 117)
ERROR: InvocationError: '/bin/bash -c ! find doc/ -type f -name *.json | xargs 
-t -n1 python -m json.tool 2>&1 > /dev/null | grep -B1 -v ^python'
_
 summary 
__
ERROR:   docs: commands failed

It seem that doc/api_samples/servers/v2.19/server-put-req.json is not a
valid json file.

** Affects: nova
 Importance: Undecided
 Assignee: Balazs Gibizer (balazs-gibizer)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

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

Title:
  tox -e docs fails due to faulty api sample

Status in OpenStack Compute (nova):
  New

Bug description:
  tox -e docs fails on master (df8216b2bcf3657b1c89797d4e3ecc456cf27054)
  with

  python -m json.tool doc/api_samples/servers/v2.19/server-put-req.json 
  Expecting property name: line 5 column 5 (char 117)
  ERROR: InvocationError: '/bin/bash -c ! find doc/ -type f -name *.json | 
xargs -t -n1 python -m json.tool 2>&1 > /dev/null | grep -B1 -v ^python'
  
_
 summary 
__
  ERROR:   docs: commands failed

  It seem that doc/api_samples/servers/v2.19/server-put-req.json is not
  a valid json file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539071/+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 1537721] Re: Image corrupts when upload

[Flavio Percoco]

** Also affects: glance/liberty
   Importance: Undecided
   Status: New

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

** Changed in: glance/liberty
   Importance: Undecided => High

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

Title:
  Image corrupts when upload

Status in Glance:
  In Progress
Status in Glance liberty series:
  New

Bug description:
  After this commit 
https://github.com/openstack/glance_store/commit/a0572ef672512a8ed7ef203816ec256eafd5f9de
  image uploads works incorrect.

  Steps to reproduce:

  1. Upload image (1.47GB)
  md5sum virtual_ubuntu_trasty_ext4_demo 
  fa9ec35d64d43aefd6356150d361ec24  virtual_ubuntu_trasty_ext4_demo

  glance image-create --disk-format raw --container-format bare --file 
virtual_ubuntu_trasty_ext4_demo --progress --name ubuntu_upload_with_fix 
  [=>] 100%
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | fa9ec35d64d43aefd6356150d361ec24 |
  | container_format | bare |
  | created_at   | 2016-01-25T11:06:15Z |
  | disk_format  | raw  |
  | id   | 5b955bce-61ab-4c55-afd9-8bd6012cf1ab |
  | min_disk | 0|
  | min_ram  | 0|
  | name | ubuntu_upload_with_fix   |
  | owner| e885a6c5e87c45d38a274de4388241e6 |
  | protected| False|
  | size | 1476395008   |
  | status   | active   |
  | tags | []   |
  | updated_at   | 2016-01-25T11:10:49Z |
  | virtual_size | None |
  | visibility   | private  |
  +--+--+

  2. It has 10 obects in Swift, but should has only one (size is less than 5G)
  swift list glance
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-1
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-2
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-3
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-4
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-5
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-6
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
  5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9

  Image splitted by 7 chunks of 200MB + 1*47MB + 1 zero length chunk.
  swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
 Account: v1
   Container: glance
  Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7
Content Type: binary/octet-stream
  Content Length: 20480
   Last Modified: Mon, 25 Jan 2016 11:10:42 GMT
ETag: eda9a9889837ac4bc81d6387d92c1bec
   Accept-Ranges: bytes
  Server: Apache
 X-Timestamp: 1453720242.0
  X-Trans-Id: txda5cc-0056a6064c-5e81-default
  swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
 Account: v1
   Container: glance
  Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8
Content Type: binary/octet-stream
  Content Length: 42795008
   Last Modified: Mon, 25 Jan 2016 11:10:49 GMT
ETag: f3c9b36eceea8d2192996ca931f1fa55
   Accept-Ranges: bytes
  Server: Apache
 X-Timestamp: 1453720249.0
  X-Trans-Id: txd8c0e-0056a60655-377d-default
  swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9
 Account: v1
   Container: glance
  Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9
Content Type: binary/octet-stream
  Content Length: 0
   Last Modified: Mon, 25 Jan 2016 11:10:49 GMT
ETag: d41d8cd98f00b204e9800998ecf8427e
   Accept-Ranges: bytes
  Server: Apache
 X-Timestamp: 1453720249.0
  X-Trans-Id: txda39b-0056a60660-85c1-default

  3. Download image 
  glance image-download 5b955bce-61ab-4c55-afd9-8bd6012cf1ab --file 
ubuntu_download_with_fix --progress
  [=>] 100%[Errno 32] Corrupt image download. 
Checksum was 9253e738cabf6a3c0beace1a3b07e623 expected 
fa9ec35d64d43aefd6356150d361ec24

  Image is corrupted, and original and result files has difference in lenght 
(1754 bytes)
  ls -l virtual_ubuntu_trasty_ext4_demo 
  -rw-r--r-- 1 root root 1476395008 Jan 25 11:04 virtual_ubuntu_trasty_ext4_demo
  ls -l ubuntu_download_with_fix 
  -rw-r--r-- 1 root root 1476393254 Jan 25 11:17 ubuntu_download_with_fix

To manage notifications about this bug go to:

[Yahoo-eng-team] [Bug 1539056] [NEW] nova service-list failed when one or some cell-service exception of multiple child cells

[jinquanni（ZTE）]

Public bug reported:

1. version
kilo 2015.1.0

2. Relevant log

2016-01-28 20:16:27.232 26909 ERROR nova.cells.messaging 
[req-8daf498b-d2ae-42e6-9089-40046ec550d3 f04e318acd7e4e5093c91e6dc74a28c3 
53adc6d6825b43378d6ab89fc38051da - - -] Error waiting for responses from 
neighbor cells
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging Traceback (most recent 
call last):
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging   File 
"/usr/lib/python2.7/site-packages/nova/cells/messaging.py", line 549, in process
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging 
num_responses=len(next_hops))
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging   File 
"/usr/lib/python2.7/site-packages/nova/cells/messaging.py", line 235, in 
_wait_for_json_responses
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging raise 
exception.CellTimeout()
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging CellTimeout: Timeout 
waiting for response from cell
2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging 

3. Reproduce steps:

3.1 environment described

I have a api cell node：api-cell,
two child cell node： child-cell-01 child-cell-02，
and each child_cell have one compute node

3.2 
excuate “systemctl stop openstack-nova-cells.service” on  child-cell-01

openstack-nova-cells.service - OpenStack Nova Cells Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-cells.service; 
enabled)
   Active: inactive (dead) since Thu 2016-01-28 19:54:50 CST; 24min ago
  Process: 2566 ExecStart=/usr/bin/nova-cells (code=exited, status=0/SUCCESS)
 Main PID: 2566 (code=exited, status=0/SUCCESS)
 

3.3 excuate “nova service-list” on api-cell
Expected result: list all service and status（Tolerance does not contain service 
on child-cell-01 and it‘s compute node）
Actual result ： ERROR, log reference section 2


4
Only one or some cell’s service exception of many child cell lead to nova 
service-list failed isunreasonable

** Affects: nova
 Importance: Undecided
 Assignee: jinquanni（ZTE） (ni-jinquan)
 Status: New


** Tags: cells

** Changed in: nova
 Assignee: (unassigned) => jinquanni（ZTE） (ni-jinquan)

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

Title:
  nova service-list failed when one or some cell-service exception  of
  multiple child cells

Status in OpenStack Compute (nova):
  New

Bug description:
  1. version
  kilo 2015.1.0

  2. Relevant log

  2016-01-28 20:16:27.232 26909 ERROR nova.cells.messaging 
[req-8daf498b-d2ae-42e6-9089-40046ec550d3 f04e318acd7e4e5093c91e6dc74a28c3 
53adc6d6825b43378d6ab89fc38051da - - -] Error waiting for responses from 
neighbor cells
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging Traceback (most 
recent call last):
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging   File 
"/usr/lib/python2.7/site-packages/nova/cells/messaging.py", line 549, in process
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging 
num_responses=len(next_hops))
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging   File 
"/usr/lib/python2.7/site-packages/nova/cells/messaging.py", line 235, in 
_wait_for_json_responses
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging raise 
exception.CellTimeout()
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging CellTimeout: Timeout 
waiting for response from cell
  2016-01-28 20:16:27.232 26909 TRACE nova.cells.messaging 

  3. Reproduce steps:

  3.1 environment described

  I have a api cell node：api-cell,
  two child cell node： child-cell-01 child-cell-02，
  and each child_cell have one compute node

  3.2 
  excuate “systemctl stop openstack-nova-cells.service” on  child-cell-01

  openstack-nova-cells.service - OpenStack Nova Cells Server
 Loaded: loaded (/usr/lib/systemd/system/openstack-nova-cells.service; 
enabled)
 Active: inactive (dead) since Thu 2016-01-28 19:54:50 CST; 24min ago
Process: 2566 ExecStart=/usr/bin/nova-cells (code=exited, status=0/SUCCESS)
   Main PID: 2566 (code=exited, status=0/SUCCESS)
   

  3.3 excuate “nova service-list” on api-cell
  Expected result: list all service and status（Tolerance does not contain 
service on child-cell-01 and it‘s compute node）
  Actual result ： ERROR, log reference section 2

  
  4
  Only one or some cell’s service exception of many child cell lead to nova 
service-list failed isunreasonable

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539056/+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 1528031] Re: 'NetworkNotFound' exception during listing ports

[OpenStack Infra]

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

commit 77de9653fd60a802b11f157972f7b3e81497e8a7
Author: Kevin Benton 
Date:   Wed Jan 27 05:18:13 2016 -0800

Raise RetryRequest on policy parent not found

During a port list operation, a port and its parent network
may be concurrently deleted from the database after they have
been retrieved from the DB but before policy is enforced.
Then when the policy engine tries to do a get_network to check
network ownership for a port on a network that no longer exists,
it will encounter a NetworkNotFound exception from the core plugin.

This exception was being propagated all of the way up to the whole
API operation as a 404, which made no sense in the context of a
port list.

This patch adjusts the logic to catch any NotFound exceptions during
this processing and convert them into a RetryRequest to trigger the
API to restart the operation. At this point the objects will be gone
from the database so the problematic items will not be passed to the
policy engine for enforcement.

Closes-Bug: #1528031
Change-Id: I89d12fe0767e1c7ecb68138b5f6f17aa68a68769


** Changed in: neutron
   Status: In Progress => Fix Released

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

Title:
  'NetworkNotFound' exception during listing ports

Status in neutron:
  Fix Released

Bug description:
  There is a problem - when I run tests in parallel then one/two can fail.
  As I see in logs one thread is deleting network while second thread is
  listing all ports. And second thread get exception 'NetworkNotFound'.

  Part of neutron service logs is:

  2015-12-18 06:29:05.151 INFO neutron.wsgi 
[req-4d303e7d-ae31-47b5-a644-552fceeb03ef user-0a50ad96 project-ce45a55a] 
52.90.96.102 - - [18/Dec/2015 06:29:05] "DELETE 
/v2.0/networks/d2d2481a-4c20-452f-8088-6e6815694ac0.json HTTP/1.1" 204 173 
0.426808
  2015-12-18 06:29:05.173 ERROR neutron.policy 
[req-a406e696-6791-4345-8b04-215ca313ea67 user-0a50ad96 project-ce45a55a] 
Policy check error while calling >!
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy Traceback (most recent 
call last):
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy   File 
"/opt/stack/neutron/neutron/policy.py", line 258, in __call__
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy fields=[parent_field])
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy   File 
"/opt/stack/neutron/neutron/plugins/ml2/plugin.py", line 713, in get_network
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy result = 
super(Ml2Plugin, self).get_network(context, id, None)
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy   File 
"/opt/stack/neutron/neutron/db/db_base_plugin_v2.py", line 385, in get_network
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy network = 
self._get_network(context, id)
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy   File 
"/opt/stack/neutron/neutron/db/db_base_plugin_common.py", line 188, in 
_get_network
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy raise 
n_exc.NetworkNotFound(net_id=id)
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy NetworkNotFound: Network 
d2d2481a-4c20-452f-8088-6e6815694ac0 could not be found.
  2015-12-18 06:29:05.173 22048 ERROR neutron.policy 
  2015-12-18 06:29:05.175 INFO neutron.api.v2.resource 
[req-a406e696-6791-4345-8b04-215ca313ea67 user-0a50ad96 project-ce45a55a] index 
failed (client error): Network d2d2481a-4c20-452f-8088-6e6815694ac0 could not 
be found.
  2015-12-18 06:29:05.175 INFO neutron.wsgi 
[req-a406e696-6791-4345-8b04-215ca313ea67 user-0a50ad96 project-ce45a55a] 
52.90.96.102 - - [18/Dec/2015 06:29:05] "GET 
/v2.0/ports.json?tenant_id=63f912ca152048c6a6b375784d90bd37 HTTP/1.1" 404 359 
0.311871

  
  Answer from Kevin Benton (in mailing list):
  Ah, I believe what is happening is that the network is being deleted after 
the port has been retrieved from the database during the policy check. The 
policy check retrieves the port's network to be able to enforce the 
network_owner lookup: 
https://github.com/openstack/neutron/blob/master/etc/policy.json#L6

  So order of events seems to be:

  port list API call received
  ports retrieved from db
  network delete request is processed
  ports processed by policy engine
  policy engine triggers network lookup and hits 404

  
  This appears to be a legitimate bug. Maybe we need to find a way to cache the 
network at port retrieval time for the policy engine.

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

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

[Yahoo-eng-team] [Bug 1533473] Re: missing mm-ctl rootwrap entry for compute.filters

[OpenStack Infra]

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

commit eee50beaafb47a80033caa3f348b91ecec9fb5ef
Author: YAMAMOTO Takashi 
Date:   Wed Jan 13 13:10:56 2016 +0900

Add mm-ctl to compute.filters

It's used to plug/unplug VIF_TYPE_MIDONET vifs on compute nodes.

Closes-Bug: #1533473
Related-Bug: #1235132
Change-Id: Ic8e8b19ec1083d1c9cdab3d17dcaddbe43bb76b4


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

Title:
  missing mm-ctl rootwrap entry for compute.filters

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  mm-ctl is used to plug VIF_TYPE_MIDONET vifs.
  it needs to be in compute.filters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1533473/+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 1528372] Re: H2 should not be manually overridden

[OpenStack Infra]

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

commit 7c242e18d073c2e5f27dd302335caf1a14328c1a
Author: Diana Whitten 
Date:   Mon Dec 21 15:39:33 2015 -0700

Material Theme: Buttons need border radius

Material buttons actually have a border radius:
http://preview.tinyurl.com/zw5ftjf

Theme Preview Pages should use Font Awesome
H2 should not be manually overridden

Change-Id: I8951e04d463ef897815d8a46ad93e5d2327d4793
Closes-bug: #1528369
Closes-bug: #1528368
Closes-bug: #1528372


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  H2 should not be manually overridden

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  H2 styles are manually set in horizon.scss

  This has adverse side effects to other themes:

  
https://www.dropbox.com/s/q78kq58n4bjeo6p/Screenshot%202015-12-21%2015.36.01.png?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1528372/+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 1528368] Re: Material Theme: Buttons need border radius

[OpenStack Infra]

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

commit 7c242e18d073c2e5f27dd302335caf1a14328c1a
Author: Diana Whitten 
Date:   Mon Dec 21 15:39:33 2015 -0700

Material Theme: Buttons need border radius

Material buttons actually have a border radius:
http://preview.tinyurl.com/zw5ftjf

Theme Preview Pages should use Font Awesome
H2 should not be manually overridden

Change-Id: I8951e04d463ef897815d8a46ad93e5d2327d4793
Closes-bug: #1528369
Closes-bug: #1528368
Closes-bug: #1528372


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  Material Theme: Buttons need border radius

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  All buttons in 'material' need to have 0 border radius:
  
https://www.dropbox.com/s/9z27cjpua72o381/Screenshot%202015-12-21%2015.24.28.png?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1528368/+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 1528369] Re: Theme Preview Pages should use Font Awesome

[OpenStack Infra]

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

commit 7c242e18d073c2e5f27dd302335caf1a14328c1a
Author: Diana Whitten 
Date:   Mon Dec 21 15:39:33 2015 -0700

Material Theme: Buttons need border radius

Material buttons actually have a border radius:
http://preview.tinyurl.com/zw5ftjf

Theme Preview Pages should use Font Awesome
H2 should not be manually overridden

Change-Id: I8951e04d463ef897815d8a46ad93e5d2327d4793
Closes-bug: #1528369
Closes-bug: #1528368
Closes-bug: #1528372


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  Theme Preview Pages should use Font Awesome

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Horizon converted all class='caret' to class='fa fa-caret-down'.  The
  theme preview page should reflect this as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1528369/+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 1539006] [NEW] Unused exception and unnecessary actions in the db

[Darja Shakhray]

Public bug reported:

Do update the image when you delete an image from the database to. Then,
caught exception ImageNotFound and Forbidden. The check of access takes
place at higher layer domain model. This code is obsolete. Extra
updating image  increases the load on the db.

https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L285-L295
https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L278

** Affects: glance
 Importance: Undecided
 Assignee: Darja Shakhray (dshakhray)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Darja Shakhray (dshakhray)

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

Title:
  Unused exception and unnecessary actions in the db

Status in Glance:
  New

Bug description:
  Do update the image when you delete an image from the database to.
  Then, caught exception ImageNotFound and Forbidden. The check of
  access takes place at higher layer domain model. This code is
  obsolete. Extra updating image  increases the load on the db.

  
https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L285-L295
  https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L278

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1539006/+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 1456955] Re: tox -epep8 fails due to tox picking python 3.x

[Alvaro Lopez]

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

** No longer affects: nova (Ubuntu)

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

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

Title:
  tox -epep8 fails due to tox picking python 3.x

Status in Designate:
  Fix Released
Status in OpenStack Compute (nova):
  New

Bug description:
  karlsone@workstation:~/projects/dnsaas/designate$ tox -epep8
  pep8 create: /home/karlsone/projects/dnsaas/designate/.tox/pep8
  pep8 installdeps: 
-r/home/karlsone/projects/dnsaas/designate/requirements.txt, 
-r/home/karlsone/projects/dnsaas/designate/test-requirements.txt
  pep8 develop-inst: /home/karlsone/projects/dnsaas/designate
  pep8 runtests: PYTHONHASHSEED='0'
  pep8 runtests: commands[0] | flake8
  Traceback (most recent call last):
File ".tox/pep8/bin/flake8", line 9, in 
  load_entry_point('flake8==2.1.0', 'console_scripts', 'flake8')()
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/flake8/main.py",
 line 24, in main
  flake8_style = get_style_guide(parse_argv=True, 
config_file=DEFAULT_CONFIG)
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/flake8/engine.py",
 line 79, in get_style_guide
  kwargs['parser'], options_hooks = get_parser()
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/flake8/engine.py",
 line 53, in get_parser
  parser_hook(parser)
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/hacking/core.py",
 line 146, in add_options
  factory = pbr.util.resolve_name(local_check_fact)
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/pbr/util.py",
 line 171, in resolve_name
  ret = __import__('.'.join(module_name), fromlist=[attr_name])
File "/home/karlsone/projects/dnsaas/designate/designate/__init__.py", line 
16, in 
  import eventlet
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/__init__.py",
 line 10, in 
  from eventlet import convenience
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/convenience.py",
 line 6, in 
  from eventlet.green import socket
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/green/socket.py",
 line 17, in 
  from eventlet.support import greendns
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/support/greendns.py",
 line 54, in 
  socket=_socket_nodns)
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/patcher.py",
 line 119, in import_patched
  *additional_modules + tuple(kw_additional_modules.items()))
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/eventlet/patcher.py",
 line 93, in inject
  module = __import__(module_name, {}, {}, module_name.split('.')[:-1])
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/dns/resolver.py",
 line 32, in 
  import dns.flags
File 
"/home/karlsone/projects/dnsaas/designate/.tox/pep8/lib/python3.4/site-packages/dns/flags.py",
 line 51, in 
  _by_value = dict([(y, x) for x, y in _by_text.iteritems()])
  AttributeError: 'dict' object has no attribute 'iteritems'
  ERROR: InvocationError: 
'/home/karlsone/projects/dnsaas/designate/.tox/pep8/bin/flake8'
  

 summary 
_
  ERROR:   pep8: commands failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/designate/+bug/1456955/+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 1535918] Re: instance.host not updated on evacuation

[Drew Thorstensen]

The issue with the PowerVM driver is actually in neutron.  I set up a
libvirt environment, and the difference is that the PowerVM VIF is for
some reason in a BUILD state, where as it is ACTIVE in libvirt.

If the PowerVM VIF was in an ACTIVE state, this wouldn't occur, and no
neutron events would need to be waited for.

I'll investigate what's going on with the port state for networking-
powervm.  The state up is being sent...so this requires some
verification.


It is true that the nova instance.host isn't updated until after the spawn in 
nova.  That could be investigated...but this is the root reason why PowerVM is 
seeing different behavior than Libvirt.

** Project changed: nova => networking-powervm

** Changed in: networking-powervm
 Assignee: Wen Zhi Yu (yuywz) => Drew Thorstensen (thorst)

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

Title:
  instance.host not updated on evacuation

Status in networking-powervm:
  In Progress

Bug description:
  I'm working on the nova-powervm driver for Mitaka and trying to add
  support for evacuation.

  The problem I'm hitting is that instance.host is not updated when the
  compute driver is called to spawn the instance on the destination
  host.  It is still set to the source host.  It's not until after the
  spawn completes that the compute manager updates instance.host to
  reflect the destination host.

  The nova-powervm driver uses instance events callback mechanism during
  plug VIF to determine when Neutron has finished provisioning the
  network.  The instance events code sends the event to instance.host
  and hence is sending the event to the source host (which is down).
  This causes the spawn to fail and also causes weirdness when the
  source host gets the events when it's powered back up.

  To temporarily work around the problem, I hacked in setting
  instance.host = CONF.host; instance.save() in the compute driver but
  that's not a good solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-powervm/+bug/1535918/+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 1536509] Re: boot n-cpu from a clean database lead to pci passthrough stop work

[Yongli He]

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

Title:
  boot n-cpu from a clean database lead to pci passthrough stop work

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  first time boot nova or clean the pci devices from nova database then
  reboot n-cpu, will leading to scheduling the VM with pci devices fail.
  if then reboot the n-cpu, everything is ok.

  this bug now block the third-party pci-test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1536509/+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 1539029] [NEW] rollback_live_migration_at_destination fails in libvirt - expects migrate_data object, gets dictionary

[Drew Thorstensen]

Public bug reported:

The rollback_live_migration_at_destination in the libvirt nova driver is
currently expecting the migrate_data as an object.  The object model for
the migrate data was introduced here:

https://github.com/openstack/nova/commit/69e01758076d0e89eddfe6945c8c7e423c862a49

Subsequently, a change set was added to provide transitional support for
the migrate_data object.  This currently forces all of the migrate_data
objects that are sent to the manager to be converted to dictionaries:

https://github.com/openstack/nova/commit/038dfd672f5b2be5ebe30d85bd00d09bae2993fc


It looks like the rollback_live_migration_at_destination method still expects 
the migrate_data in object form.  However the manager passes it down as a 
dictionary.  Which results in this error message upon a rollback:

  File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 
204, in __exit__
six.reraise(self.type_, self.value, self.tb)
  File "/opt/stack/nova/nova/compute/manager.py", line 373, in 
decorated_function
return function(self, context, *args, **kwargs)
  File "/opt/stack/nova/nova/compute/manager.py", line 5554, in 
rollback_live_migration_at_destination
destroy_disks=destroy_disks, migrate_data=migrate_data)
  File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 6391, in 
rollback_live_migration_at_destination
is_shared_instance_path = migrate_data.is_shared_instance_path
  AttributeError: 'dict' object has no attribute 'is_shared_instance_path'

** Affects: nova
 Importance: Undecided
 Assignee: Drew Thorstensen (thorst)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Drew Thorstensen (thorst)

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

Title:
  rollback_live_migration_at_destination fails in libvirt - expects
  migrate_data object, gets dictionary

Status in OpenStack Compute (nova):
  New

Bug description:
  The rollback_live_migration_at_destination in the libvirt nova driver
  is currently expecting the migrate_data as an object.  The object
  model for the migrate data was introduced here:

  
https://github.com/openstack/nova/commit/69e01758076d0e89eddfe6945c8c7e423c862a49

  Subsequently, a change set was added to provide transitional support
  for the migrate_data object.  This currently forces all of the
  migrate_data objects that are sent to the manager to be converted to
  dictionaries:

  
https://github.com/openstack/nova/commit/038dfd672f5b2be5ebe30d85bd00d09bae2993fc

  
  It looks like the rollback_live_migration_at_destination method still expects 
the migrate_data in object form.  However the manager passes it down as a 
dictionary.  Which results in this error message upon a rollback:

File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 
204, in __exit__
  six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/nova/nova/compute/manager.py", line 373, in 
decorated_function
  return function(self, context, *args, **kwargs)
File "/opt/stack/nova/nova/compute/manager.py", line 5554, in 
rollback_live_migration_at_destination
  destroy_disks=destroy_disks, migrate_data=migrate_data)
File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 6391, in 
rollback_live_migration_at_destination
  is_shared_instance_path = migrate_data.is_shared_instance_path
AttributeError: 'dict' object has no attribute 'is_shared_instance_path'

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539029/+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 1538620] Re: Attach with host and instance_uuid not backwards compatible

[OpenStack Infra]

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

commit ed5958d552f6743f4659318a4dac0259868cb552
Author: Ildiko Vancsa 
Date:   Wed Jan 27 15:17:46 2016 +

Revert "Pass host when call attach to Cinder"

Older Cinder blows up because of the extra parameter in the detach call
to Cinder. We need to find another way to pass the info.

This reverts commit d31bb4be8edbce6719258ae1cbbb583a2c3c3a28.

Closes-Bug: #1538620
Change-Id: I99335827ee6492d3f5629850be8e7cbe19371830


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

Title:
  Attach with host and instance_uuid not backwards compatible

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Patch https://review.openstack.org/#/c/266006/ added the ability for
  Cinder to accept both host and instance_uuid when doing an attach.
  This is not backwards compatible to earlier API versions, so when Nova
  calls attach with versions prior to this change with both arguments it
  causes a failure.

  This information is needed for the multiattach work, but we should
  revert that change and try to find a cleaner way to do this that will
  not break backwards compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1538620/+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 1539197] [NEW] Integration tests fail with 'TypeError: string indices must be integers'

[Timur Sufiev]

Public bug reported:

New release of Selenium is under suspicion:
https://github.com/SeleniumHQ/selenium/issues/1497

** Affects: horizon
 Importance: Critical
 Assignee: Timur Sufiev (tsufiev-x)
 Status: New

** Summary changed:

- Integration tests fail with 'TypeError: string indices must be integers
+ Integration tests fail with 'TypeError: string indices must be integers'

** Changed in: horizon
 Assignee: (unassigned) => Timur Sufiev (tsufiev-x)

** Changed in: horizon
   Importance: Undecided => Critical

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

Title:
  Integration tests fail with 'TypeError: string indices must be
  integers'

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  New release of Selenium is under suspicion:
  https://github.com/SeleniumHQ/selenium/issues/1497

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1539197/+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 1537629] Re: No HTTPBadRequest(400) error will be raised from get_console_output.

[OpenStack Infra]

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

commit 56773f04c70760f137b5270d56da927159fde698
Author: Eli Qiao 
Date:   Thu Jan 21 17:19:54 2016 +0800

API: Remove unexpected from errors get_console_output

No HTTPBadRequest(400) error will be raised from get_console_output.

Closes-Bug: #1537629
Change-Id: I5c652697ac0e7ccdb6af33a35074e26fb3f3891f


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

Title:
  No HTTPBadRequest(400) error will be raised from get_console_output.

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  No HTTPBadRequest(400) error will be raised from get_console_output.

  @extensions.expected_errors((400, 404, 409, 501))
  @wsgi.action('os-getConsoleOutput')
  @validation.schema(console_output.get_console_output)
  def get_console_output(self, req, id, body):

  extensions.expected_errors should contain all errors which would be raised 
from the function which is decorated,
  but there is no 400 error come out from the body of get_console_output()

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1537629/+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 1538053] Re: The successful information will disappear automatically but the failure will not

[space]

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

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

Title:
  The successful information will disappear automatically  but the
  failure will not

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
When performing operations,The successful information will disappear
  automatically after several seconds but the failure will not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1538053/+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 1539387] [NEW] l2 agent should subscribe to dvr_update topic only when dvr is enabled

[Sudhakar Gariganti]

Public bug reported:

In OVS Neutron agent, I see that the dvr_update topic is being added to
the consumer list irrespective of DVR being enabled or not. Because of
this, even though I have disabled DVR in my environment, I still see the
agent subscribe and listen on dvr_update topic.

It is expected that the agent subscribes to dvr_update only when dvr is
enabled in the environment.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: l3-dvr-backlog

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

Title:
  l2 agent should subscribe to dvr_update topic only when dvr is enabled

Status in neutron:
  New

Bug description:
  In OVS Neutron agent, I see that the dvr_update topic is being added
  to the consumer list irrespective of DVR being enabled or not. Because
  of this, even though I have disabled DVR in my environment, I still
  see the agent subscribe and listen on dvr_update topic.

  It is expected that the agent subscribes to dvr_update only when dvr
  is enabled in the environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1539387/+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 1328589] Re: Tests fails with non english locale settings

[Launchpad Bug Tracker]

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

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

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

Title:
  Tests fails with non english locale settings

Status in OpenStack Identity (keystone):
  Expired

Bug description:
  When the locale environment setting uses a language other than
  english, some Keystone tests fails.

   $> locale -a
   C
   C.UTF-8
   en_US.utf8
   fr_BE.utf8
   fr_FR
   fr_FR.iso88591
   fr_FR.utf8
   POSIX

   $> LANG=en_US.utf8 ./run_tests.sh
   [ ... ]
   Ran 3283 tests in 158.885s
   OK

   $>LANG=fr_FR.utf8 ./run_tests.sh
   [ ... ]
   Ran 3286 tests in 161.606s
   FAILED (failures=3)

  There are 3 failing tests:
   - keystone.tests.test_backend_ldap.LDAPIdentity.test_wrong_ldap_scope
   - 
keystone.tests.test_backend_ldap.LDAPIdentityEnabledEmulation.test_wrong_ldap_scope
   - keystone.tests.test_wsgi.LocalizedResponseTest.test_get_localized_response

  The two first are in fact only one test (called twice).
  The test compares two string values, but they don't match because one of them 
is translated.

  The last test fails because the message
  exception.NotFound.message_format is translated, in
  
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/tests/test_wsgi.py#n356

  # keystone/tests/test_wsgi.py
  354:class LangTranslator(object):
  355:def ugettext(self, msgid):
   # This condition is broken if 
exception.NotFound.message_format is translated.
  356:if msgid == exception.NotFound.message_format:
  357:return xlated_msg_fmt
  358:return msgid
  359:
  360:gettext = ugettext

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1328589/+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 1539358] [NEW] internal exception when show network topology

[yalei wang]

Public bug reported:

2016-01-29 03:06:46.251227 Internal Server Error: 
/dashboard/project/network_topology/json
2016-01-29 03:06:46.251248 Traceback (most recent call last):
2016-01-29 03:06:46.251253   File 
"/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 
132, in get_response
2016-01-29 03:06:46.251256 response = wrapped_callback(request, 
*callback_args, **callback_kwargs)
2016-01-29 03:06:46.251259   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py", line 
36, in dec
2016-01-29 03:06:46.251262 return view_func(request, *args, **kwargs)
2016-01-29 03:06:46.251265   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py", line 
52, in dec
2016-01-29 03:06:46.251268 return view_func(request, *args, **kwargs)
2016-01-29 03:06:46.251270   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py", line 
36, in dec
2016-01-29 03:06:46.251273 return view_func(request, *args, **kwargs)
2016-01-29 03:06:46.251276   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../horizon/decorators.py", line 
84, in dec
2016-01-29 03:06:46.251278 return view_func(request, *args, **kwargs)
2016-01-29 03:06:46.251281   File 
"/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 71, 
in view
2016-01-29 03:06:46.251283 return self.dispatch(request, *args, **kwargs)
2016-01-29 03:06:46.251286   File 
"/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 89, 
in dispatch
2016-01-29 03:06:46.251288 return handler(request, *args, **kwargs)
2016-01-29 03:06:46.251291   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/network_topology/views.py",
 line 409, in get
2016-01-29 03:06:46.251294 'ports': self._get_ports(request),
2016-01-29 03:06:46.251296   File 
"/opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/network_topology/views.py",
 line 369, in _get_ports
2016-01-29 03:06:46.251528 print self.trans.port[port.status]
2016-01-29 03:06:46.251534 KeyError: u'N/A'
^Chorizon failed to start


the reason is that status of port is N/A, but self.trans.port don't include 
this key.

ubuntu@wyl-neutron-fun2:/opt/stack/networking-odl$ neutron port-show 
c3114c65-c5da-4f89-a311-31add977cce1
+---+---+
| Field | Value 
|
+---+---+
| admin_state_up| True  
|
| allowed_address_pairs |   
|
| binding:host_id   |   
|
| binding:profile   | {}
|
| binding:vif_details   | {}
|
| binding:vif_type  | unbound   
|
| binding:vnic_type | normal
|
| device_id | 0550f6e2-763b-408f-8af9-0609c6320642  
|
| device_owner  | network:floatingip
|
| dns_assignment| {"hostname": "host-172-24-4-5", "ip_address": 
"172.24.4.5", "fqdn": "host-172-24-4-5.openstacklocal."}|
|   | {"hostname": "host-2001-db8--6", "ip_address": 
"2001:db8::6", "fqdn": "host-2001-db8--6.openstacklocal."} |
| dns_name  |   
|
| extra_dhcp_opts   |   
|
| fixed_ips | {"subnet_id": "bac86baa-388d-445d-8d59-3cf7407affee", 
"ip_address": "172.24.4.5"} |
|   | {"subnet_id": "58e9aedf-495e-45a2-8099-a1f535abfe3b", 
"ip_address": "2001:db8::6"}|
| id| c3114c65-c5da-4f89-a311-31add977cce1  
|
| mac_address   | fa:16:3e:e4:ae:bc  

[Yahoo-eng-team] [Bug 1539342] [NEW] AttributeError raised during roll_back_live_migration_at_destination

[Zhenyu Zheng]

Public bug reported:

In roll_back_live_migration_at_destination, we treat migrate_data as a 
LiveMigrateData object, but it can also be a dict:
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5176-L5198
We have logic here :
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5484-L5491
but we directly pass it down to driver here:
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5512-L5514
and it has not been handled in libvirt driver:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6406-L6412

This will cause AttributeError.

** Affects: nova
 Importance: Undecided
 Assignee: Zhenyu Zheng (zhengzhenyu)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)

** Description changed:

- In roll_back_live_migration_at_destination, we treat migrate_data as a 
LiveMigrateData object, but it is actually a dict:
+ In roll_back_live_migration_at_destination, we treat migrate_data as a 
LiveMigrateData object, but it can also be a dict:
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5176-L5198
  We have logic here :
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5484-L5491
  but we directly pass it down to driver here:
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5512-L5514
  and it has not been handled in libvirt driver:
  
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6406-L6412
  
  This will cause AttributeError.

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

Title:
  AttributeError raised during roll_back_live_migration_at_destination

Status in OpenStack Compute (nova):
  New

Bug description:
  In roll_back_live_migration_at_destination, we treat migrate_data as a 
LiveMigrateData object, but it can also be a dict:
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5176-L5198
  We have logic here :
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5484-L5491
  but we directly pass it down to driver here:
  
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L5512-L5514
  and it has not been handled in libvirt driver:
  
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L6406-L6412

  This will cause AttributeError.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539342/+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 1539351] [NEW] Authorization by user_id does not work in V2.1 API

[Takashi NATSUME]

Public bug reported:

In case that authorization for deleting a VM instance is done by user_id,
it works fine in V2.0 API, but it does not work in V2.1 API.

[How to reproduce]
In nova policy.json,
Add the following entries(or modify existing entries like the following).

---
"user":  "user_id:%(user_id)s",
"compute:delete": "rule:user",
"os_compute_api:servers:delete": "rule:user",
---

In nova api-paste.ini,
change 'openstack_compute_api_v21_legacy_v2_compatible' to
'openstack_compute_api_legacy_v2' for "/v2" endpoint.

---
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v2: openstack_compute_api_legacy_v2
/v2.1: openstack_compute_api_v21
---

In V2.0 API, the authorization by 'user_id' works fine.
Only the user who created a VM instance can delete the VM instance.

In V2.1 API, the authorization by 'user_id' does not work.
Any users in the same project can delete the VM instance that another user 
created.

stack@devstack-master:/opt/devstack$ openstack user list
+--+--+
| ID   | Name |
+--+--+
| 1cd4d65d4f534cd89299bbf31edb37a4 | admin|
| 218e7be255be4c90bf0c4d796a9d509c | nova |
| 357fc80d750646f7b3b56fc1e679 | demo |
| 37c5204df2d345fb8a76359966dc8d1b | heat |
| 4a6e928a20a743a6a3d80944c607a22a | neutron  |
| 8c613c4691e2447e8082f6c425cd34af | glance   |
| 9ab80146bc964e81bfcf3331f6b8bb2d | alt_demo |
| ecd940201f5c45a8833bb739149a54f0 | cinder   |
+--+--+
stack@devstack-master:/opt/devstack$ openstack project list
+--++
| ID   | Name   |
+--++
| 4b7c129ea5ee49d1a620c26272091ec7 | admin  |
| 4c3e76d51a3c4df384c74b8cafb3a9cc | invisible_to_admin |
| 533daaf421554a84aa3b023b4a9c341c | demo   |
| b04c7788628849a48b831f5ad57e374a | service|
+--++
stack@devstack-master:/opt/devstack$ openstack catalog show compute
+---++
| Field | Value 
 |
+---++
| endpoints | RegionOne 
 |
|   |   publicURL: 
http://10.0.2.15:8774/v2.1/533daaf421554a84aa3b023b4a9c341c   |
|   |   internalURL: 
http://10.0.2.15:8774/v2.1/533daaf421554a84aa3b023b4a9c341c |
|   |   adminURL: 
http://10.0.2.15:8774/v2.1/533daaf421554a84aa3b023b4a9c341c|
|   |   
 |
| name  | nova  
 |
| type  | compute   
 |
+---++
stack@devstack-master:/opt/devstack$ openstack catalog show compute_legacy
+---+--+
| Field | Value 
   |
+---+--+
| endpoints | RegionOne 
   |
|   |   publicURL: 
http://10.0.2.15:8774/v2/533daaf421554a84aa3b023b4a9c341c   |
|   |   internalURL: 
http://10.0.2.15:8774/v2/533daaf421554a84aa3b023b4a9c341c |
|   |   adminURL: 
http://10.0.2.15:8774/v2/533daaf421554a84aa3b023b4a9c341c|
|   |   
   |
| name  | nova_legacy   
   |
| type  | compute_legacy
   |
+---+--+
stack@devstack-master:/opt/devstack$ nova show server1
+--++
| Property | Value  
|
+--++
| OS-DCF:diskConfig| MANUAL 
|
| OS-EXT-AZ:availability_zone  | nova 

[Yahoo-eng-team] [Bug 1539354] Re: django.conf.urls.patterns is deprecated since django 1.8

[Shu Muto]

** Summary changed:

- django.conf.urls.patterns deprecated since django 1.8
+ django.conf.urls.patterns is deprecated since django 1.8

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

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

Title:
  django.conf.urls.patterns is deprecated since django 1.8

Status in OpenStack Dashboard (Horizon):
  New
Status in Magnum UI:
  New

Bug description:
  We should not use django.conf.urls.patterns method in urls.py.

  https://docs.djangoproject.com/en/1.9/ref/urls/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1539354/+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 1539136] [NEW] AMQP notifications contain an empty message context

[Daryl Mowrer]

Public bug reported:

The Glance notification event messages do not contain useful request
context information. The notifications should contain the request
context so that user and project information can be extracted from them.

For example, in the v2 api, see the glance notifier.py code. It passes
an empty dict for the request context to the oslo_messaging notifier
calls when sending info, warn, and error notifications. The same applies
to the v1 api.

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  AMQP notifications contain an empty message context

Status in Glance:
  New

Bug description:
  The Glance notification event messages do not contain useful request
  context information. The notifications should contain the request
  context so that user and project information can be extracted from
  them.

  For example, in the v2 api, see the glance notifier.py code. It passes
  an empty dict for the request context to the oslo_messaging notifier
  calls when sending info, warn, and error notifications. The same
  applies to the v1 api.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1539136/+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 1511593] Re: Missing documentation for plugins

[OpenStack Infra]

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

commit 15c7b03d06b206d98c8e79a8fa77b183956bc514
Author: Thai Tran 
Date:   Mon Jan 25 12:32:39 2016 -0800

Plugin Docs

Added tutorial folder for future tutorials.
Added tutorial for creating and installing plugins.
Moved dashboard tutorial into tutorial folder.

Change-Id: I17c1ff279b47292d723c100b580667418aa05636
Closes-Bug: #1511593


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  Missing documentation for plugins

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  We have great architecture for plugins, but no documentation on how to
  actually do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511593/+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 1539402] [NEW] Refactoring required in nova/tests/unit/db/test_migrations.py

[Mark]

Public bug reported:

In nova/tests/unit/db/test_migrations.py,

We can use constant for Text, String, Integer, DateTime type constant
like

Text_TYPE = sqlalchemy.types.Text
String_TYPE = sqlalchemy.types.String
Integer_TYPE = sqlalchemy.types.Integer
DateTime_TYPE = sqlalchemy.types.DateTime


Currently it is directly used as 

self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
  sqlalchemy.type.Text)
self.assertIsInstance(key_pairs.c.type.type,
  sqlalchemy.types.String)
self.assertIsInstance(pci_devices.c.numa_node.type,
  sqlalchemy.types.Integer)
self.assertIsInstance(services.c.last_seen_up.type,
  sqlalchemy.types.DateTime)

It should be

self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
  self.Text_TYPE)
 self.assertIsInstance(shadow_pci_devices.c.parent_addr.type,
  self.String_TYPE)
self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
  self.Integer_TYPE)
self.assertIsInstance(shadow_services.c.last_seen_up.type,
  self.DateTime_TYPE)


These changes are suggested in a separate bug 
(https://bugs.launchpad.net/cinder/+bug/1528989) for cinder and I found them in 
Nova too. Updating for a better visibility of the code.

** Affects: nova
 Importance: Undecided
 Assignee: Mark (rocky-asdf)
 Status: New


** Tags: compute nova

** Changed in: nova
 Assignee: (unassigned) => Mark (rocky-asdf)

** Tags added: nova

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

Title:
  Refactoring required in nova/tests/unit/db/test_migrations.py

Status in OpenStack Compute (nova):
  New

Bug description:
  In nova/tests/unit/db/test_migrations.py,

  We can use constant for Text, String, Integer, DateTime type constant
  like

  Text_TYPE = sqlalchemy.types.Text
  String_TYPE = sqlalchemy.types.String
  Integer_TYPE = sqlalchemy.types.Integer
  DateTime_TYPE = sqlalchemy.types.DateTime

  
  Currently it is directly used as 

  self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
sqlalchemy.type.Text)
  self.assertIsInstance(key_pairs.c.type.type,
sqlalchemy.types.String)
  self.assertIsInstance(pci_devices.c.numa_node.type,
sqlalchemy.types.Integer)
  self.assertIsInstance(services.c.last_seen_up.type,
sqlalchemy.types.DateTime)

  It should be

  self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
self.Text_TYPE)
   self.assertIsInstance(shadow_pci_devices.c.parent_addr.type,
self.String_TYPE)
  self.assertIsInstance(shadow_instance_extra.c.vcpu_model.type,
self.Integer_TYPE)
  self.assertIsInstance(shadow_services.c.last_seen_up.type,
self.DateTime_TYPE)

  
  These changes are suggested in a separate bug 
(https://bugs.launchpad.net/cinder/+bug/1528989) for cinder and I found them in 
Nova too. Updating for a better visibility of the code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1539402/+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 1527716] Re: (Import Refactor) Make tasks API admin only

[OpenStack Infra]

Reviewed:  https://review.openstack.org/265448
Committed: 
https://git.openstack.org/cgit/openstack/glance/commit/?id=8f0d6ea9c535f6ab09fc9b2ae84cf0bef2401ee4
Submitter: Jenkins
Branch:master

commit 8f0d6ea9c535f6ab09fc9b2ae84cf0bef2401ee4
Author: Flavio Percoco 
Date:   Fri Jan 8 16:38:49 2016 -0430

Make the task's API admin only by default

One of the goals of this spec is to improve the image import process and
allow for other background operations to be executed when the image data
is added. This supersedes the need of the task endpoint that we'll
slowly deprecate. As part of this spec, we should make it admin only and
warn deployers that this API is going to be deprecated.

MitakaPriority
DocImpact: Tasks API is now admin only. Deployments depending on this
API need to make sure they make it accessible for non-admins.
Closes-bug: #1527716
Partially-blueprint: image-import-refactor
Change-Id: I28cb69ea730ae58b9aed1dd43b68305dbbf132c1


** Changed in: glance
   Status: In Progress => Fix Released

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

Title:
   (Import Refactor) Make tasks API admin only

Status in Glance:
  Fix Released

Bug description:
  This is a sub-task for the image import process work:
  https://review.openstack.org/#/c/232371/

  One of the goals of this spec is to improve the image import process
  and allow for other background operations to be executed when the
  image data is added. This supersedes the need of the task endpoint
  that we'll slowly deprecate. As part of this spec, we should make it
  admin only and warn deployers that this API is going to be deprecated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1527716/+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 1536919] Re: "Name" doesn't be shown when Bay was created without name

[OpenStack Infra]

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

commit 2c932cd97a84f5274de838fbfea9fa3c64dd6af8
Author: shu-mutou 
Date:   Fri Jan 22 17:21:40 2016 +0900

Add filter to replace null to "None"

Already "noValueFilter" is there, that replace null to "-",
but "-" is small for clickable string.
So this patch adds filter to replace null to "None".

ex.) Name: string for link that must be clicked and needs
 enough size to be clicked.

Change-Id: I2068035b173384d645ba44ccd39e6a7329eb496a
Closes-Bug: #1536919


** Changed in: horizon
   Status: In Progress => Fix Released

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

Title:
  "Name" doesn't be shown when Bay was created without name

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Magnum UI:
  In Progress

Bug description:
  When the Bay was created without "name" option,
  Table view doesn't  show "Name", so can not link to detail view.
  Since "Name" must be able to click, it must have enough size to click.

  BayModel and Container have same issue, should be fixed.

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