date:20160212

This is legacy behavior in Nova network, and the kind of issue that
isn't going to be addressed at this point.

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

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

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

Title:
  VM launch fails with Neutron in "admin" tenant if "admin" and "demo"
  tenants have secgroups with a same name "web"

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Dashboard (Horizon) kilo series:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Using Grizzly with Neutron: If there are multiple security groups with
  the same name (in other tenants for example), it is not possible to
  boot an instance with this security group as Horizon will only use the
  name of the security group.

  Example from logs:
  2013-07-21 03:39:12.432 ERROR nova.network.security_group.quantum_driver 
[req-aaca5681-72b8-41dc-a89c-9a5c95c7eff4 33fe423e114c4586a573514b3e98341e 
e91fe07ea4834f8487c5cec7deaa2eac] Quantum Error: Multiple security_group 
matches found for name 'web', use an ID to be more specific.
  2013-07-21 03:39:12.439 ERROR nova.api.openstack 
[req-aaca5681-72b8-41dc-a89c-9a5c95c7eff4 33fe423e114c4586a573514b3e98341e 
e91fe07ea4834f8487c5cec7deaa2eac] Caught error: Multiple security_group matches 
found for name 'web', use an ID to be more specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1203413/+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 1527925] Re: glanceclient.exc.HTTPInternalServerError when running nova image-list

I believe that this is the issue with Glance incompatibilities with v1
vs. v2 images. If you create an image with v2 via the glance API, glance
explodes when you probe for that image over the v1 API because of
property incompatibilities. Pushing back as a glance issue for now for
that team to look into it.

** Tags removed: api

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

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

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

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

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

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

Title:
  glanceclient.exc.HTTPInternalServerError when running nova image-list

Status in Glance:
  Confirmed
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I am following this guide verbatim: http://docs.openstack.org/liberty
  /install-guide-rdo/nova-verify.html (on CentOS 7.1).

  When I run `nova image-list` I get the following output:

  ERROR (ClientException): Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
req-d4a1d4b7-3bfd-46b5-bda7-37631106b839)

  All other commands so far has worked fine. I can see services in nova
  and upload images in glance.

  Logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1527925/+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 1491022] Re: Glance client proxy doens't respect the osapi_max_limit configuration paramater

As explained above, this would change the behavior of the API for
portions that we are trying to deprecate out. People wanting a paginated
API should go directly to Glance.

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

** Changed in: nova
   Importance: Medium => Low

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

Title:
  Glance client proxy doens't respect the osapi_max_limit configuration
  paramater

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

Bug description:
  With osapi_max_limit set to 1 for example, querying a list of images
  from Nova returns all the available images, ignoring the limit set in
  the configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491022/+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 1535707] Re: Create router with external network attached doesn't create router namespace

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

commit 7334c3cfee12a81657296fa0e90c7d25457de9f6
Author: Masco Kaliyamoorthy 
Date:   Tue Jan 19 18:21:33 2016 +0530

Router namespace not created in controller

When creating a router with an external network attached
from the Create Router form a router namespace doesn't
get created on the controller.

By calling the correct APIs, the namespace get
created.

To check the namespace list run the below command
on controller node.
'sudo ip netns list'

Change-Id: I829c707353830ff808b6f6a0b29ccedeca588616
Closes-Bug: #1535707


** 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 neutron.
https://bugs.launchpad.net/bugs/1535707

Title:
  Create router with external network attached doesn't create router
  namespace

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in neutron:
  Confirmed

Bug description:
  Description of problem:
  In Horizon when creating a router with an external network attached from the 
Create Router form a router namespace doesn't get created on the controller.

  Steps to Reproduce:
  1. Go to Project-> Network -> Routers
  2. Click Create Router
  3. Input name, Admin state UP and select an External Network from the list 

  Actual results:
  Router gets created but no router namespace gets created on the controller. 

  Expected results:
  Router namespace gets created on the controller with an IP assigned from the 
selected external network.

  Additional info:
  If I don't select the external network in the Create Router form when I 
create it and attach it to the external network afterwards by using the set 
gateway button then the router namespace gets created ok.

  to check the router namespace list, run this below command in the controller 
node.
  "sudo ip netns list"

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535707/+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 1544956] [NEW] Missing DocImpact explanation/patch for "libosinfo" change

2016-02-12 Thread Markus Zoeller (markus_z)

Public bug reported:

Commit [1] ("Introducing a new library to retrieve information from
libosinfo database.") declared a DocImpact in its commit message
but doesn't provide information which documents are affected in
which way. Is it:

* a release note for the deployers/ops?
* an information which should be in one of the different manuals we have?
* something for the Nova deloper docs?
* something else?

I'm setting Vladik Romanovsky as bug assignee since he commited this
change.

References
--
[1]
https://git.openstack.org/cgit/openstack/nova/commit/?id=e8c3196b7e4a0dad2674638d212d7eb21d6b94f2

** Affects: nova
Importance: Medium
Assignee: Vladik Romanovsky (vladik-romanovsky)
Status: Confirmed

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

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

** Changed in: nova
Assignee: (unassigned) => Vladik Romanovsky (vladik-romanovsky)

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

Title:
Missing DocImpact explanation/patch for "libosinfo" change

Status in OpenStack Compute (nova):
Confirmed

Bug description:
Commit [1] ("Introducing a new library to retrieve information from
libosinfo database.") declared a DocImpact in its commit message
but doesn't provide information which documents are affected in
which way. Is it:

* a release note for the deployers/ops?
* an information which should be in one of the different manuals we have?
* something for the Nova deloper docs?
* something else?

I'm setting Vladik Romanovsky as bug assignee since he commited this
change.

References
--
[1]
https://git.openstack.org/cgit/openstack/nova/commit/?id=e8c3196b7e4a0dad2674638d212d7eb21d6b94f2

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

I think we have now decided the old behavior was never intended, and
will not be supported in Nova moving forward. Permission restriction
should be by project_id.

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

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

Title:
  Authorization by user_id does not work in V2.1 API

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

Bug description:
  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

[Yahoo-eng-team] [Bug 1538006] Re: useless 'u' in the return info of "openstack aggregate show"

Not a nova bug, this is completely in the display layer for novaclient

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

** Changed in: python-novaclient
   Status: New => Confirmed

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

** Tags removed: api

** Changed in: python-novaclient
   Importance: Undecided => Low

** Changed in: python-novaclient
   Status: Confirmed => Triaged

** Tags added: low-hanging-fruit

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

Title:
  useless 'u' in the return info of "openstack aggregate show"

Status in OpenStack Compute (nova):
  Invalid
Status in python-novaclient:
  Triaged

Bug description:
  [Summary]
  useless 'u' in the return info of "openstack aggregate show"

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless 'u' in the return info of "openstack aggregate show"

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) useless 'u' for metadata when creating an aggregate:
  root@45-59:/opt/stack/devstack# openstack aggregate create 
  --zone bbb --property abc=1  agg3
  +---+--+
  | Field | Value|
  +---+--+
  | availability_zone | bbb  |
  | created_at| 2016-01-26T11:07:16.00   |
  | deleted   | False|
  | deleted_at| None |
  | hosts | []   |
  | id| 3|
  | metadata  | {u'abc': u'1', u'availability_zone': u'bbb'} |  
  | name  | agg3 |
  | updated_at| None |
  +---+--+
  root@45-59:/opt/stack/devstack# 

  2)useless 'u' for properties when show an aggregate:
  root@45-59:/opt/stack/devstack# openstack aggregate show agg3
  +---++
  | Field | Value  |
  +---++
  | availability_zone | bbb|
  | created_at| 2016-01-26T11:07:16.00 |
  | deleted   | False  |
  | deleted_at| None   |
  | hosts | [] |
  | id| 3  |
  | name  | agg3   |
  | properties| {u'abc': u'1'} |
  | updated_at| None   |
  +---++
  root@45-59:/opt/stack/devstack# 

  3)useless 'u' for hosts when add host into an aggregate:
  root@45-59:~# openstack aggregate add host agg3 45-59
  +---+--+
  | Field | Value|
  +---+--+
  | availability_zone | bbb  |
  | created_at| 2016-01-26T11:07:16.00   |
  | deleted   | False|
  | deleted_at| None |
  | hosts | [u'45-59']   |
  | id| 3|
  | metadata  | {u'abc': u'1', u'availability_zone': u'bbb'} |
  | name  | agg3 |
  | updated_at| None |
  +---+--+
  root@45-59:~# 

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538006/+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 1544964] [NEW] [glare] glance-glare fails with default paste config

2016-02-12 Thread Kirill Zaitsev

Public bug reported:

$ tox -e venv -- glance-glare --config-file ./etc/glance-glare.conf

...

2016-02-12 16:02:20.318 16830 ERROR glance.common.config [-] Unable to load 
glare-api from configuration file 
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)
ERROR: Unable to load glare-api from configuration file 
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
Got: ImportError('No module named router',)

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: artifacts

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

Title:
  [glare] glance-glare fails with default paste config

Status in Glance:
  New

Bug description:
  $ tox -e venv -- glance-glare --config-file ./etc/glance-glare.conf

  ...

  2016-02-12 16:02:20.318 16830 ERROR glance.common.config [-] Unable to load 
glare-api from configuration file 
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
  Got: ImportError('No module named router',)
  ERROR: Unable to load glare-api from configuration file 
/Users/teferi/openstack/glance/etc/glance-glare-paste.ini.
  Got: ImportError('No module named router',)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1544964/+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 1545008] [NEW] Unicode symbols in tenant name are displayed incorrectly in RC file download

2016-02-12 Thread Timur Sufiev

Public bug reported:

When you download RC v2/v3 file from Access & Security -> API Access,
tenant_name is being interpolated into 'Content-Disposition: attachment;
filename="%s-openrc.sh"' header. This doesn't work when tenant name
contains non ASCII characters.

** Affects: horizon
 Importance: Undecided
 Assignee: Timur Sufiev (tsufiev-x)
 Status: In Progress

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

Title:
  Unicode symbols in tenant name are displayed incorrectly in RC file
  download

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  When you download RC v2/v3 file from Access & Security -> API Access,
  tenant_name is being interpolated into 'Content-Disposition:
  attachment; filename="%s-openrc.sh"' header. This doesn't work when
  tenant name contains non ASCII characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1545008/+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 1544999] Re: Encountered database ACL.", "error":"referential integrity violation" running OVN stack

2016-02-12 Thread Assaf Muller

** Project changed: neutron => networking-ovn

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

Title:
  Encountered database  ACL.","error":"referential integrity violation"
  running OVN stack

Status in networking-ovn:
  Confirmed

Bug description:
  Scenario tested: A tenant has 2 networks, each with a subnet connected 
through a router. Each tenant gets two VMs each in a network. When these two 
VMs boot up, they send iperf traffic across the router.
  Scale tenants to 500 and measure scaling performance

  Results: Scaled up to 330 vms successfully and failed to boot VMs
  beyond 330VMs.

  The neturon servers including plugin were pegged at 100% and see this 
database integrity violation:
  2016-01-28 04:55:04.723 2757 WARNING requests.packages.urllib3.connectionpool 
[req-7964fc18-a95c-4464-a568-038a453d006e 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
  2016-01-28 04:55:04.772 2757 WARNING requests.packages.urllib3.connectionpool 
[-] Connection pool is full, discarding connection: identity.open.softlayer.com
  2016-01-28 04:55:05.776 2757 WARNING requests.packages.urllib3.connectionpool 
[req-6b80241f-0928-4d93-a80e-988a7b3e9690 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
  2016-01-28 04:55:55.380 2757 ERROR neutron.agent.ovsdb.impl_idl [-] OVSDB 
Error:
  {"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"}

  2016-01-28 04:55:55.443 2757 ERROR neutron.agent.ovsdb.impl_idl 
[req-0bd44851-ecd9-4957-978f-350b52ada25b cc27c50b17fc4954905db5f3f3eed730 
e53d6cd40c5140c58ec014eb56070917 - - -] Traceback (most recent call last):
  File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/native/connection.py",
 line 99, in run
  txn.results.put(txn.do_commit())
  File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_idl.py", 
line 106, in do_commit
  raise RuntimeError(msg)
  RuntimeError: OVSDB Error:
  {"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"} 

  This problem occurs consistently scaling to 500 VMs.

  Also have seen this problem occurring in a 5 node devstack
  installation.  In this case we increased the Neutron api threads to 18
  to recreate this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1544999/+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 1479981] Re: Openstackclient return wrong quota information

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

** This bug is no longer a duplicate of bug 1317515
   flavor-access-add doesn't validate the tenant id
** This bug has been marked a duplicate of bug 1544989
   Nova doesn't validate user/project is valid from keystone during admin 
operations

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

Title:
  Openstackclient return wrong quota information

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

Bug description:
  I try to update the quota port limitations for my project,
  neutronclient works well and I can get the right result using
  neutronclient. But when we run ```openstack  quota show admin``` we
  found the quota port limitation doesn't changed.  Here are the testing
  process:

  
  layton-pistachio:/opt/openstack # neutron --insecure --os-project-id 
d3a77adc69004a6bbfe233cf7f08fdc1 --os-project-domain-name default 
--os-user-domain-name default quota-update --port 160

  +-+---+
  | Field   | Value |
  +-+---+
  | floatingip  | 50|
  | health_monitor  | -1|
  | member  | -1|
  | network | 10|
  | pool| 10|
  | port| 160   |
  | router  | 10|
  | security_group  | 10|
  | security_group_rule | 100   |
  | subnet  | 10|
  | vip | 10|
  +-+---+
  layton-pistachio:/opt/openstack # neutron --insecure --os-project-id 
d3a77adc69004a6bbfe233cf7f08fdc1 --os-project-domain-name default 
--os-user-domain-name default quota-show
  +-+---+
  | Field   | Value |
  +-+---+
  | floatingip  | 50|
  | health_monitor  | -1|
  | member  | -1|
  | network | 10|
  | pool| 10|
  | port| 160   |
  | router  | 10|
  | security_group  | 10|
  | security_group_rule | 100   |
  | subnet  | 10|
  | vip | 10|
  +-+---+
  layton-pistachio:/opt/openstack # openstack quota show admin
  +--+---+
  | Field| Value |
  +--+---+
  | backup_gigabytes | 1000  |
  | backups  | 10|
  | cores| 20|
  | fixed-ips| -1|
  | floating-ips | 50|
  | gigabytes| 1000  |
  | health_monitor   | -1|
  | injected-file-size   | 10240 |
  | injected-files   | 5 |
  | injected-path-size   | 255   |
  | instances| 10|
  | key-pairs| 100   |
  | member   | -1|
  | network  | 10|
  | pool | 10|
  | port | 50|
  | project  | admin |
  | properties   | 128   |
  | ram  | 51200 |
  | router   | 10|
  | secgroup-rules   | 100   |
  | secgroups| 10|
  | server_group_members | 10|
  | server_groups| 10|
  | snapshots| 10|
  | subnet   | 10|
  | vip  | 10|
  | volumes  | 10|
  +--+---+

  layton-pistachio:/opt/openstack # openstack project list
  +--+-+
  | ID   | Name|
  +--+-+
  | 1c30e840b3d1447ea3820d99cc38cd33 | service |
  | 55d10960d5f7447990e69ebf481ac97d | demo|
  | d3a77adc69004a6bbfe233cf7f08fdc1 | admin   |
  +--+-+


  
  I checked the neutron database and the quota information was right:

  
  MariaDB [neutron]> select * from quotas;
  
+--+--+--+---+
  | id   | tenant_id| 
resource | limit |
  
+--+--+--+---+
  | 1c5586f5-7c71-4666-9162-bf29bcaa511d | d3a77adc69004a6bbfe233cf7f08fdc1 | 
port |   160 |
  
+--+--+--+---+
  1 row in set (0.00 sec)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1479981/+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 1544989] [NEW] Nova doesn't validate user/project is valid from keystone during admin operations

Public bug reported:

For any API call to Nova which takes a tenant_id / user_id as a
parameter, and inserts it into the Nova database, no validation is done
of these values.

This is currently by design, largely because there is no clear way to
check the existence of those users/projects. Nova has no generic
credentials to do that to Keystone. It's unclear if there is a way to do
this from a non admin user.

Many other bugs are related to this fundamental issue for which there is
no infrastructure. This includes updating quotas, adding access to
flavors, etc. This will be a placeholder for all those bugs until there
is some way to actually address this at the root.

** Affects: nova
 Importance: Low
 Status: Confirmed


** Tags: api

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

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

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

Title:
  Nova doesn't validate user/project is valid from keystone during admin
  operations

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  For any API call to Nova which takes a tenant_id / user_id as a
  parameter, and inserts it into the Nova database, no validation is
  done of these values.

  This is currently by design, largely because there is no clear way to
  check the existence of those users/projects. Nova has no generic
  credentials to do that to Keystone. It's unclear if there is a way to
  do this from a non admin user.

  Many other bugs are related to this fundamental issue for which there
  is no infrastructure. This includes updating quotas, adding access to
  flavors, etc. This will be a placeholder for all those bugs until
  there is some way to actually address this at the root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1544989/+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 1466773] Re: remove the current consumer from the choices in QoS

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

commit 60a0abe46dfa859eec3ff8406b4d692909b66f7a
Author: Masco Kaliyamoorthy 
Date:   Fri Jun 19 14:12:56 2015 +0530

Remove current consumer in QoS spec edit

In QoS spec edit consumer, the choices including the current choices.
If we select the current choice again, we are getting form error.
Instead of this, this patch removing the current choice from the list.
Displays the current consumer in read only field.

Change-Id: Ie30517a34146f9bf1e8859088cb030f4032e6649
Closes-Bug: #1466773


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

Title:
  remove the current consumer from the choices in QoS

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  While editing the consumer in the QoS spec the choices having all the options 
including current one.
  If we select the current one it is validating and returning form error.
  instead of this we can remove the current choice from the list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1466773/+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 1544999] [NEW] Encountered database ACL.", "error":"referential integrity violation" running OVN stack

2016-02-12 Thread Mala Anand

Public bug reported:

Scenario tested: A tenant has 2 networks, each with a subnet connected through 
a router. Each tenant gets two VMs each in a network. When these two VMs boot 
up, they send iperf traffic across the router.
Scale tenants to 500 and measure scaling performance

Results: Scaled up to 330 vms successfully and failed to boot VMs beyond
330VMs.

The neturon servers including plugin were pegged at 100% and see this database 
integrity violation:
2016-01-28 04:55:04.723 2757 WARNING requests.packages.urllib3.connectionpool 
[req-7964fc18-a95c-4464-a568-038a453d006e 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
2016-01-28 04:55:04.772 2757 WARNING requests.packages.urllib3.connectionpool 
[-] Connection pool is full, discarding connection: identity.open.softlayer.com
2016-01-28 04:55:05.776 2757 WARNING requests.packages.urllib3.connectionpool 
[req-6b80241f-0928-4d93-a80e-988a7b3e9690 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
2016-01-28 04:55:55.380 2757 ERROR neutron.agent.ovsdb.impl_idl [-] OVSDB Error:
{"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"}

2016-01-28 04:55:55.443 2757 ERROR neutron.agent.ovsdb.impl_idl 
[req-0bd44851-ecd9-4957-978f-350b52ada25b cc27c50b17fc4954905db5f3f3eed730 
e53d6cd40c5140c58ec014eb56070917 - - -] Traceback (most recent call last):
File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/native/connection.py",
 line 99, in run
txn.results.put(txn.do_commit())
File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_idl.py", 
line 106, in do_commit
raise RuntimeError(msg)
RuntimeError: OVSDB Error:
{"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"} 

This problem occurs consistently scaling to 500 VMs.

Also have seen this problem occurring in a 5 node devstack installation.
In this case we increased the Neutron api threads to 18 to recreate this
problem.

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

Title:
  Encountered database  ACL.","error":"referential integrity violation"
  running OVN stack

Status in neutron:
  New

Bug description:
  Scenario tested: A tenant has 2 networks, each with a subnet connected 
through a router. Each tenant gets two VMs each in a network. When these two 
VMs boot up, they send iperf traffic across the router.
  Scale tenants to 500 and measure scaling performance

  Results: Scaled up to 330 vms successfully and failed to boot VMs
  beyond 330VMs.

  The neturon servers including plugin were pegged at 100% and see this 
database integrity violation:
  2016-01-28 04:55:04.723 2757 WARNING requests.packages.urllib3.connectionpool 
[req-7964fc18-a95c-4464-a568-038a453d006e 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
  2016-01-28 04:55:04.772 2757 WARNING requests.packages.urllib3.connectionpool 
[-] Connection pool is full, discarding connection: identity.open.softlayer.com
  2016-01-28 04:55:05.776 2757 WARNING requests.packages.urllib3.connectionpool 
[req-6b80241f-0928-4d93-a80e-988a7b3e9690 7a0b7c6414734a93b5dffbc666534690 
e53d6cd40c5140c58ec014eb56070917 - - -] Connection pool is full, discarding 
connection: identity.open.softlayer.com
  2016-01-28 04:55:55.380 2757 ERROR neutron.agent.ovsdb.impl_idl [-] OVSDB 
Error:
  {"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"}

  2016-01-28 04:55:55.443 2757 ERROR neutron.agent.ovsdb.impl_idl 
[req-0bd44851-ecd9-4957-978f-350b52ada25b cc27c50b17fc4954905db5f3f3eed730 
e53d6cd40c5140c58ec014eb56070917 - - -] Traceback (most recent call last):
  File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/native/connection.py",
 line 99, in run
  txn.results.put(txn.do_commit())
  File 
"/opt/neutron/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_idl.py", 
line 106, in do_commit
  raise RuntimeError(msg)
  RuntimeError: OVSDB Error:
  {"details":"Table Logical_Switch column acls row 
36d940b2-26cc-426a-bda6-dd2491f18397 references nonexistent row 
0644cffd-71ca-467f-8e1d-6652968870ef in table ACL.","error":"referential 
integrity violation"} 

  This problem occurs

[Yahoo-eng-team] [Bug 1399065] Re: Quota updated through nova api not refelected in Horizon

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

** This bug is no longer a duplicate of bug 1317515
   flavor-access-add doesn't validate the tenant id
** This bug has been marked a duplicate of bug 1544989
   Nova doesn't validate user/project is valid from keystone during admin 
operations

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

Title:
  Quota updated through nova api not refelected in Horizon

Status in Cinder:
  New
Status in OpenStack Dashboard (Horizon):
  Invalid
Status in neutron:
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I am trying to update the quota of the user using the
  nova.quota.update( ... ), when i do this the quota is reflected in the
  commmond line but the same updated values are not reflected in the
  horizon dashboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1399065/+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 1544990] [NEW] Python table JS polling is borked - multiple errors

2016-02-12 Thread Rob Cresswell

Public bug reported:

GET
http://localhost:8000/project/volumes/?action=row_update=volumes_id=fdd57453-035d-4862-aea7-ef3b505acf13
404 (NOT FOUND)

GET http://localhost:8000/project/volumes/?action=create=volumes
500 (INTERNAL SERVER ERROR)

There are two issues here: the data_table is looking for a template that
doesn't exist, and the polling is trying to iterate over a row that
doesnt exist as it has been deleted.

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

Title:
  Python table JS polling is borked - multiple errors

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  GET
  
http://localhost:8000/project/volumes/?action=row_update=volumes_id=fdd57453-035d-4862-aea7-ef3b505acf13
  404 (NOT FOUND)

  GET http://localhost:8000/project/volumes/?action=create=volumes
  500 (INTERNAL SERVER ERROR)

  There are two issues here: the data_table is looking for a template
  that doesn't exist, and the polling is trying to iterate over a row
  that doesnt exist as it has been deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1544990/+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 1544801] Re: Constant tracebacks with eventlet 0.18.2

2016-02-12 Thread Markus Zoeller (markus_z)

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

** Also affects: neutron
   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/1544801

Title:
  Constant tracebacks with eventlet 0.18.2

Status in Cinder:
  New
Status in neutron:
  New
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Kilo builds, with eventlet 0.18.2 have a constant traceback:

  2016-02-12 00:47:01.126 3936 DEBUG nova.api.openstack.wsgi [-] Calling method 
'>' _process_stack 
/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:783
  2016-02-12 00:47:01.129 3936 INFO nova.osapi_compute.wsgi.server [-] 
Traceback (most recent call last):
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/wsgi.py",
 line 501, in handle_one_response
  write(b''.join(towrite))
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/wsgi.py",
 line 442, in write
  _writelines(towrite)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/support/__init__.py",
 line 62, in safe_writelines
  writeall(fd, item)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/support/__init__.py",
 line 67, in writeall
  fd.write(buf)
File "/usr/lib/python2.7/socket.py", line 324, in write
  self.flush()
File "/usr/lib/python2.7/socket.py", line 303, in flush
  self._sock.sendall(view[write_offset:write_offset+buffer_size])
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 383, in sendall
  tail = self.send(data, flags)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 377, in send
  return self._send_loop(self.fd.send, data, flags)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 364, in _send_loop
  return send_method(data, *args)
  error: [Errno 104] Connection reset by peer

  This is happening across nova, neutron, glance, etc..

  Dropping back to eventlet < 0.18.0 works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1544801/+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 1541742] Re: fullstack tests break when tearing down database

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

commit a5a7b892df46f5d48840f600f03e7be2db999a1d
Author: Jakub Libosvar 
Date:   Wed Feb 10 16:35:30 2016 +

fullstack: Gracefully stop neutron-server process

There is possible scenario that neutron-server loses connection to AMQP
bus and that can cause timeouts when hanging on rpc calls. On the other
hand, we should be able to stop service gracefully even if AMQP server
isn't running.

During teardown there were still neutron-server orphaned api workers
processes running that had open connection to database which caused
unexpected failures.

Note that this change applies only for neutron-server because previous
investigations showed agents using oslo service can hang on rpc causing
other failures. Next step should be making sure rabbitmq is stopped as
last or decrease rpc timeouts in agents.

Change-Id: I3d793ba924dc3fd229d8588f4be1e943614f22bb
Related-bug: 1494363
Closes-bug: 1541742


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

Title:
  fullstack tests break when tearing down database

Status in neutron:
  Fix Released

Bug description:
  http://logs.openstack.org/41/265041/7/check/gate-neutron-dsvm-
  fullstack/8ac64cd/testr_results.html.gz

  Late runs fail with the same errors:

  Traceback (most recent call last):
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/fixtures/fixture.py",
 line 125, in cleanUp
  return self._cleanups(raise_errors=raise_first)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/fixtures/callmany.py",
 line 88, in __call__
  reraise(error[0], error[1], error[2])
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/fixtures/callmany.py",
 line 82, in __call__
  cleanup(*args, **kwargs)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/testresources/__init__.py",
 line 797, in tearDownResources
  resource[1].finishedWith(getattr(test, resource[0]), result)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/testresources/__init__.py",
 line 509, in finishedWith
  self._clean_all(resource, result)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/testresources/__init__.py",
 line 478, in _clean_all
  self.clean(resource)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/provision.py",
 line 127, in clean
  resource.database.engine)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/provision.py",
 line 263, in drop_all_objects
  self.impl.drop_all_objects(engine)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/provision.py",
 line 415, in drop_all_objects
  conn.execute(schema.DropConstraint(fkc))
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
 line 914, in execute
  return meth(self, multiparams, params)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/sql/ddl.py",
 line 68, in _execute_on_connection
  return connection._execute_ddl(self, multiparams, params)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
 line 968, in _execute_ddl
  compiled
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
 line 1146, in _execute_context
  context)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
 line 1337, in _handle_dbapi_exception
  util.raise_from_cause(newraise, exc_info)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py",
 line 200, in raise_from_cause
  reraise(type(exception), exception, tb=exc_tb)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
 line 1139, in _execute_context
  context)
File 
"/opt/stack/new/neutron/.tox/dsvm-fullstack-constraints/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py",

[Yahoo-eng-team] [Bug 1537909] Re: Graph looks smaller after boostrap refactor

2016-02-12 Thread David Lyle

The charts are smaller to better align with bootstrap. Since the charts
convey little meaningful information, 2 values per chart, the smaller
size is not seen as an impediment to understanding the data.

** Changed in: horizon
   Status: New => Won't Fix

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

Title:
  Graph looks smaller after boostrap refactor

Status in OpenStack Dashboard (Horizon):
  Won't Fix

Bug description:
  In the Admin - > Hypervisor graph, the graph is relatively is smaller
  from when M started.

  Increase the size of the graph back to original

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1537909/+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 1516808] Re: nova-api throws TypeError exception while loading osapi_compute

2016-02-12 Thread Michael

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

This has been fixed as of the oslo_middleware 3.0.0 release, and is
already in nova's requirements.

** This bug has been marked a duplicate of bug 1491293
   cors filter won't work when oslo_config_project is set in paste

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

Title:
  nova-api throws TypeError exception while loading osapi_compute

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  Using git revision: e6100f593413de77cc825cb9aeb5b86a739874e9

  When I run nova-api without an arguments I get an exception.  I used
  the api-paste.ini that was in the source tree.

  2015-11-16 16:21:28.376 47780 DEBUG nova.wsgi [-] Loading app osapi_compute 
from /etc/nova/api-paste.ini load_app 
/usr/lib/python2.7/site-packages/nova/wsgi.py:543
  2015-11-16 16:21:28.380 47780 CRITICAL nova [-] TypeError: factory() takes 
exactly 3 arguments (2 given); got ({'__file...va'}, oslo_config_project=...), 
wanted (cls, global_conf, allowed_origin, **local_conf)
  2015-11-16 16:21:28.380 47780 ERROR nova Traceback (most recent call last):
  2015-11-16 16:21:28.380 47780 ERROR nova   File "/usr/bin/nova-api", line 10, 
in 
  2015-11-16 16:21:28.380 47780 ERROR nova sys.exit(main())
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/cmd/api.py", line 56, in main
  2015-11-16 16:21:28.380 47780 ERROR nova server = 
service.WSGIService(api, use_ssl=should_use_ssl)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/service.py", line 328, in __init__
  2015-11-16 16:21:28.380 47780 ERROR nova self.app = 
self.loader.load_app(name)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/wsgi.py", line 544, in load_app
  2015-11-16 16:21:28.380 47780 ERROR nova return 
deploy.loadapp("config:%s" % self.config_path, name=name)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 247, in 
loadapp
  2015-11-16 16:21:28.380 47780 ERROR nova return loadobj(APP, uri, 
name=name, **kw)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 272, in 
loadobj
  2015-11-16 16:21:28.380 47780 ERROR nova return context.create()
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 710, in create
  2015-11-16 16:21:28.380 47780 ERROR nova return 
self.object_type.invoke(self)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 144, in invoke
  2015-11-16 16:21:28.380 47780 ERROR nova **context.local_conf)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/util.py", line 59, in fix_call
  2015-11-16 16:21:28.380 47780 ERROR nova reraise(*exc_info)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/compat.py", line 22, in reraise
  2015-11-16 16:21:28.380 47780 ERROR nova exec('raise t, e, tb', dict(t=t, 
e=e, tb=tb))
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/util.py", line 56, in fix_call
  2015-11-16 16:21:28.380 47780 ERROR nova val = callable(*args, **kw)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/urlmap.py", line 160, in 
urlmap_factory
  2015-11-16 16:21:28.380 47780 ERROR nova app = loader.get_app(app_name, 
global_conf=global_conf)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 350, in 
get_app
  2015-11-16 16:21:28.380 47780 ERROR nova name=name, 
global_conf=global_conf).create()
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 710, in create
  2015-11-16 16:21:28.380 47780 ERROR nova return 
self.object_type.invoke(self)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/loadwsgi.py", line 144, in invoke
  2015-11-16 16:21:28.380 47780 ERROR nova **context.local_conf)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/util.py", line 59, in fix_call
  2015-11-16 16:21:28.380 47780 ERROR nova reraise(*exc_info)
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/compat.py", line 22, in reraise
  2015-11-16 16:21:28.380 47780 ERROR nova exec('raise t, e, tb', dict(t=t, 
e=e, tb=tb))
  2015-11-16 16:21:28.380 47780 ERROR nova   File 
"/usr/lib/python2.7/site-packages/paste/deploy/util.py",

[Yahoo-eng-team] [Bug 1545041] [NEW] Error 500 on resize when hitting quota

2016-02-12 Thread Alexey I. Froloff

Public bug reported:

There's always KeyError exception when processing OverQuota in resize:

  File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 2697, 
in resize
headroom = self._get_headroom(quotas, usages, deltas)
  File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 384, in 
_get_headroom
hr = headroom['instances'] * deltas['ram']
KeyError: 'instances'

This is because "quotas" parameter in OverQuota argument only contains
"cores" and "ram" resources (quota difference for resize operation), but
_get_headroom method expects "instances" resource to be present.

test_resize_quota_exceeds_fails does not handle this situation, because
"quotas" used in this test is "{'resource': 0}" and does not trigger
this branch of code in _get_headroom.

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

Title:
  Error 500 on resize when hitting quota

Status in OpenStack Compute (nova):
  New

Bug description:
  There's always KeyError exception when processing OverQuota in resize:

File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 2697, 
in resize
  headroom = self._get_headroom(quotas, usages, deltas)
File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 384, 
in _get_headroom
  hr = headroom['instances'] * deltas['ram']
  KeyError: 'instances'

  This is because "quotas" parameter in OverQuota argument only contains
  "cores" and "ram" resources (quota difference for resize operation),
  but _get_headroom method expects "instances" resource to be present.

  test_resize_quota_exceeds_fails does not handle this situation,
  because "quotas" used in this test is "{'resource': 0}" and does not
  trigger this branch of code in _get_headroom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1545041/+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 1471916] Re: race with neutron: can't create bridge with the same name

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

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

** Changed in: nova/kilo
   Status: New => In Progress

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

** Changed in: nova/kilo
 Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)

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

Title:
  race with neutron: can't create bridge with the same name

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

Bug description:
  If a node running nova-compute is using the neutron with the
  linuxbridge agent, and the node is also running other neutron agents
  like the l3-agent or dhcp-agent (ie the node is acting as compute node
  and a network node) then races can happen when both nova-compute and
  the linuxbridge agent try to add the same linux bridge at the same
  time. This can cause instances to fail to start.

  http://logs.openstack.org/12/138512/10/experimental/check-tempest-
  dsvm-neutron-linuxbridge/e737f60/

  http://logs.openstack.org/12/138512/10/experimental/check-tempest-
  dsvm-neutron-
  linuxbridge/e737f60/logs/screen-n-cpu.txt.gz#_2015-07-02_03_09_09_131

  The neutron l3-agent added a tap tap device:

  2015-07-02 03:09:06.614 DEBUG neutron.agent.linux.utils 
[req-42397477-9e58-4c7a-aa0b-8e54269f9d34 None None] Running command (rootwrap 
daemon): ['ip', 'link', 'add', 'tapbb2831fd-86', 'type', 'veth', 'peer', 
'name', 'qr-bb2831fd-86', 'netns', 
'qrouter-048a7c31-08a1-4693-91a8-13e3221c0982'] execute_rootwrap_daemon 
/opt/stack/new/neutron/neutron/agent/linux/utils.py:101
  Command: ['ip', 'link', 'add', u'tapbb2831fd-86', 'type', 'veth', 'peer', 
'name', u'qr-bb2831fd-86', 'netns', 
u'qrouter-048a7c31-08a1-4693-91a8-13e3221c0982']

  
  The linuxbridge-agent detects this device and adds the bridge for it's 
network:

  2015-07-02 03:09:09.119 DEBUG neutron.agent.linux.utils 
[req-d4f88282-233b-437e-8157-5d134538d206 None None] Running command (rootwrap 
daemon): ['brctl', 'addbr', 'brq94158651-73'] execute_rootwrap_daemon 
/opt/stack/new/neutron/neutron/agent/linux/utils.py:101
  2015-07-02 03:09:09.122 DEBUG neutron.agent.linux.utils 
[req-d4f88282-233b-437e-8157-5d134538d206 None None] 
  Command: ['brctl', 'addbr', u'brq94158651-73']
  Exit code: 0

  
  About the same time, nova-compute also tried to add the same bridge for a VIF 
it was about to create on the same network, but lost the race and so the 
instance went into an error state:

  2015-07-02 03:09:09.130 DEBUG oslo_concurrency.processutils 
[req-8391bcc1-bc92-48c7-a635-7e3b2f1af76b 
tempest-ServerRescueNegativeTestJSON-1230044074 
  tempest-ServerRescueNegativeTestJSON-1737504944] CMD "sudo nova-rootwrap 
/etc/nova/rootwrap.conf brctl addbr brq94158651-73" returned: 1 in 0.094s exe
  cute 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:247
  2015-07-02 03:09:09.131 DEBUG oslo_concurrency.processutils 
[req-8391bcc1-bc92-48c7-a635-7e3b2f1af76b 
tempest-ServerRescueNegativeTestJSON-1230044074 
  tempest-ServerRescueNegativeTestJSON-1737504944] u'sudo nova-rootwrap 
/etc/nova/rootwrap.conf brctl addbr brq94158651-73' failed. Not Retrying. execut
  e /usr/local/lib/python2.7/dist-packages/oslo_concurrency/processutils.py:295
  2015-07-02 03:09:09.131 DEBUG oslo_concurrency.lockutils 
[req-8391bcc1-bc92-48c7-a635-7e3b2f1af76b 
tempest-ServerRescueNegativeTestJSON-1230044074 tem
  pest-ServerRescueNegativeTestJSON-1737504944] Lock "lock_bridge" released by 
"ensure_bridge" :: held 0.096s inner /usr/local/lib/python2.7/dist-packag
  es/oslo_concurrency/lockutils.py:262
  2015-07-02 03:09:09.131 ERROR nova.compute.manager 
[req-8391bcc1-bc92-48c7-a635-7e3b2f1af76b 
tempest-ServerRescueNegativeTestJSON-1230044074 tempest-S
  erverRescueNegativeTestJSON-1737504944] [instance: 
018793d0-c890-43c7-91ad-5694931cd98c] Instance failed to spawn
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance: 
018793d0-c890-43c7-91ad-5694931cd98c] Traceback (most recent call last):
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance: 
018793d0-c890-43c7-91ad-5694931cd98c]   File 
"/opt/stack/new/nova/nova/compute/mana
  ger.py", line 2113, in _build_resources
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance: 
018793d0-c890-43c7-91ad-5694931cd98c] yield resources
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance: 
018793d0-c890-43c7-91ad-5694931cd98c]   File 
"/opt/stack/new/nova/nova/compute/mana
  ger.py", line 1985, in _build_and_run_instance
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance: 
018793d0-c890-43c7-91ad-5694931cd98c] block_device_info=block_device_info)
  2015-07-02 03:09:09.131 5163 ERROR nova.compute.manager [instance:

[Yahoo-eng-team] [Bug 1545042] [NEW] New i9n tests exceptions_captured context manager introduce a bug in failure reports

2016-02-12 Thread Timur Sufiev

Public bug reported:

If test fails in a non-fatal for Selenium way and it's still able to
fetch page source/ browser log/ screenshot that data is not added to
TestCase reports because of lines like
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/helpers.py#L127
where `content` gets thrown away once we return from block
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/helpers.py#L106

To mitigate that we need to use a container instead of single reference.

** Affects: horizon
 Importance: High
 Assignee: Timur Sufiev (tsufiev-x)
 Status: In Progress

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

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

Title:
  New i9n tests exceptions_captured context manager introduce a bug in
  failure reports

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If test fails in a non-fatal for Selenium way and it's still able to
  fetch page source/ browser log/ screenshot that data is not added to
  TestCase reports because of lines like
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/helpers.py#L127
  where `content` gets thrown away once we return from block
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/helpers.py#L106

  To mitigate that we need to use a container instead of single
  reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1545042/+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 1545058] [NEW] ovs agent Runtime error when checking int_if_name type for the first time

2016-02-12 Thread Rossella Sblendido

Public bug reported:

When ovs agent starts for the first time I get

2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl 
[req-38d5137d-054e-4a60-ac14-3b4d62cfa0da - - - - -] Unable to execute 
['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 
'--columns=type', 'list', 'Interface', 'int-br-public'].
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Traceback 
(most recent call last):
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl   File 
"/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 63, 
in run_vsctl
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl 
log_fail_as_error=False).rstrip()
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py", line 159, in 
execute
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl raise 
RuntimeError(m)
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl RuntimeError:
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Command: 
['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', 
'--timeout=10', '--oneline', '--format=json', '--', '--columns=type', 'list', 
'Interface', 'int-br-public']
2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Exit code: 1

since int-br-public doesn't exists yet.

** Affects: neutron
 Importance: Medium
 Status: New


** Tags: low-hanging-fruit

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

** Tags added: low-hanging-fruit

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

Title:
  ovs agent Runtime error when checking int_if_name type for the first
  time

Status in neutron:
  New

Bug description:
  When ovs agent starts for the first time I get

  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl 
[req-38d5137d-054e-4a60-ac14-3b4d62cfa0da - - - - -] Unable to execute 
['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 
'--columns=type', 'list', 'Interface', 'int-br-public'].
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Traceback 
(most recent call last):
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl   File 
"/usr/lib/python2.7/site-packages/neutron/agent/ovsdb/impl_vsctl.py", line 63, 
in run_vsctl
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl 
log_fail_as_error=False).rstrip()
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py", line 159, in 
execute
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl raise 
RuntimeError(m)
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl 
RuntimeError:
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Command: 
['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', 
'--timeout=10', '--oneline', '--format=json', '--', '--columns=type', 'list', 
'Interface', 'int-br-public']
  2016-02-11 18:49:15.778 12566 ERROR neutron.agent.ovsdb.impl_vsctl Exit code: 
1

  since int-br-public doesn't exists yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1545058/+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 1544349] Re: neutron-vpnaas db migration breaks in MySQL 5.6

Reviewed:  https://review.openstack.org/278796
Committed: 
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=f4babb050ba5a54c9c9f91e2d1ac370539dadf3c
Submitter: Jenkins
Branch:master

commit f4babb050ba5a54c9c9f91e2d1ac370539dadf3c
Author: ajmiller 
Date:   Wed Feb 10 15:34:34 2016 -0800

Remove Foreign Key constraint during ALTER

Beginning with MySQL 5.6, ALTER will fail if there are foreign key
constraints affecting the column being altered.  This patch
removes the constraint, before applying the update and then
restores the constraint.

Change-Id: I0982ec34d51f9e8004d85512bc8e0cde7b84b4f2
Depends-On: Id3f199d688d648f4618a6850d094e26ca6bb9a7f
Closes-Bug: 1544349


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

Title:
  neutron-vpnaas db migration breaks in MySQL 5.6

Status in neutron:
  Fix Released

Bug description:
  Starting in MySQL 5.6, it is illegal to alter a column that is subject
  to a Foreign Key constraint, and any migration doing such will fail.
  Other projects (I have found examples in Barbican and Trove) work
  around this by removing the constraint, performing the ALTER, and
  reinstating the constraint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1544349/+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 1467843] Re: Experimental job for Nova API under Apache2 fails

This is really a devstack setup issue, not a nova api issue

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

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

Title:
  Experimental job for Nova API under Apache2 fails

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Experimental job for Nova API services under Apache2 fails with error message:
  "Syntax error on line 4 of /etc/apache2/sites-enabled/nova-api.conf Invalid 
process count for WSGI daemon process."
  And apache config contains line:
  "WSGIDaemonProcess nova-api processes=0 threads=1 user=stack 
display-name=%{GROUP}"
  Option 'processes' can not contain 0 value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1467843/+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 1483417] Re: move vpn api tests from neutron to neutron-vpnaas

Reviewed:  https://review.openstack.org/211381
Committed: 
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=3cae934aee276659d07eb21ce3615d8c44ea1077
Submitter: Jenkins
Branch:master

commit 3cae934aee276659d07eb21ce3615d8c44ea1077
Author: madhusudhan-kandadai 
Date:   Mon Aug 10 18:23:00 2015 -0700

Add VPNaaS API tests in neutron-vpnaas tree

Change [1] implemented that VPN tests are removed from
neutron tree. This change adds the same test with their
resources to run them in neutron-vpnaas tree.

In the other patch, a new CI job can be pushed in project-config
so that this api test can be tested.

[1] https://review.openstack.org/278606

Change-Id: Ia7d7b53aaeda8c328dcb7694f1a9f974e4f2ca31
Closes-Bug: #1483417


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

Title:
  move vpn api tests from neutron to neutron-vpnaas

Status in neutron:
  Fix Released

Bug description:
  Since, vpnaas has a separate repo, we need to move the api tests from
  neutron project to vpnaas repo and then test it is working. If it is
  working, then delete the same files in neutron project

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1483417/+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 1458122] Re: nova shouldn't error if we can't schedule all of max_count instances at boot time

This is really a feature as it changes quite substantially how the bulk
create works and is accounted for. This should really come in as a spec
I think.

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

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

Title:
  nova shouldn't error if we can't schedule all of max_count instances
  at boot time

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  When booting up instances, nova allows the user to specify a "min
  count" and a "max count".

  Currently, if the user has quota space for "max count" instances, then
  nova will try to create them all.  If any of them can't be scheduled,
  then the creation of all of them will be aborted and they will all be
  put into an error state.

  Arguably, if nova was able to schedule at least "min count" instances
  (which defaults to 1) then it should continue on with creating those
  instances that it was able to schedule.  Only if nova cannot create at
  least "min count" instances should nova actually consider the request
  as failed.

  And I think that if nova can't schedule "max count" instances, but can
  schedule at least "min count" instances, then it shouldn't put the
  others into an error state--it should be like they never actually
  existed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1458122/+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 1497740] Re: nova API proxy to neutron should avoid race-ful behavior

The API semantics are really async. For different semantics we should
probe directly to neutron.

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

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

Title:
  nova API proxy to neutron should avoid race-ful behavior

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

Bug description:
  Version of Nova/OpenStack: liberty

  Calls to associate a floating IP with an instance currently returns a
  202 status.  When proxying these calls to neutron, just returning 202
  without having validated the status of the floating IP first leads to
  raceful failures in tempest scenario tests (for example, see the
  test_volume_boot_pattern failure in
  http://logs.openstack.org/20/225420/1/check/gate-tempest-dsvm-neutron-
  dvr/a78a052/logs/testr_results.html.gz)

  Is it possible to (when proxying to neutron) first verify the status
  of the neutron floating IP before returning the 202 status

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1497740/+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 1545101] [NEW] "TypeError: init() takes exactly 3 arguments (2 given)" in n-api logs for nova metadata api request

Public bug reported:

http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
neutron-
multinode/8f1deec/logs/new/screen-n-api.txt.gz?level=INFO#_2016-02-12_16_28_16_860

2016-02-12 16:28:16.860 20168 INFO nova.metadata.wsgi.server [-] Traceback 
(most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 470, in 
handle_one_response
result = self.application(self.environ, start_response)
  File "/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 216, in 
__call__
return app(environ, start_response)
  File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in 
__call__
resp = self.call_func(req, *args, **self.kwargs)
  File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in 
call_func
return self.func(req, *args, **kwargs)
  File "/opt/stack/new/nova/nova/api/ec2/__init__.py", line 32, in __call__
return webob.exc.HTTPException(message=_DEPRECATION_MESSAGE)
TypeError: __init__() takes exactly 3 arguments (2 given)

This only shows up in the gate-grenade-dsvm-neutron-multinode job which
is not running the n-api-meta service but is running the neutron
metadata service, which has a bunch of warnings because it's not getting
valid responses back from the nova metadata API (b/c it's not running):

http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
neutron-multinode/8f1deec/logs/new/screen-q-meta.txt.gz?level=TRACE

** Affects: nova
 Importance: High
 Status: Confirmed

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

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

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

Title:
  "TypeError: __init__() takes exactly 3 arguments (2 given)" in n-api
  logs for nova metadata api request

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
  neutron-
  
multinode/8f1deec/logs/new/screen-n-api.txt.gz?level=INFO#_2016-02-12_16_28_16_860

  2016-02-12 16:28:16.860 20168 INFO nova.metadata.wsgi.server [-] Traceback 
(most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 470, 
in handle_one_response
  result = self.application(self.environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 216, in 
__call__
  return app(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in 
__call__
  resp = self.call_func(req, *args, **self.kwargs)
File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in 
call_func
  return self.func(req, *args, **kwargs)
File "/opt/stack/new/nova/nova/api/ec2/__init__.py", line 32, in __call__
  return webob.exc.HTTPException(message=_DEPRECATION_MESSAGE)
  TypeError: __init__() takes exactly 3 arguments (2 given)

  This only shows up in the gate-grenade-dsvm-neutron-multinode job
  which is not running the n-api-meta service but is running the neutron
  metadata service, which has a bunch of warnings because it's not
  getting valid responses back from the nova metadata API (b/c it's not
  running):

  http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
  neutron-multinode/8f1deec/logs/new/screen-q-meta.txt.gz?level=TRACE

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1545101/+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 1326124] Re: Allow for editing of existing Security Rules

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

Title:
  Allow for editing of existing Security Rules

Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in neutron:
  Confirmed
Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Currently in the Horizon UI, after adding a security rule you can only
  delete it. If you mess up one of the fields, there's no edit option
  available where you could see the create dialog again, flip it from
  TCP to UDP or whatever you forgot to do, and then update the rule.
  You've got to remember everything you need to fill out, delete it, and
  then create it properly.

  It'd be much simpler if users could edit a security rule group,
  instead of having to delete and recreate.

  If there's nothing in nova that lets us edit a rule, could we fake it
  in the UI and when they "edit" a rule, we just pull out all the
  configured info, populate a create dialog with it, and then when they
  click save, it deletes the old rule and creates the updated one?

  As someone who has entered lots of security rules, I can tell you
  firsthand that it's really demoralizing when you realize you forgot to
  change TCP to UDP on your otherwise correct rule after creating it,
  and have to delete it and try again, remembering which position you
  were in on your port table so you don't start entering a different
  rule...

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1326124/+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 1325736] Re: Security Group Rules can only be specified in one direction

Closing an a possible, though unlikely future feature

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

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

Title:
  Security Group Rules can only be specified in one direction

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Compute (nova):
  Opinion

Bug description:
  It might save users potentially a lot of time if instead of only
  offering an INGRESS and an EGRESS direction, if they could specify a
  BOTH direction. Whenever someone needs to enter both an ingress and
  egress rule for the same port they have to enter it twice, remembering
  all of the information they need (since it can't be cloned). If they
  forget to flip the direction the second time from the default value,
  it'll error out as a duplicate and they'll have to try a third time.
  If they messed up the second rule, there's no edit, so they would have
  to delete it if they got a value wrong and do it all over again.

  It would be awesome if the UI allowed for specifying both an ingress
  and egress rule at the same time, even if all it did was create the
  ingress and egress rows and put them in the table, at least they'd be
  guaranteed to have the same configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1325736/+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 1443494] Re: Return supported micro-version by http headers when request with invalid micro-version

I think we're actually going to not fix this issue, the extra headers
are mostly bloat

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

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

Title:
  Return supported micro-version by http headers when request with
  invalid micro-version

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

Bug description:
  Although we add API discover for micro-version by this
  https://launchpad.net/bugs/1443375, but if request without discover
  first and with invalid micro-version, the request will failed and
  without the supported version info, then user need send another
  discover request for get supported version. we can return supported
  version by http headers when the request failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1443494/+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 1545117] [NEW] neutron: 500 error when trying to attach no network to an instance with no network

Public bug reported:

It's possible to create a VM with nova using neutron as the backend and
have no network information. If the tenant doesn't have any available
network in neutron and doesn't request any network, the neutron backend
will simply log a message and continue.

If you then later attempt to use the os-attach-interface API and don't
provider a network, and the tenant still doesn't have any networks
available in neutron, then the request fails in the neutronv2 API code
with an IndexError because it's assuming there is at least one available
network:

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

2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
executor_callback))
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
executor_callback)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions result = 
func(ctxt, **new_args)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions payload)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
six.reraise(self.type_, self.value, self.tb)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions return f(self, 
context, *args, **kw)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/manager.py", line 385, in decorated_function
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
kwargs['instance'], e, sys.exc_info())
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
six.reraise(self.type_, self.value, self.tb)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/manager.py", line 373, in decorated_function
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions return 
function(self, context, *args, **kwargs)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/compute/manager.py", line 4933, in attach_interface
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions context, 
instance, port_id, network_id, requested_ip)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/network/neutronv2/api.py", line 775, in 
allocate_port_for_instance
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
requested_networks=requested_networks)
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/network/neutronv2/api.py", line 579, in 
allocate_for_instance
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
objects.NetworkRequest(network_id=nets[0]['id']))
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions 
2016-02-12 09:34:32.188 TRACE nova.api.openstack.extensions IndexError: list 
index out of range

We should at least handle that case and report a 400 to the user.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: network neutron

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

Title:
  neutron: 500 error

[Yahoo-eng-team] [Bug 1544801] Re: Constant tracebacks with eventlet 0.18.2

2016-02-12 Thread Jesse Keating

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

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

Title:
  Constant tracebacks with eventlet 0.18.2

Status in Cinder:
  New
Status in Glance:
  New
Status in neutron:
  New
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Kilo builds, with eventlet 0.18.2 have a constant traceback:

  2016-02-12 00:47:01.126 3936 DEBUG nova.api.openstack.wsgi [-] Calling method 
'>' _process_stack 
/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:783
  2016-02-12 00:47:01.129 3936 INFO nova.osapi_compute.wsgi.server [-] 
Traceback (most recent call last):
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/wsgi.py",
 line 501, in handle_one_response
  write(b''.join(towrite))
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/wsgi.py",
 line 442, in write
  _writelines(towrite)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/support/__init__.py",
 line 62, in safe_writelines
  writeall(fd, item)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/support/__init__.py",
 line 67, in writeall
  fd.write(buf)
File "/usr/lib/python2.7/socket.py", line 324, in write
  self.flush()
File "/usr/lib/python2.7/socket.py", line 303, in flush
  self._sock.sendall(view[write_offset:write_offset+buffer_size])
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 383, in sendall
  tail = self.send(data, flags)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 377, in send
  return self._send_loop(self.fd.send, data, flags)
File 
"/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/eventlet/greenio/base.py",
 line 364, in _send_loop
  return send_method(data, *args)
  error: [Errno 104] Connection reset by peer

  This is happening across nova, neutron, glance, etc..

  Dropping back to eventlet < 0.18.0 works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1544801/+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 1521236] Re: Missing list of stores in glance-api.conf

2016-02-12 Thread nikhil komawar

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

** Changed in: glance-store
   Status: Confirmed => Invalid

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

Title:
  Missing list of stores in glance-api.conf

Status in Glance:
  Invalid
Status in glance_store:
  Invalid
Status in glance_store liberty series:
  Confirmed

Bug description:
  We used to give some indication of which stores could be configured:

   [glance_store]
   # List of which store classes and store class locations are
   # currently known to glance at startup.
   # Deprecated group/name - [DEFAULT]/known_stores
   # Existing but disabled stores:
   #  glance.store.rbd.Store,
   #  glance.store.s3.Store,
   #  glance.store.swift.Store,
   #  glance.store.sheepdog.Store,
   #  glance.store.cinder.Store,
   #  glance.store.gridfs.Store,
   #  glance.store.vmware_datastore.Store,
   #stores = glance.store.filesystem.Store,
   # glance.store.http.Store

  
  We don't seem to have a full list of stores in etc/glance-api.conf any more:

   [glance_store]

   #
   # From glance.store
   #

   # List of stores enabled (list value)
   #stores = file,http

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1521236/+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 1539971] Re: Style: Material Design: Compression warning for view-grid override

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

commit 4f072790b68062ebff0701c682f739442488
Author: Diana Whitten 
Date:   Thu Feb 11 17:17:33 2016 -0700

Material: Compression warning for missing icon

On compressing the 'material' theme:

Compressing... SassDeprecationWarning: Can't find any matching rules
to extend u'.mdi-view-grid' -- thiswill be fatal in 2.0, unless
!optional is specified! (at custom/horizon/_icons.scss:10)
WARNING:py.warnings:SassDeprecationWarning: Can't find any matching
rules to extend u'.mdi-view-grid' -- thiswill be fatal in 2.0, unless
!optional is specified! (at custom/horizon/_icons.scss:10)

The icon that we were attempting to replace is this one:
http://fortawesome.github.io/Font-Awesome/icon/th-large/

The correct replacement for this, IS in fact view-grid,
but view-grid is not available in our current version of
material design icons. We will fall back to view-module
until we can get this updated:

https://materialdesignicons.com/icon/view-module

Closes-bug: #1539971

Change-Id: If57d8cbd332a219dd5b6d986ce4fc938034533d6


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

Title:
  Style: Material Design: Compression warning for view-grid override

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  On compressing 'matieral':

  Compressing... SassDeprecationWarning: Can't find any matching rules to 
extend u'.mdi-view-grid' -- thiswill be fatal in 2.0, unless !optional is 
specified! (at custom/horizon/_icons.scss:10)
  WARNING:py.warnings:SassDeprecationWarning: Can't find any matching rules to 
extend u'.mdi-view-grid' -- thiswill be fatal in 2.0, unless !optional is 
specified! (at custom/horizon/_icons.scss:10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1539971/+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] Re: create tests for trusts and implied roles

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

commit 98934a3e548f8abd8722b01493356fcc8586b1ba
Author: Steve Martinelli 
Date:   Mon Feb 8 03:48:25 2016 -0500

add a test that uses trusts and implies roles

looks like implied roles are not expanded for tokens that were
created from trusts

Change-Id: I76b94faf094721c254caa6f9d7289d084c957d80
Closes-Bug: 1539240
Related-Bug: 1543318


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

Title:
  create tests for trusts and implied roles

Status in OpenStack Identity (keystone):
  Fix Released

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 1540254] Re: "#flake8: noqa" is using incorrectly

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

commit f94463bb53f8799882a8a2df6f92ea3195eb3fc6
Author: Bo Wang 
Date:   Mon Feb 1 16:58:54 2016 +0800

Switch to use "# noqa" correctly

"# flake8: noqa" option disables all checks for the whole file.
To disable one line we should use "# noqa".
switch to use "# noqa" and fix the hidden hacking issues.

Change-Id: I1fe747da7a9ab345d0c84a8cb82a8243bf1ee761
Closes-Bug: #1540254


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

Title:
  "#flake8: noqa" is using incorrectly

Status in Designate:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-novaclient:
  Fix Released

Bug description:
  "# flake8: noqa" option disables all checks for the whole file. To
  disable one line we should use "# noqa".

  Refer to: https://pypi.python.org/pypi/flake8
  
https://github.com/openstack/python-keystoneclient/commit/3b766c51438396a0ab0032de309c9d56e275e0cb

To manage notifications about this bug go to:
https://bugs.launchpad.net/designate/+bug/1540254/+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 1543251] Re: Missing comma in the Column status_choices tuple

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

commit 3802147d70e0729be68449eff5b3c1c184ae8fef
Author: Alok Kumar 
Date:   Fri Feb 12 00:50:27 2016 +0530

Fixed missing ',' in docstring of Column table.

There was a missing comma in the docstring for table Column's
status_choices field and in helpText of field cell_attributes_getter.


http://docs.openstack.org/developer/horizon/ref/tables.html#horizon.tables.Column.status_choices

Added simple comma at both the places.

Closes-Bug: #1543251

Change-Id: Ibb71e95087825f7bbab86ba5cadbf00fc44d52de


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

Title:
  Missing comma in the Column status_choices tuple

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Missing comma in the tuple example:

  
http://docs.openstack.org/developer/horizon/ref/tables.html#horizon.tables.Column.status_choices

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1543251/+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 1545177] [NEW] nova_object.changes compare intermittently fails in py34 unit tests

Public bug reported:

Seen here:

http://logs.openstack.org/81/270981/3/check/gate-nova-
python34/dfbe2a4/console.html#_2016-02-11_23_31_38_797

2016-02-11 23:31:38.797 | 
nova.tests.unit.compute.test_compute.ComputeAPITestCase.test_create_with_numa_topology
2016-02-11 23:31:38.798 | 
--
2016-02-11 23:31:38.798 | 
2016-02-11 23:31:38.798 | Captured traceback:
2016-02-11 23:31:38.798 | ~~~
2016-02-11 23:31:38.798 | b'Traceback (most recent call last):'
2016-02-11 23:31:38.798 | b'  File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mock/mock.py",
 line 1305, in patched'
2016-02-11 23:31:38.798 | b'return func(*args, **keywargs)'
2016-02-11 23:31:38.798 | b'  File 
"/home/jenkins/workspace/gate-nova-python34/nova/tests/unit/compute/test_compute.py",
 line 7656, in test_create_with_numa_topology'
2016-02-11 23:31:38.799 | b'
instances[0].numa_topology.cells[0].obj_to_primitive())'
2016-02-11 23:31:38.799 | b'  File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
 line 362, in assertEqual'
2016-02-11 23:31:38.799 | b'self.assertThat(observed, matcher, message)'
2016-02-11 23:31:38.799 | b'  File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
 line 447, in assertThat'
2016-02-11 23:31:38.799 | b'raise mismatch_error'
2016-02-11 23:31:38.799 | b'testtools.matchers._impl.MismatchError: !=:'
2016-02-11 23:31:38.799 | b"reference = {'nova_object.changes': ['memory', 
'cpuset', 'id'],"
2016-02-11 23:31:38.799 | b" 'nova_object.data': {'cpu_pinning_raw': None,"
2016-02-11 23:31:38.799 | b"  'cpu_policy': None,"
2016-02-11 23:31:38.800 | b"  'cpu_thread_policy': 
None,"
2016-02-11 23:31:38.800 | b"  'cpu_topology': None,"
2016-02-11 23:31:38.800 | b"  'cpuset': (1, 2),"
2016-02-11 23:31:38.800 | b"  'id': 0,"
2016-02-11 23:31:38.800 | b"  'memory': 512,"
2016-02-11 23:31:38.800 | b"  'pagesize': None},"
2016-02-11 23:31:38.800 | b" 'nova_object.name': 'InstanceNUMACell',"
2016-02-11 23:31:38.800 | b" 'nova_object.namespace': 'nova',"
2016-02-11 23:31:38.800 | b" 'nova_object.version': '1.3'}"
2016-02-11 23:31:38.801 | b"actual= {'nova_object.changes': ['id', 
'memory', 'cpuset'],"
2016-02-11 23:31:38.801 | b" 'nova_object.data': {'cpu_pinning_raw': None,"
2016-02-11 23:31:38.801 | b"  'cpu_policy': None,"
2016-02-11 23:31:38.801 | b"  'cpu_thread_policy': 
None,"
2016-02-11 23:31:38.801 | b"  'cpu_topology': None,"
2016-02-11 23:31:38.801 | b"  'cpuset': (1, 2),"
2016-02-11 23:31:38.801 | b"  'id': 0,"
2016-02-11 23:31:38.801 | b"  'memory': 512,"
2016-02-11 23:31:38.802 | b"  'pagesize': None},"
2016-02-11 23:31:38.802 | b" 'nova_object.name': 'InstanceNUMACell',"
2016-02-11 23:31:38.802 | b" 'nova_object.namespace': 'nova',"
2016-02-11 23:31:38.802 | b" 'nova_object.version': '1.3'}"
2016-02-11 23:31:38.802 | b''
2016-02-11 23:31:38.802 | b''

The nova_object.changes are a set which aren't sorted so we get
intermittent results on the py34 job.

Dan Smith has a patch for this here:
https://review.openstack.org/#/c/279242/

** Affects: nova
 Importance: Medium
 Assignee: Dan Smith (danms)
 Status: In Progress


** Tags: testing

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

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

** Changed in: nova
 Assignee: (unassigned) => Dan Smith (danms)

** Tags added: testing

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

Title:
  nova_object.changes compare intermittently fails in py34 unit tests

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Seen here:

  http://logs.openstack.org/81/270981/3/check/gate-nova-
  python34/dfbe2a4/console.html#_2016-02-11_23_31_38_797

  2016-02-11 23:31:38.797 | 
nova.tests.unit.compute.test_compute.ComputeAPITestCase.test_create_with_numa_topology
  2016-02-11 23:31:38.798 | 
--
  2016-02-11 23:31:38.798 | 
  2016-02-11 23:31:38.798 | Captured traceback:
  2016-02-11 23:31:38.798 | ~~~
  2016-02-11 23:31:38.798 | b'Traceback (most recent call last):'
  2016-02-11 23:31:38.798 | b'  File

[Yahoo-eng-team] [Bug 1541540] Re: Implied role "root_role" config needs to be expanded

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

commit f984518971fe2c91630016c8e726ae00e5d41e6a
Author: John Dennis 
Date:   Thu Feb 11 11:31:36 2016 -0500

Convert assignment.root_role config option to list of strings

The assigment.root_role config option was previously a single string
which specified a role name that was prohibited from being added as an
implied role. By default it was 'admin'. For greater flexibility we
now permit a list of role names that are prohibited from being
implied.

Summary of changes:

* Change assigment.root_role from cfg.StrOpt to cfg.ListOpt.
  ListOpt is preferred over MultiStrOpt because of config file formatting.
  Update help for option.

* Change assigment.root_role name to assignment.prohibited_implied_role

* Change test for implied role name from string equality to
  membership in list of strings.

* Expand ImpliedRolesTests.test_root_role_as_implied_role_forbidden()
  unit test to test 2 prohibited implied role names and 1 valid
  implied. role name.

Change-Id: Idfe14080e2f1ec1e89b85d8f5f00aad187f1fd22
Closes-Bug: #1541540
Signed-off-by: John Dennis 


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

Title:
  Implied role "root_role" config needs to be expanded

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The "root_role" option is insufficient for blocking "implied" roles.
  This needs to be expanded to where a list opt makes sense. There will
  likely be many cases where more than one role should never be allowed
  to be implied, for example "domain admin" if the domain admin needs to
  come from SSO.

  Suggest making it an option that is a listopt and calling it something
  not "root_role".

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1541540/+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 1545167] [NEW] _compare_results incorrectly reports extra list items when items in lists don't match

2016-02-12 Thread Augustina Ragwitz

Public bug reported:

I discovered this bug while refactoring functional tests. This happens
in the current Nova master.

The _compare_results function is defined in
nova/tests/functional/api_samples_test_base.py

To reproduce, pass two lists to _compare_results that are the same
length but have one item not equal.

list1 = [{u'foo': u'bar', u'bar': u'baz'}]

list2 = [{u'foo': u'baz', u'bar': u'baz'}]

_compare_results returns the following:

nova.tests.functional.api_samples_test_base.NoMatch: Extra list items in 
template:
{u'foo': u'bar', u'bar': u'baz'}
Extra list items in Test:
{u'foo': u'baz', u'bar': u'baz'}

While this is "technically" accurate, it's really hard to debug if you
can imagine a lengthy, nested json file dumped into that response.

_compare_results is already checking each item in the list, it should
just be returning a list of keys that don't match, not the whole thing!

** Affects: nova
 Importance: Medium
 Assignee: Augustina Ragwitz (auggy)
 Status: Confirmed


** Tags: testing

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

Title:
  _compare_results incorrectly reports extra list items when items in
  lists don't match

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  I discovered this bug while refactoring functional tests. This happens
  in the current Nova master.

  The _compare_results function is defined in
  nova/tests/functional/api_samples_test_base.py

  To reproduce, pass two lists to _compare_results that are the same
  length but have one item not equal.

  list1 = [{u'foo': u'bar', u'bar': u'baz'}]

  list2 = [{u'foo': u'baz', u'bar': u'baz'}]

  _compare_results returns the following:

  nova.tests.functional.api_samples_test_base.NoMatch: Extra list items in 
template:
  {u'foo': u'bar', u'bar': u'baz'}
  Extra list items in Test:
  {u'foo': u'baz', u'bar': u'baz'}

  While this is "technically" accurate, it's really hard to debug if you
  can imagine a lengthy, nested json file dumped into that response.

  _compare_results is already checking each item in the list, it should
  just be returning a list of keys that don't match, not the whole
  thing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1545167/+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 1473553] Re: AuthContextMiddleware re-implements AdminToken

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

commit c29ff68a6f91d020ee248f70ba6f2a7a2801013b
Author: Brant Knudson 
Date:   Mon Jul 6 19:51:48 2015 -0500

AuthContextMiddleware admin token handling

The AuthContextMiddleware shouldn't be re-implementing the
AdminTokenAuthMiddleware but using the request environment
context setting that the admin token middleware sets up.

This makes it so that admin token handling is in one place
rather than duplicating it and allows for an alternative
implementation of the admin token middleware.

The old behavior is left in place as deprecated to be removed
in a future release.

ReleaseNotesImpact
 - The paste.ini file is changed to put the admin token
   middleware first so that the auth context middleware can use
   the results. It's deprecated to have the admin token
   middleware after the auth context middleware.

Closes-Bug: 1473553
Change-Id: I658213699ac4af0abd08f893d9cf18ef0af5827d


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

Title:
  AuthContextMiddleware re-implements AdminToken

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  
  AuthContextMiddleware essentially re-implements the default 
AdminTokenAuthMiddleware:

  class AdminTokenAuthMiddleware(wsgi.Middleware):
  ...
  context['is_admin'] = (token == CONF.admin_token)

  class AuthContextMiddleware(wsgi.Middleware):
  ...
  if token_id == CONF.admin_token:

  The problem is, what if someone decides they want to implement their
  own `AdminTokenAuthMiddleware` that implements "admin token"
  differently. For example, using a special client certificate instead.

  This should be possible, but it's not because AuthContextMiddleware
  decided to re-implement AdminTokenAuthMiddleware rather than using its
  output (the setting of is_admin in the context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1473553/+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 1540064] Re: neutron router-update --routes should prevent user from adding existing cidr

2016-02-12 Thread Martin Hickey

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

Title:
  neutron router-update --routes should prevent user from adding
  existing cidr

Status in neutron:
  Opinion

Bug description:
  Find this when do some debug.
  Steps to reproduce:
  1) I have a router with some subnets connected to it, for example 
100.0.0.0/24 100.0.1.0/24. There will be some routes that are created by the 
kernel for the router interfaces.
  # ip r
  100.0.1.0/24 dev qr-fef63af2-82  proto kernel  scope link  src 100.0.1.1 
  100.0.0.0/24 dev qr-af2ae2b0-8c  proto kernel  scope link  src 100.0.0.1

  2) I update the extra route by (just for testing)
  neutron router-update router1 --route 
destination=100.0.1.0/24,nexthop=100.0.0.3 

  3) The route that was for 100.0.1.0/24 will be replaced.
  # ip r
  100.0.1.0/24 via 100.0.0.3 dev qr-af2ae2b0-8c 
  100.0.0.0/24 dev qr-af2ae2b0-8c  proto kernel  scope link  src 100.0.0.1

  4) I clear the extra route that I added by using 
  neutron router-update router1 --no-routes
  The I get the following routes in router namespace:
  # ip r
  100.0.0.0/24 dev qr-af2ae2b0-8c  proto kernel  scope link  src 100.0.0.1

  As a result, I lost the connection to 100.0.1.0/24.

  
  I think neutron should prevent user from adding extra routes to the existing 
cidrs that have been connected to router(as interface or as gateway).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1540064/+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 1532768] Re: Missing service 'region' and endpoint name for EndpointFilterCatalog

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

commit f767b641e8aecc4e1102f5241b9ede4b0ac46d9c
Author: Einar Forselv 
Date:   Mon Jan 11 13:07:28 2016 +0100

Missing 'region' in service and 'name' in endpoint for EndpointFilterCatalog

EndpointFilterCatalog should return a catalog consistent with the normal
v3 catalog. This means that a service will return the 'region' property
(same as 'region_id') for backwards compatibility. In addition each
endpoint will return its name.

Change-Id: I0f1a337dae1ee2f910d34c14624854a3c9f06358
Closes-Bug: 1532768


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

Title:
  Missing service 'region' and endpoint name for EndpointFilterCatalog

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  This is similar to :
  https://bugs.launchpad.net/keystone/+bug/1410543 : Include service name in 
filtered catalog
  (Work has been done to  collapse the catalog drivers into a single driver, 
but the progress on this has been fairly slow lately)

  This bug is meant as a quick fix to get endpoint filtering to work and
  be consistent with the normal v3 catalog.

  The current EndpointFilterCatalog are missing the following to be consistent 
with the normal v3 catalog :
  * EndpointFilterCatalog only returns 'region_id'. The normal v3 catalog also 
includes 'region' for backwards compatibility. The vast amount of tools still 
use 'region' and will fail unless it's present.
  * EndpointFilterCatalog doesn't include the endpoint's name.

  EndpointFilterCatalog currently returns the following :

  'endpoints': [{

'url':'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
  }, 

  Normal v3 catalog returns the following

  'endpoints': [{
'url': 
'https://objects.zetta.io:8443/v1/AUTH_d67f3235ece449ecaf8a9f731ca9a10c', 
'interface': 'public', 
'region_id': 'no-osl1',
'region': 'no-osl1',
'id': u'6513c4a646594292a3f8cdf65a0882f3'
}], 
'type': 'object-store',
'name': 'swift',
'id': '7a806e12a8644d7ea67e6e4f4c287fec'
  },

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1532768/+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 1545153] [NEW] BadRequest: Invalid input for dns_name. Name must not start or end with a hyphen.

Public bug reported:

I'm seeing this in a tempest job run:

http://logs.openstack.org/21/279721/3/check/gate-tempest-dsvm-neutron-
full/8292a4a/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-02-12_19_46_26_529

2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api 
[req-bb911afc-2a34-4812-8c83-0bb6eabc527f 
tempest-TestSecurityGroupsBasicOps-630833589 
tempest-TestSecurityGroupsBasicOps-22256548] [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] Neutron error creating port on network 
6796595c-c739-4080-b8a9-997f6936208c
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] Traceback (most recent call last):
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 255, in _create_port
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] port = 
port_client.create_port(port_req_body)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
100, in with_params
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] ret = self.function(instance, *args, 
**kwargs)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
525, in create_port
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] return self.post(self.ports_path, 
body=body)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
271, in post
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] headers=headers, params=params)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
206, in do_request
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] 
self._handle_fault_response(status_code, replybody)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 
182, in _handle_fault_response
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] exception_handler_v20(status_code, 
des_error_body)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b]   File 
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 69, 
in exception_handler_v20
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] status_code=status_code)
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] BadRequest: Invalid input for dns_name. 
Reason: 'tempest-server-tempest-testsecuritygroupsbasicops-22256548-gen-' not a 
valid PQDN or FQDN. Reason: Name 
'tempest-server-tempest-testsecuritygroupsbasicops-22256548-gen-' must not 
start or end with a hyphen..
2016-02-12 19:46:26.529 19015 ERROR nova.network.neutronv2.api [instance: 
25bf790e-cc4b-42fa-99f2-38f9bb7a004b] 
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager 
[req-bb911afc-2a34-4812-8c83-0bb6eabc527f 
tempest-TestSecurityGroupsBasicOps-630833589 
tempest-TestSecurityGroupsBasicOps-22256548] Instance failed network setup 
after 1 attempt(s)
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager Traceback (most recent 
call last):
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager   File 
"/opt/stack/new/nova/nova/compute/manager.py", line 1564, in 
_allocate_network_async
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager 
bind_host_id=bind_host_id)
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager   File 
"/opt/stack/new/nova/nova/network/neutronv2/api.py", line 662, in 
allocate_for_instance
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager 
self._delete_ports(neutron, instance, created_port_ids)
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager 
self.force_reraise()
2016-02-12 19:46:26.553 19015 ERROR nova.compute.manager   File

[Yahoo-eng-team] [Bug 1522317] Re: string in glance.service.js cannot control the word order in translations

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

commit ed28f129d5cdd680e7b051ccac520c8304920887
Author: Akihiro Motoki 
Date:   Thu Dec 3 17:51:06 2015 +0900

Use interpolate in JS to allow translators to control word order

String concatenation is not recommended for better translation.

Closes-Bug: #1522317
Change-Id: Ib90f8e119d330b27023f2ef05bd24b048f1045bb


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

Title:
  string in glance.service.js cannot control the word order in
  translations

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  openstack_dashboard/static/app/core/openstack-service-
  api/glance.service.js

return suppressError ? promise : promise.error(function() {
  toastService.add('error', gettext('Unable to delete the image with 
id: ') + imageId);
});

  String concatenation should not be used.
  https://docs.djangoproject.com/en/1.8/topics/i18n/translation/#interpolate

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1522317/+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 1440107] Re: Clearing up project assignments makes assumptions that domain_id != project_id

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

commit 23fc378cac759fa8fea109ed1f42dc85bf90d4fe
Author: Clenimar 
Date:   Tue Feb 9 17:11:33 2016 -0300

Avoid wrong deletion of domain assignments

The method delete_project_assignments() in assignment backend removes
all assignments for a project - although the code fails to set the type
of assignment, and just uses target_id. This patch sets the type of
assignment (i.e. USER_PROJECT or GROUP_PROJECT) in order to avoid wrong
deletions when domain_id == project_id.

Closes-Bug: #1440107
Change-Id: I17487db0e3f9a64868742b33be5958ceb3f8c4bc


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

Title:
  Clearing up project assignments makes assumptions that domain_id !=
  project_id

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The method delete_project_assignments() in the assignment backends
  removes all assignments for a project - although the code fails to set
  the type of assignment, and just uses target_id.  This is nearly
  always going to be fine, although technically one should also specify
  the type of the assignment in the delete (e.g. USER_PROJECT or
  GROUP_PROJECT).

  
https://github.com/openstack/keystone/blob/b819cea41f6cdf34a0bfc18db34188387f07d982/keystone/assignment/backends/sql.py#L368

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1440107/+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 1434172] Re: security group create errors without description

We've updated the Nova docs that this is no longer optional.

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

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

Title:
  security group create errors without description

Status in OpenStack Compute (nova):
  Won't Fix
Status in python-novaclient:
  In Progress
Status in python-openstackclient:
  Fix Released

Bug description:
  security group create returns an error without --description supplied.
  This appears to be the server rejecting the request so we should set a
  default value rather than sending None.

    $ openstack security group create qaz
    ERROR: openstack Security group description is not a string or unicode 
(HTTP 400) (Request-ID: req-dee03de3-893a-4d58-bc3d-de87d09c3fb8)

  Sent body:

    {"security_group": {"name": "qaz2", "description": null}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1434172/+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 1545202] [NEW] Domain info is not shown in federated token validation response

2016-02-12 Thread Sam Leong

Public bug reported:

When validating a federated token, the group id info shows in the
response but the domain info does not show, only shows 'Federated' for
both domain id and domain name.

HTTP/1.1 200 OK
Date: Fri, 12 Feb 2016 21:24:16 GMT
Server: Apache/2.4.10 (Debian)
X-Subject-Token: b6c115ce0aed425baf3e8ed104da945d
Vary: X-Auth-Token
x-openstack-request-id: req-6c1a9a92-f3f9-48a2-8767-61001c77cadd
Content-Length: 419
Content-Type: application/json

{"token": {"methods": ["saml2"], "expires_at":
"2016-02-13T01:20:20.037092Z", "extras": {}, "user": {"OS-FEDERATION":
{"identity_provider": {"id": "ks_fed1_idp"}, "protocol": {"id":
"saml2"}, "groups": [{"id": "357f50fed4cc4f00804cd8da821426ea"}]},
"domain": {"id": "Federated", "name": "Federated"}, "id": "admin",
"name": "admin"}, "audit_ids": ["gCNZNyOAQfughh3tPMyEhQ"], "issued_at":
"2016-02-12T21:20:20.037127Z"}}

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

Title:
  Domain info is not shown in federated token validation response

Status in OpenStack Identity (keystone):
  New

Bug description:
  When validating a federated token, the group id info shows in the
  response but the domain info does not show, only shows 'Federated' for
  both domain id and domain name.

  HTTP/1.1 200 OK
  Date: Fri, 12 Feb 2016 21:24:16 GMT
  Server: Apache/2.4.10 (Debian)
  X-Subject-Token: b6c115ce0aed425baf3e8ed104da945d
  Vary: X-Auth-Token
  x-openstack-request-id: req-6c1a9a92-f3f9-48a2-8767-61001c77cadd
  Content-Length: 419
  Content-Type: application/json

  {"token": {"methods": ["saml2"], "expires_at":
  "2016-02-13T01:20:20.037092Z", "extras": {}, "user": {"OS-FEDERATION":
  {"identity_provider": {"id": "ks_fed1_idp"}, "protocol": {"id":
  "saml2"}, "groups": [{"id": "357f50fed4cc4f00804cd8da821426ea"}]},
  "domain": {"id": "Federated", "name": "Federated"}, "id": "admin",
  "name": "admin"}, "audit_ids": ["gCNZNyOAQfughh3tPMyEhQ"],
  "issued_at": "2016-02-12T21:20:20.037127Z"}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1545202/+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 1481425] Re: flavor-create form should include -rxtx-factor option