date:20160429

[Yahoo-eng-team] [Bug 1569681] Re: It's hard to find the resource_type in Orchestration panel

2016-04-29 Thread OpenStack Infra

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

commit 2b80998f9a4fc7799014d3d358664e58baeb626a
Author: Kenji Ishii 
Date:   Wed Apr 13 05:24:39 2016 +

Add filter function on resource type table

Resource Types panel in Orchestration panel group has a resources
type table. This table does not have a filter function even though
the number of colums is over 90.
This patch add a filter function to this table.

Change-Id: I66e950b1acc3d9ea70fff5545cc0cc7fce6fa500
Closes-bug: #1569681


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

Title:
  It's hard to find the resource_type in Orchestration panel

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Resource Type panel In Orchestration panel group has a resources type table.
  At the moment, the number of rows are over 90. However, this table doesn't 
have a filter function, so it's hard to find the resource type which users 
want. 
  Same as table in other panels, filter function should be added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1569681/+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 1570748] Re: Bug: resize instance after edit flavor with horizon

2016-04-29 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/311145
Committed: 
https://git.openstack.org/cgit/openstack/nova-powervm/commit/?id=e72a505860b2f7ce2dd4a492f65d426f8b091e1f
Submitter: Jenkins
Branch:master

commit e72a505860b2f7ce2dd4a492f65d426f8b091e1f
Author: Drew Thorstensen 
Date:   Fri Apr 29 10:12:33 2016 -0500

Fix revert migration if flavor deleted

After an instance is created, the flavor could be deleted.  But
operations still need to be able to occur against the VM when that
occurs.  A new test in Tempest showed that we had been using the
incorrect (and potentially deleted) flavor when a resize/migration was
reverting.

This change updates the code to use the flavor that is stored on the
instance itself.

Change-Id: I16254d8eb74a724e3e0a538f47259e9627c4233a
Closes-Bug: 1570748


** Changed in: nova-powervm
   Status: New => Fix Released

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

Title:
  Bug: resize instance after edit flavor with horizon

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Fix Committed
Status in OpenStack Compute (nova) liberty series:
  Fix Committed
Status in OpenStack Compute (nova) mitaka series:
  Fix Committed
Status in nova-powervm:
  Fix Released
Status in tempest:
  Fix Released

Bug description:
  Error occured when resize instance after edit flavor with horizon (and
  also delete flavor used by instance)

  Reproduce step :

  1. create flavor A
  2. boot instance using flavor A
  3. edit flavor with horizon (or delete flavor A)
  -> the result is same to edit or to delelet flavor because edit flavor 
means delete/recreate flavor)
  4. resize or migrate instance
  5. Error occured

  Log : 
  nova-compute.log
 File "/opt/openstack/src/nova/nova/conductor/manager.py", line 422, in 
_object_dispatch
   return getattr(target, method)(*args, **kwargs)

 File "/opt/openstack/src/nova/nova/objects/base.py", line 163, in wrapper
   result = fn(cls, context, *args, **kwargs)

 File "/opt/openstack/src/nova/nova/objects/flavor.py", line 132, in 
get_by_id
   db_flavor = db.flavor_get(context, id)

 File "/opt/openstack/src/nova/nova/db/api.py", line 1479, in flavor_get
   return IMPL.flavor_get(context, id)

 File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 233, in 
wrapper
   return f(*args, **kwargs)

 File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 4732, in 
flavor_get
   raise exception.FlavorNotFound(flavor_id=id)

   FlavorNotFound: Flavor 7 could not be found.

  
  This Error is occured because of below code:
  /opt/openstack/src/nova/nova/compute/manager.py

  def resize_instance(self, context, instance, image,
  reservations, migration, instance_type,
  clean_shutdown=True):
  
  if (not instance_type or
  not isinstance(instance_type, objects.Flavor)):
  instance_type = objects.Flavor.get_by_id(
  context, migration['new_instance_type_id'])
  

  I think that deleted flavor should be taken when resize instance. 
  I tested this in stable/kilo, but I think stable/liberty and stable/mitaka 
has same bug because source code is not changed.

  thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1570748/+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 1325952] Re: tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON tearDownClass FAILED

2016-04-29 Thread Armando Migliaccio

** No longer affects: neutron

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

Title:
  tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON
  tearDownClass FAILED

Status in tempest:
  Invalid

Bug description:
  2014-06-03 10:45:31.772 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_create_update_delete_firewall_policy
 [0.138860s] ... ok
  2014-06-03 10:45:31.862 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_create_update_delete_firewall_rule
 [0.089827s] ... ok
  2014-06-03 10:45:31.879 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_list_firewall_policies
 [0.016316s] ... ok
  2014-06-03 10:45:31.893 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_list_firewall_rules
 [0.013835s] ... ok
  2014-06-03 10:45:31.914 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_show_firewall_policy
 [0.019647s] ... ok
  2014-06-03 10:45:31.930 | {0} 
tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON.test_show_firewall_rule
 [0.016054s] ... ok
  2014-06-03 10:45:31.956 | {0} tearDownClass 
(tempest.api.network.test_fwaas_extensions.FWaaSExtensionTestJSON) [0.00s] 
... FAILED
  2014-06-03 10:45:31.956 | 
  2014-06-03 10:45:31.956 | Captured traceback:
  2014-06-03 10:45:31.956 | ~~~
  2014-06-03 10:45:31.956 | Traceback (most recent call last):
  2014-06-03 10:45:31.956 |   File "tempest/api/network/base.py", line 89, 
in tearDownClass
  2014-06-03 10:45:31.956 | 
cls.client.delete_firewall_policy(fw_policy['id'])
  2014-06-03 10:45:31.956 |   File 
"tempest/services/network/network_client_base.py", line 118, in _delete
  2014-06-03 10:45:31.956 | return self.delete(uri)
  2014-06-03 10:45:31.956 |   File 
"tempest/services/network/network_client_base.py", line 78, in delete
  2014-06-03 10:45:31.956 | return self.rest_client.delete(uri, headers)
  2014-06-03 10:45:31.957 |   File "tempest/common/rest_client.py", line 
215, in delete
  2014-06-03 10:45:31.957 | return self.request('DELETE', url, 
extra_headers, headers, body)
  2014-06-03 10:45:31.957 |   File "tempest/common/rest_client.py", line 
419, in request
  2014-06-03 10:45:31.957 | resp, resp_body)
  2014-06-03 10:45:31.957 |   File "tempest/common/rest_client.py", line 
473, in _error_checker
  2014-06-03 10:45:31.957 | raise exceptions.Conflict(resp_body)
  2014-06-03 10:45:31.957 | Conflict: An object with that identifier 
already exists
  2014-06-03 10:45:31.957 | Details: {u'message': u'Firewall Policy 
e948ad84-9c97-4769-846d-a09ea6e034c8 is being used.', u'type': 
u'FirewallPolicyInUse', u'detail': u''}

To manage notifications about this bug go to:
https://bugs.launchpad.net/tempest/+bug/1325952/+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 1492142] Re: FWaaS: FIP namespace created after/before Firewall creation doesn't contain FW rules

2016-04-29 Thread Armando Migliaccio

This could be fixed for backporting purposes, but fixing it in master
does not seem worthwhile as the FWaaS v2 API means the implementation
must be revised. It's now over a month since the last expiration. At
some point we must admit when too late is too late.

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

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

Title:
  FWaaS: FIP namespace created after/before Firewall creation doesn't
  contain FW rules

Status in neutron:
  Won't Fix

Bug description:
  L3 agent is set to "dvr_snat" mode.

  Steps to reproduce:
  1) Create security group rules
  2) Boot nova instance
  3) Create floating ip on public network and associate it to the nova instance
  4) Create firewall rules
  5) Create firewall policy with the above rules
  6) Create firewall with the above policy

  Expected Result:
  Both SNAT and FIP namespaces should contain the FW rules

  Observed Result:
  Only SNAT namespace contains the FW rules while the FIP namespace doesn't

  Impact:
  Due to this, the packets transferred over the external network that are 
destined to this instance could bypass the firewall rules using the floating ip 
of the instance.

  Following are the commands and their output:

  demofw@devstack:~/devstack$ neutron router-show router1
  
+---++
  | Field | Value   


   |
  
+---++
  | admin_state_up| True


   |
  | external_gateway_info | {"network_id": 
"b162e6a0-ab7b-4a2f-8239-e06f1e13ccb5", "enable_snat": true, 
"external_fixed_ips": [{"subnet_id": "4743e969-7a36-427e-86e0-908c767c9d12", 
"ip_address": "172.24.4.2"}, {"subnet_id": 
"8f59a96f-2a06-4973-bbf9-40ae143ec1df", "ip_address": "2001:db8::3"}]} |
  | id| fb2f3983-7a9d-4bc7-812c-20f0c182ef1a


   |
  | name  | router1 


   |
  | routes| 


   |
  | status| ACTIVE  


   |
  | tenant_id | b8e6948ab2394672b2fa603c75d02eda


   |
  
+---++

  
  demofw@devstack:~/devstack$ neutron floatingip-create public --port-id 
0d283e44-96e9-4f98-9db1-5f464f8163b8
  Created a new floatingip:
  +-+--+
  | Field   | Value|

[Yahoo-eng-team] [Bug 1554762] Re: Neutron fwaas install doc needs to replace the wiki page

2016-04-29 Thread Armando Migliaccio

We'll aggressively kill all Neutron related wiki pages that are no
longer relevant.

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

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

Title:
  Neutron fwaas install doc needs to replace the wiki page

Status in neutron:
  Won't Fix

Bug description:
  It's outdated and refers to DevStack.

  
  https://wiki.openstack.org/wiki/Neutron/FWaaS/HowToInstall

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1554762/+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 1498603] Re: Cannot Support multiple firewall per router

2016-04-29 Thread Armando Migliaccio

The model has changed with the v2 proposal

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

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

Title:
  Cannot Support multiple firewall per router

Status in neutron:
  Won't Fix

Bug description:
   Cannot create  multiple firewall per router.

  While creating getting below message

  stack@hdp-001:~$ neutron firewall-create policy-fw2 --name user-fw2
  Router(s) [u'58d36628-e7a2-472d-b38d-0015117b519d'] provided already 
associated with other Firewall(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1498603/+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 1503595] Re: Firewall remain in active state even after deleting router associated with firewall

2016-04-29 Thread Armando Migliaccio

Do we still expect to fix bugs to an implementation that is meant to be
supplanted?

** Changed in: neutron
   Status: Incomplete => Won't Fix

** Changed in: neutron
 Assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) => (unassigned)

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

Title:
  Firewall remain in active state even after deleting router associated
  with firewall

Status in neutron:
  Won't Fix

Bug description:
  Steps to Reproduce:
  ==
  1.  Create a  network,subnet,router and add router interface
  2. Create firewall rule
  3. Create firewall Policy with the above firewall rule
  4. Create firewall  with above policy 
  And make above route set to the firewall.

  5. Then delete the  router attached to the firewall and check the
  status of the firewall

  Issue :
Firewall remain in ACTIVE state even though  router id field is blank while 
getting the details of the firewall
  {code}
  stack@stevens-creek:~/firewall$ neutron firewall-list
  
+--+-+--+
  | id   | name| firewall_policy_id 
  |
  
+--+-+--+
  | 71746ed4-4e12-48c6-8db5-31543276058e | user-fw | 
320f68ea-4947-484d-af32-5ead4f368348 |
  
+--+-+--+
  stack@stevens-creek:~/firewall$ neutron firewall-show user-fw
  ++--+
  | Field  | Value|
  ++--+
  | admin_state_up | True |
  | description|  |
  | firewall_policy_id | 320f68ea-4947-484d-af32-5ead4f368348 |
  | id | 71746ed4-4e12-48c6-8db5-31543276058e |
  | name   | user-fw  |
  | router_ids |  |
  | status | ACTIVE   |
  | tenant_id  | 84dc1f66b8b34fb2a48e2dce7031f279 |
  ++--+
  stack@stevens-creek:~/firewall$
  {code}

  Expected :

Firewall  state should change to either pending or error state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1503595/+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 1567801] Re: incorrect status codes from pecan shim controller

2016-04-29 Thread OpenStack Infra

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

commit 2e19107fe2b7740d750aa39d28e2377a63c9dcfe
Author: Kevin Benton 
Date:   Mon Mar 14 08:00:46 2016 -0700

Pecan: Fix Shim status codes

Fix the status codes returned by the shim controller
to match the expectations of the API tests.

Closes-bug: #1567801
Change-Id: Ibfede6b6bc4ba24cf2b9e4ff5540c2249695252f


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

Title:
  incorrect status codes from pecan shim controller

Status in neutron:
  Fix Released

Bug description:
  found in API test from pecan job:

  Traceback (most recent call last):
File "neutron/tests/api/admin/test_l3_agent_scheduler.py", line 93, in 
test_add_list_remove_router_on_l3_agent
  self.router['id'])
File "neutron/tests/tempest/services/network/json/network_client.py", line 
555, in add_router_to_l3_agent
  self.expected_success(201, resp.status)
File 
"/opt/stack/new/neutron/.tox/api/local/lib/python2.7/site-packages/tempest/lib/common/rest_client.py",
 line 243, in expected_success
  raise exceptions.InvalidHttpSuccessCode(details)
  tempest.lib.exceptions.InvalidHttpSuccessCode: The success code is different 
than the expected one
  Details: Unexpected http success status code 200,
   The expected status code is 201

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1567801/+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 1513353] Re: VPNaaS: leftid should be configurable

2016-04-29 Thread Armando Migliaccio

The fix proposed here left much to be desired. A release note is
missing, and the API extension was changed in place without taking into
account that a user is unable to discover whether or not a system does
support this capability. This should be reopened.

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

** Changed in: neutron
Milestone: None => newton-1

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

Title:
  VPNaaS: leftid should be configurable

Status in neutron:
  In Progress

Bug description:
  Currently, both left & leftid are filled with external_ip automatically. But 
sometimes, user may want to specify the leftid as they desired, such as an 
email address.
  It would be better if this can be supported.

  Pre-conditions: None

  Step-by-step reproduction steps:
  1) create an ipsec connection from dashboard or CLI, there is no leftid 
option.

  Version:
  Stable Kilo/CentOS7/RDO

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1513353/+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 1576888] Re: Support local_id configuration

2016-04-29 Thread Armando Migliaccio

This looks like a new feature to me and it needs a user as well as API
documentation (see commit message).

** Also affects: openstack-manuals
   Importance: Undecided
   Status: New

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

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

Title:
  Support local_id configuration

Status in neutron:
  Confirmed
Status in openstack-manuals:
  Confirmed

Bug description:
  https://review.openstack.org/310676
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.

  commit 7cf4ef682f83fc08484011454f62c27882064dff
  Author: nick.zhuyj 
  Date:   Wed Apr 27 03:36:02 2016 -0500

  Support local_id configuration
  
  In some case, we want to specify the local id instead of use the
  external ip. For example, the router is behind NAT, and we don't
  want to expose this IP to peer. This patch will make local_id
  configurable. Most often, local id would be domain name, email
  address etc. But if local id is not configured then external ip
  will still be used as the leftid.
  
  Note: this change is DocImpact & APIImpact
  
  Change-Id: I2433d72ba22ce410cbfafb7b8bfb16f51eefdfc1
  Closes-Bug: #1513353

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576888/+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 1576106] Re: File constants.py miss VETH_DEVICE_PREFIX and SNAT_INT_DEV_PREFIX parameters

2016-04-29 Thread Armando Migliaccio

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

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

Title:
  File constants.py miss VETH_DEVICE_PREFIX and SNAT_INT_DEV_PREFIX
  parameters

Status in neutron:
  Invalid

Bug description:
  During installing Openstack via Devstack and running "neutron-db-
  manage revision" command, it is always fail [1]. I found to miss two
  parameter: VETH_DEVICE_PREFIX and SNAT_INT_DEV_PREFIX in file
  constants.py [2]. They have to be added.

  [1] http://paste.openstack.org/show/495635/
  [2] 
https://github.com/openstack/neutron/blob/master/neutron/common/constants.py#L95

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576106/+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 1567830] Re: “10 $digest() iterations reached” Error occur in ng-swift

2016-04-29 Thread OpenStack Infra

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

commit ea6d708f06645d4fb3d78676a0a20d36066ee957
Author: Richard Jones 
Date:   Wed Apr 20 13:53:31 2016 +1000

Remove broken "link" type action

This change also requires switching the Swift UI over
to using a regular button instead of the link.

Change-Id: I41fbed21614c3ea81aed0ad2bfa98ea31980a01b
Closes-Bug: 1572386
Closes-Bug: 1567830


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

Title:
  “10 $digest() iterations reached” Error occur in ng-swift

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  In latest horizon, when I open the container page or I select a container, 
error occurred.
  As a result, I can't do any operation.

  "Error: [$rootScope:infdig] 10 $digest() iterations reached. Aborting!
  Watchers fired in the last 5 iterations: []
  http://errors.angularjs.org/1.3.7/$rootScope/infdig?p0=10=%5B%5D
  
minErr/<@http://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:699:8
  
$RootScopeProvider/this.$gethttp://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:1363:242
  
$RootScopeProvider/this.$gethttp://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:1365:244
  
done@http://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:1142:112
  
completeRequest@http://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:1159:20
  
requestLoaded@http://10.58.79.172/dashboard/static/dashboard/js/7fd3f7d69c71.js:1153:1
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1567830/+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 1572386] Re: Action list "link" actions broken after patch #295605

2016-04-29 Thread OpenStack Infra

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

commit ea6d708f06645d4fb3d78676a0a20d36066ee957
Author: Richard Jones 
Date:   Wed Apr 20 13:53:31 2016 +1000

Remove broken "link" type action

This change also requires switching the Swift UI over
to using a regular button instead of the link.

Change-Id: I41fbed21614c3ea81aed0ad2bfa98ea31980a01b
Closes-Bug: 1572386
Closes-Bug: 1567830


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

Title:
  Action list "link" actions broken after patch #295605

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The fix for bug 1560303 in https://review.openstack.org/#/c/295605
  broke when any "link" type action was included in the actions list.
  This broke in the new Swift UI.

  The fix is either to revert patch 295605, fix the link actions or to
  change the Swift UI to not use link actions.

  Altering the implementation of link actions is unlikely because to do
  so would require significant changes across the action-list
  implementation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1572386/+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 1576046] Re: test_create_router_port_and_fail_create_postcommit makes networking-odl py27 and py34 fail

2016-04-29 Thread Armando Migliaccio

It looks like this seems resolved as this just merged:

https://review.openstack.org/#/c/300898/

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

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

Title:
  test_create_router_port_and_fail_create_postcommit  makes networking-
  odl py27 and py34 fail

Status in neutron:
  Invalid

Bug description:
  New test case introduced to neutron lately by
   
https://github.com/openstack/neutron/commit/cc3ba38641e5a414ec4408b13ecb7bd80ea343ff
   Caused networking-odl py27/py34 gate checking failure, as shown in  
  https://review.openstack.org/#/c/309847/

  The first hunch is the mock for  create_port_postcommit of the test
  driver does not take effect since networking-odl over-writes
  self._mechanism_drivers to ['opendaylight']

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576046/+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 1576888] [NEW] Support local_id configuration

2016-04-29 Thread OpenStack Infra

Public bug reported:

https://review.openstack.org/310676
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.

commit 7cf4ef682f83fc08484011454f62c27882064dff
Author: nick.zhuyj 
Date:   Wed Apr 27 03:36:02 2016 -0500

Support local_id configuration

In some case, we want to specify the local id instead of use the
external ip. For example, the router is behind NAT, and we don't
want to expose this IP to peer. This patch will make local_id
configurable. Most often, local id would be domain name, email
address etc. But if local id is not configured then external ip
will still be used as the leftid.

Note: this change is DocImpact & APIImpact

Change-Id: I2433d72ba22ce410cbfafb7b8bfb16f51eefdfc1
Closes-Bug: #1513353

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc neutron-vpnaas

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

Title:
  Support local_id configuration

Status in neutron:
  New

Bug description:
  https://review.openstack.org/310676
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.

  commit 7cf4ef682f83fc08484011454f62c27882064dff
  Author: nick.zhuyj 
  Date:   Wed Apr 27 03:36:02 2016 -0500

  Support local_id configuration
  
  In some case, we want to specify the local id instead of use the
  external ip. For example, the router is behind NAT, and we don't
  want to expose this IP to peer. This patch will make local_id
  configurable. Most often, local id would be domain name, email
  address etc. But if local id is not configured then external ip
  will still be used as the leftid.
  
  Note: this change is DocImpact & APIImpact
  
  Change-Id: I2433d72ba22ce410cbfafb7b8bfb16f51eefdfc1
  Closes-Bug: #1513353

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576888/+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 1450294] Re: Enable password support for vnc session

2016-04-29 Thread Markus Zoeller (markus_z)

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on.

** Tags removed: low-hanging-fruit

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

Title:
  Enable password support for vnc session

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  qemu supports that password based authentication is used for client 
connections by adding password option for -vnc as below [1]. 
  -vnc 0.0.0.0:1,password -k en-us 
  qemu xml configuration file provides a VNC password in clear text. 
   

  but openstack doesn't support to configure vpn password, see the following 
codes: 
  if ((CONF.vnc_enabled and 
  virt_type not in ('lxc', 'uml'))): 
  graphics = vconfig.LibvirtConfigGuestGraphics() 
  graphics.type = "vnc" 
  graphics.keymap = CONF.vnc_keymap 
  graphics.listen = CONF.vncserver_listen 
  guest.add_device(graphics) 
  add_video_driver = True 

  
  [1], http://www.cyberciti.biz/faq/linux-kvm-vnc-for-guest-machine/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1450294/+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 1576869] [NEW] Attach Interface form error

2016-04-29 Thread Ankur

Public bug reported:

Horizon->Project->Instances

When modal pops up, if you try submitting without selecting a network it errors 
(as it should).
Modal stays open.
When you go back and select a proper network to attach. Form errors out (it 
shouldn't)

Error message:
Danger: There was an error submitting the form. Please try again.

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

Title:
  Attach Interface form error

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Horizon->Project->Instances

  When modal pops up, if you try submitting without selecting a network it 
errors (as it should).
  Modal stays open.
  When you go back and select a proper network to attach. Form errors out (it 
shouldn't)

  Error message:
  Danger: There was an error submitting the form. Please try again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1576869/+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 1410003] Re: Performance Issue on Nova API about Nova Quota Usage

2016-04-29 Thread Markus Zoeller (markus_z)

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on.

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

Title:
Performance Issue on Nova API about Nova Quota Usage

Status in OpenStack Compute (nova):
Opinion

Bug description:
We have a requirement to collect quota usage information at project level
with admin role account. We noticed that the only api we can work with
currently is to get them one by one:
Request: GET /v2/{tenant_id}/limits/?tenant_id={tenant_id}
Refer to:

http://docs.openstack.org/api/openstack-compute/2/content/GET_os-used-limits-for-admins-v2_getCustomerLimits__v2__tenant_id__limits__tenant_id__ext-compute_limits_admins.html

In production env, we maintained 1K projects at least. So with this
API, we have to get the summary with 1K http requests.(O(n), n is the
number of projects).

This would cause low performance if we check the quota usages
frequently. I would hope there's an API similar to the way we did for
instances summary(/v2/{tenant_id}/servers/detail?all_tenant=True)
which is use a "all_tenants" parameter to return the summary list we
want.

That would totally solve the performance issue we met(O(n) -> O(1)). I just
wrote a prototype to get this down and hope it would be helpful to describe the
issue. Code link is here:
https://github.com/henryzzq/nova/compare/stable/icehouse?expand=1

Also attached a design doc about this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1410003/+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 1576840] [NEW] fullstack OVS agent in native openflow mode sometimes fails to bind socket

2016-04-29 Thread Assaf Muller

Public bug reported:

Plenty of hits in the last few days, currently the top issue affecting
fullstack stability.

Example paste:
http://paste.openstack.org/show/495797/

Example logs:
http://logs.openstack.org/18/276018/21/check/gate-neutron-dsvm-fullstack/c0761dc/logs/TestOvsConnectivitySameNetwork.test_connectivity_VLANs,openflow-native_ovsdb-native_/

** Affects: neutron
 Importance: High
 Status: Confirmed


** Tags: fullstack

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

Title:
  fullstack OVS agent in native openflow mode sometimes fails to bind
  socket

Status in neutron:
  Confirmed

Bug description:
  Plenty of hits in the last few days, currently the top issue affecting
  fullstack stability.

  Example paste:
  http://paste.openstack.org/show/495797/

  Example logs:
  
http://logs.openstack.org/18/276018/21/check/gate-neutron-dsvm-fullstack/c0761dc/logs/TestOvsConnectivitySameNetwork.test_connectivity_VLANs,openflow-native_ovsdb-native_/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576840/+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 1489059] Re: "db type could not be determined" running py34

2016-04-29 Thread Christophe Sauthier

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

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Bareon:
  Fix Released
Status in Cinder:
  Fix Released
Status in cloudkitty:
  Fix Released
Status in Fuel for OpenStack:
  In Progress
Status in Fuel for OpenStack mitaka series:
  Won't Fix
Status in Fuel for OpenStack newton series:
  In Progress
Status in Glance:
  Fix Released
Status in hacking:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in kolla:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in networking-ofagent:
  Fix Released
Status in neutron:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-muranoclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in python-swiftclient:
  In Progress
Status in Rally:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  Fix Released
Status in senlin:
  Fix Released
Status in tap-as-a-service:
  Fix Released
Status in tempest:
  Fix Released
Status in zaqar:
  Fix Released
Status in python-ironicclient package in Ubuntu:
  Fix Committed

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1400310] Re: Booting from an image and creating a volume does not enable caller to pass volume_type

2016-04-29 Thread Matt Riedemann

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

Title:
  Booting from an image and creating a volume does not enable caller to
  pass volume_type

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  The creation of a volume would not enable the caller to pass the
  volume_type_id. This will default to default value set in cinder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1400310/+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 1575055] Re: check_instance_id() error on reboots when using config-drive

2016-04-29 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init - 0.7.7~bzr1215-0ubuntu1

---
cloud-init (0.7.7~bzr1215-0ubuntu1) yakkety; urgency=medium

  * debian/new-upstream-snapshot: minor change supporting revision
passed in as an argument.
  * New upstream snapshot.
- Paths: fix instance path if datasource's id has a '/'. (LP: #1575938)
- Config Drive: fix check_instance_id signature.  (LP: #1575055)
- cloudstack: Only use DHCPv4 lease files as a datasource (LP: #1576273)

 -- Scott Moser   Fri, 29 Apr 2016 12:37:48 -0400

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  check_instance_id() error on reboots when using config-drive

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

Bug description:
  Problem Description
  =
  When using a config-drive to provide meta-data to cloud-init on ubuntu (for 
Linux guest running in KVM for z Systems) we get a check_instance_id() error 
whenever we soft reboot after the (successful) initial boot.

  The error shows:

  [5.283203] cloud-init[1637]: Cloud-init v. 0.7.7 running 'init-local' at 
Sat, 23 Apr 2016 00:50:58 +. Up 5.25 seconds.
  [5.283368] cloud-init[1637]: 2016-04-22 20:50:58,839 - util.py[WARNING]: 
failed of stage init-local
  [5.286659] cloud-init[1637]: failed run of stage init-local
  [5.286770] cloud-init[1637]: 

  [5.286849] cloud-init[1637]: Traceback (most recent call last):
  [5.286924] cloud-init[1637]:   File "/usr/bin/cloud-init", line 520, in 
status_wrapper
  [5.286998] cloud-init[1637]: ret = functor(name, args)
  [5.287079] cloud-init[1637]:   File "/usr/bin/cloud-init", line 250, in 
main_init
  [5.287152] cloud-init[1637]: init.fetch(existing=existing)
  [5.287225] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 322, in fetch
  [5.287298] cloud-init[1637]: return 
self._get_data_source(existing=existing)
  [5.287371] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 229, in 
_get_data_source
  [5.287445] cloud-init[1637]: ds.check_instance_id(self.cfg)):
  [5.287518] cloud-init[1637]: TypeError: check_instance_id() takes 1 
positional argument but 2 were given
  [5.287592] cloud-init[1637]: 

  [FAILED] Failed to start Initial cloud-init job (pre-networking).

  
  The failure of the init-local pre-networking does seem to lead to a boot up 
delay as cloud-init tries to search for networking outside of the already saved 
networking data.   

  Otherwise the error is purely cosmetic as later init modules find (or
  let existing IP configuration take over) and bring up the correct
  interfaces.

  The original problem was found outside of openstack with stand-alone
  cloud-config iso images.  But have been able to reproduce the problem
  within an openstack ICM environment.

  Team has had some success getting around the problem by patching the
  check_instance_id function in /usr/lib/python3/dist-
  packages/cloudinit/sources/DataSourceConfigDrive.py so that it
  accepted an extra argument, ex:

  ubuntu@markvercd:~$ sudo cat check_instance_id.patch 
  --- /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py 
2016-04-06 15:29:59.0 +
  +++ 
/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py.new   
  2016-04-11 22:53:47.799867139 +
  @@ -155,7 +155,7 @@
   
   return True
   
  -def check_instance_id(self):
  +def check_instance_id(self,somecfg):
   # quickly (local check only) if self.instance_id is still valid
   return 
sources.instance_id_matches_system_uuid(self.get_instance_id())
   
  ubuntu@markvercd:~$ 

  ---uname output---
  Linux k6mpathcl.pokprv.stglabs.ibm.com 4.4.0-21-generic #37-Ubuntu SMP Mon 
Apr 18 18:31:26 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest on a z13 (2827-732) LPAR 

  Steps to Reproduce
  =
   1) set up ubuntu guest image with cloud-init
  2) pass in iso image with cloud-config data in cdrom device
  3) boot up successfully with cloud-config data
  4) attempt a soft reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1575055/+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 1575938] Re: Instance path in / if instance-id starts with '/'

2016-04-29 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init - 0.7.7~bzr1215-0ubuntu1

---
cloud-init (0.7.7~bzr1215-0ubuntu1) yakkety; urgency=medium

  * debian/new-upstream-snapshot: minor change supporting revision
passed in as an argument.
  * New upstream snapshot.
- Paths: fix instance path if datasource's id has a '/'. (LP: #1575938)
- Config Drive: fix check_instance_id signature.  (LP: #1575055)
- cloudstack: Only use DHCPv4 lease files as a datasource (LP: #1576273)

 -- Scott Moser   Fri, 29 Apr 2016 12:37:48 -0400

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Instance path in / if instance-id starts with '/'

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  A cloud using the Ec2 datasource has an instance-id metadata value in
  the form:

  /Compute-$TENANT/$CLOUDUSERNAME/$UUID

  The leading '/' causes /var/lib/cloud/instance to link to
  /Compute-$TENANT/$CLOUDUSERNAME/$UUID rather than
  /var/lib/cloud/instances/Compute-$TENANT/$CLOUDUSERNAME/$UUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1575938/+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 1576273] Re: CloudStack datasource fails to find DHCP lease if IPv6 present

2016-04-29 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init - 0.7.7~bzr1215-0ubuntu1

---
cloud-init (0.7.7~bzr1215-0ubuntu1) yakkety; urgency=medium

  * debian/new-upstream-snapshot: minor change supporting revision
passed in as an argument.
  * New upstream snapshot.
- Paths: fix instance path if datasource's id has a '/'. (LP: #1575938)
- Config Drive: fix check_instance_id signature.  (LP: #1575055)
- cloudstack: Only use DHCPv4 lease files as a datasource (LP: #1576273)

 -- Scott Moser   Fri, 29 Apr 2016 12:37:48 -0400

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

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

Title:
  CloudStack datasource fails to find DHCP lease if IPv6 present

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  The CloudStack data source looks in /var/lib/dhcp for DHCP lease files
  and compares the timestamps.

  If you have a dhclient.leases and dhclient6.leases file present it
  will look in the dhclient6.leases file for a DHCP server to connect
  to.

  The fix for this is rather simple, change a if-statement so that it
  checks if the leases file starts with 'dhclient.'

  if file_name.startswith("dhclient.") and \
 (file_name.endswith(".lease") or file_name.endswith(".leases")):

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576273/+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 1561550] Re: Untranslated strings found in Launch Instance window

2016-04-29 Thread OpenStack Infra

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

commit fdf0bf6f186f056fea6ed5761616c40463a2e269
Author: Richard Jones 
Date:   Thu Apr 7 14:28:05 2016 +1000

Fix babel msgids to include tag attributes and entities

The messages for translation were omitting the attributes in
tags and HTML entities embedded in the translation strings,
thus they no longer matched the original HTML.

Additionally, HTML entities are mostly (but not always) decoded
by the browser before angular-gettext sees them, so we have to
emulate this behaviour in our babel extractor so the message
ids match.

Change-Id: Ie6ae0776a2c0d7db589b34a9e7676508178a473d
Closes-Bug: 1561550
Closes-Bug: 1561738
Closes-Bug: 1561761


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

Title:
  Untranslated strings found in Launch Instance window

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Project > Instances > Launch Instance > Details

  Strings "Instance Name" and "Count" are not localized in the UI.

  DRF Added: also "Configuration Drive" on the Configuration step is not
  localized.

  According to Motoki-san (amotoki), those strings are not included in
  pot files under the horizon project, despite they are labled with
  "translate" in the directives and should be considered as
  translatable. It could be due to the tool's bug which inserts
  linebreaks, possibly preventing the strings to be extracted.

  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow
  /launch-instance/details/details.html#L9

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1561550/+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 1561761] Re: Unlocalized text shown in Create Container window

2016-04-29 Thread OpenStack Infra

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

commit fdf0bf6f186f056fea6ed5761616c40463a2e269
Author: Richard Jones 
Date:   Thu Apr 7 14:28:05 2016 +1000

Fix babel msgids to include tag attributes and entities

The messages for translation were omitting the attributes in
tags and HTML entities embedded in the translation strings,
thus they no longer matched the original HTML.

Additionally, HTML entities are mostly (but not always) decoded
by the browser before angular-gettext sees them, so we have to
emulate this behaviour in our babel extractor so the message
ids match.

Change-Id: Ie6ae0776a2c0d7db589b34a9e7676508178a473d
Closes-Bug: 1561550
Closes-Bug: 1561738
Closes-Bug: 1561761


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

Title:
  Unlocalized text shown in Create Container window

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Project > Object Store > Containers > Create Container

  The following text appears unlocalized.
  It exists in pot files, and already translated in zanata, but not shown 
localized in Horizon.

  
  File: openstack_dashboard/locale/django and 
openstack_dashboard/locale/djangojs

  Source text: A container is a storage compartment for your data and
  provides a way for you to organize your data. You can think of a
  container as a folder in Windows  or a directory in UNIX .
  The primary difference between a container and these other file system
  concepts is that containers cannot be nested. You can, however, create
  an unlimited number of containers within your account. Data must be
  stored in a container so you must have at least one container defined
  in your account prior to uploading data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1561761/+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 1576755] Re: Paramiko 2.0 does not work with Nova

2016-04-29 Thread git-harry

** Also affects: openstack-ansible
   Importance: Undecided
   Status: New

** No longer affects: nova

** Description changed:

  Paramiko 2.0 has just been release and breaks nova which currently has a
- requirement for 'paramiko>=1.16.0 # LGPL'
+ requirement for 'paramiko>=1.16.0 # LGPL'. Why does the upper
+ constraints file not protect against this?
  
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
[req-2e14bc90-999a-46ba-95f6-de817548014e 8fbdaf628d114c32a81f7587df939771 
be553343f9674e61b53b6b2516d4be2f - - -] Unexpected exception in API method
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/extensions.py",
 line 478, in wrapped
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/validation/__init__.py",
 line 73, in wrapper
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/validation/__init__.py",
 line 73, in wrapper
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/compute/keypairs.py",
 line 111, in create
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
self._create(req, body)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/compute/keypairs.py",
 line 132, in _create
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions context, 
user_id, name, key_type)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/exception.py", 
line 110, in wrapped
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions payload)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 220, in __exit__
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
self.force_reraise()
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 196, in force_reraise
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
six.reraise(self.type_, self.value, self.tb)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/exception.py", 
line 89, in wrapped
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
f(self, context, *args, **kw)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/compute/api.py", 
line 4046, in create_key_pair
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions user_id, 
key_type)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/compute/api.py", 
line 4068, in _generate_key_pair
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
crypto.generate_key_pair()
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/crypto.py", line 
152, in generate_key_pair
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions key = 
generate_key(bits)
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/crypto.py", line 
144, in generate_key
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions key = 
paramiko.RSAKey(vals=(rsa.e, rsa.n))
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions TypeError: 
__init__() got an unexpected keyword argument 'vals'
  2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions
  2016-04-29 14:56:58.395 2175 INFO nova.api.openstack.wsgi 
[req-2e14bc90-999a-46ba-95f6-de817548014e 8fbdaf628d114c32a81f7587df939771 
be553343f9674e61b53b6b2516d4be2f - - -] HTTP exception thrown: Unexpected API 
Error. Please report this at http://bugs.launchpad.net/nova/ and attach the 
Nova API log if possible.

-- 
You received this bug notification because you are a member of

[Yahoo-eng-team] [Bug 1576475] Re: [RFE] Add OneView ML2 driver to Neutron

2016-04-29 Thread Doug Wiegley

This looks great, but vendor mech drivers are not in the neutron project
itself, so they don't need a neutron RFE approval.

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

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

Title:
  [RFE] Add OneView ML2 driver to Neutron

Status in neutron:
  Invalid

Bug description:
  ..
   This work is licensed under a Creative Commons Attribution 3.0 Unported
   License.

   http://creativecommons.org/licenses/by/3.0/legalcode

  ===
  HP OneView Mechanism Driver for Neutron ML2 plugin
  ===

  Launchpad blueprint:

  https://blueprints.launchpad.net/neutron/+spec/oneview-ml2-mechanism-
  driver

  This blueprint specifies the ML2 mechanism driver for HP OneView integration
  to OpenStack Neutron.

  Problem description
  ===

  One of the most important initiatives in OpenStack currently focus in solve
  communication restrictions existent in Ironic. Ironic nodes have severe
  restrictions on how they can interact with other nodes because they demand a
  networking environment composed only by flat networks, not allowing tenants
  networks to be correctly isolated as already happens when using Virtual
  Machines.

  This initiative integrates Ironic and Neutron making possible the creation of
  isolated networks in Neutron to be used by Ironic Baremetal nodes. With this
  integration a better control of nodes communication is expected, improving
  system operation.

  To take advantage of this new interaction between OpenStack components, the
  integration of HP OneView and OpenStack might be extended to improve the
  management it offers considering these new functionalities and be more
  aligned to the evolution of OpenStack Platform.

  Currently, OpenStack only supports integration with OneView in operations for
  provisioning Ironic baremetal instances. Initially, Ironic/OneView driver
  only worked with 'pre-allocated' machines. It means that a Ironic node needed
  to have a Server Profile already applicated to the Server Hardware registered
  in OneView. A new version of the driver is being implemented to dynamically
  allocate Ironic nodes, avoiding that nodes already available in Ironic but not
  released in OneView could not be used by other OneView users.

  However, operations related with the OneView's communication infrastructure
  remains unsupported since there is no integration with current Openstack
  Neutron actions. This limitation restricts Openstack/OneView interaction since
  it demands all the configurations of communication infrastructure to be
  manually replicated in both sides to ensure servers correct communication.

  The mechanism driver proposed here will interact with Neutron and OneView to
  dynamically reflect networking operations made by OpenStack on OneView. With
  these operations it's possible to a OneView administrator to know what is
  happening in OpenStack System which is running in the Data Center and also
  automatizes some operations previously required to be manual.

  Proposed change
  ===

  The diagram below provides an overview of how Neutron and OneView will
  interact using the Neutron-OneView Mechanism Driver. OneView Mechanism
  Driver uses the python-oneviewclient to provide communication between
  Neutron and OneView through OneView's Rest API.

  Flows:
  ::

  +-+
  | |
  |   Neutron Server|
  |  (with ML2 plugin)  |
  | |
  |   +-+
  |   |   OneView   |  Ironic API  ++
  |   |  Mechanism  +--+ Ironic |
  |   |   Driver|  ++
  +---+--+--+
 |
   REST API  |
 |
   +-+-+
   | OneView   |
   +---+

  
  Openstack Neutron based networks and ports information is demanded by
  OneView service to manage virtual networks. In order to send this
  information from neutron service, a new ML2 mechanism driver is required to
  post the precommit data to the OneView service. The OneView mechanism
  driver updates the OneView with port and network changes from Neutron.

  The OneView mechanism driver implements the following Neutron events:

- Port create/update/delete for compute instances;
- Network create/update/delete.

  When new networks are created in Neutron, OneView might also create this
  network to allow system

[Yahoo-eng-team] [Bug 1576757] [NEW] SRIOV: ESwitchManager should handle multiple NICs per physical net

2016-04-29 Thread Oleg Bondarev

Public bug reported:

Commit 46ddaf4288a1cac44d8afc0525b4ecb3ae2186a3 made it possible to specify 
multiple NICs per network.
However ESwitchManager now stores only one EmbSwitch per physical net (the last 
one).

** Affects: neutron
 Importance: High
 Assignee: Vladimir Eremin (yottatsa)
 Status: Confirmed


** Tags: mitaka-backport-potential sriov-pci-pt

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

Title:
  SRIOV: ESwitchManager should handle multiple NICs per physical net

Status in neutron:
  Confirmed

Bug description:
  Commit 46ddaf4288a1cac44d8afc0525b4ecb3ae2186a3 made it possible to specify 
multiple NICs per network.
  However ESwitchManager now stores only one EmbSwitch per physical net (the 
last one).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1576757/+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 1558626] Re: [sriov] physical_device_mappings allows only one physnet for per nic

2016-04-29 Thread Oleg Bondarev

New bug was filed for handling multiple nics per phys net:
https://bugs.launchpad.net/neutron/+bug/1576757


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

Title:
  [sriov] physical_device_mappings allows only one physnet for per nic

Status in neutron:
  Fix Released

Bug description:
  Mitaka, ML2, ml2_sriov.agent_required=True

  sriov_nic.physical_device_mappings is allowed to specify ony one NIC
  per physnet. If I try to specify two nics like following

  [sriov_nic]
  physical_device_mappings=physnet2:enp1s0f0,physnet2:enp1s0f1

  I've got next error on start

  2016-03-17 15:26:48.818 6832 INFO neutron.common.config [-] Logging enabled!
  2016-03-17 15:26:48.819 6832 INFO neutron.common.config [-] 
/usr/bin/neutron-sriov-nic-agent version 8.0.0.0b3
  2016-03-17 15:26:48.819 6832 DEBUG neutron.common.config [-] command line: 
/usr/bin/neutron-sriov-nic-agent 
--config-file=/etc/neutron/plugins/ml2/sriov_agent.ini 
--log-file=/var/log/neutron/neutron-sriov-agent.log 
--config-file=/etc/neutron/neutron.conf setup_logging 
/usr/lib/python2.7/dist-packages/neutron/common/config.py:266
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Failed on 
Agent configuration parse. Agent terminated!
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent Traceback (most 
recent call last):
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py",
 line 436, in main
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent 
config_parser.parse()
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py",
 line 411, in parse
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent 
cfg.CONF.SRIOV_NIC.physical_device_mappings)
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent   File 
"/usr/lib/python2.7/dist-packages/neutron/common/utils.py", line 240, in 
parse_mappings
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent "unique") % 
{'key': key, 'mapping': mapping})
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent ValueError: Key 
physnet2 in mapping: 'physnet2:enp1s0f1' not unique
  2016-03-17 15:26:48.819 6832 ERROR 
neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1558626/+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 1576755] [NEW] Paramiko 2.0 does not work with Nova

2016-04-29 Thread git-harry

Public bug reported:

Paramiko 2.0 has just been release and breaks nova which currently has a
requirement for 'paramiko>=1.16.0 # LGPL'

2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
[req-2e14bc90-999a-46ba-95f6-de817548014e 8fbdaf628d114c32a81f7587df939771 
be553343f9674e61b53b6b2516d4be2f - - -] Unexpected exception in API method
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/extensions.py",
 line 478, in wrapped
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/validation/__init__.py",
 line 73, in wrapper
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/validation/__init__.py",
 line 73, in wrapper
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/compute/keypairs.py",
 line 111, in create
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
self._create(req, body)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/api/openstack/compute/keypairs.py",
 line 132, in _create
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions context, 
user_id, name, key_type)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/exception.py", 
line 110, in wrapped
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions payload)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 220, in __exit__
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
self.force_reraise()
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/oslo_utils/excutils.py",
 line 196, in force_reraise
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions 
six.reraise(self.type_, self.value, self.tb)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/exception.py", 
line 89, in wrapped
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
f(self, context, *args, **kw)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/compute/api.py", 
line 4046, in create_key_pair
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions user_id, 
key_type)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/compute/api.py", 
line 4068, in _generate_key_pair
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions return 
crypto.generate_key_pair()
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/crypto.py", line 
152, in generate_key_pair
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions key = 
generate_key(bits)
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions   File 
"/openstack/venvs/nova-master/lib/python2.7/site-packages/nova/crypto.py", line 
144, in generate_key
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions key = 
paramiko.RSAKey(vals=(rsa.e, rsa.n))
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions TypeError: 
__init__() got an unexpected keyword argument 'vals'
2016-04-29 14:56:58.381 2175 ERROR nova.api.openstack.extensions
2016-04-29 14:56:58.395 2175 INFO nova.api.openstack.wsgi 
[req-2e14bc90-999a-46ba-95f6-de817548014e 8fbdaf628d114c32a81f7587df939771 
be553343f9674e61b53b6b2516d4be2f - - -] HTTP exception thrown: Unexpected API 
Error. Please report this at http://bugs.launchpad.net/nova/ and attach the 
Nova API log if possible.

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

Title:
  Paramiko 2.0 does not work with Nova

Status in OpenStack Compute (nova):
  New

Bug description:

[Yahoo-eng-team] [Bug 1570748] Re: Bug: resize instance after edit flavor with horizon

2016-04-29 Thread Drew Thorstensen

** Also affects: nova-powervm
   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/1570748

Title:
  Bug: resize instance after edit flavor with horizon

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Fix Committed
Status in OpenStack Compute (nova) liberty series:
  Fix Committed
Status in OpenStack Compute (nova) mitaka series:
  Fix Committed
Status in nova-powervm:
  New
Status in tempest:
  Fix Released

Bug description:
  Error occured when resize instance after edit flavor with horizon (and
  also delete flavor used by instance)

  Reproduce step :

  1. create flavor A
  2. boot instance using flavor A
  3. edit flavor with horizon (or delete flavor A)
  -> the result is same to edit or to delelet flavor because edit flavor 
means delete/recreate flavor)
  4. resize or migrate instance
  5. Error occured

  Log : 
  nova-compute.log
 File "/opt/openstack/src/nova/nova/conductor/manager.py", line 422, in 
_object_dispatch
   return getattr(target, method)(*args, **kwargs)

 File "/opt/openstack/src/nova/nova/objects/base.py", line 163, in wrapper
   result = fn(cls, context, *args, **kwargs)

 File "/opt/openstack/src/nova/nova/objects/flavor.py", line 132, in 
get_by_id
   db_flavor = db.flavor_get(context, id)

 File "/opt/openstack/src/nova/nova/db/api.py", line 1479, in flavor_get
   return IMPL.flavor_get(context, id)

 File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 233, in 
wrapper
   return f(*args, **kwargs)

 File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 4732, in 
flavor_get
   raise exception.FlavorNotFound(flavor_id=id)

   FlavorNotFound: Flavor 7 could not be found.

  
  This Error is occured because of below code:
  /opt/openstack/src/nova/nova/compute/manager.py

  def resize_instance(self, context, instance, image,
  reservations, migration, instance_type,
  clean_shutdown=True):
  
  if (not instance_type or
  not isinstance(instance_type, objects.Flavor)):
  instance_type = objects.Flavor.get_by_id(
  context, migration['new_instance_type_id'])
  

  I think that deleted flavor should be taken when resize instance. 
  I tested this in stable/kilo, but I think stable/liberty and stable/mitaka 
has same bug because source code is not changed.

  thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1570748/+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 1576713] [NEW] Network metadata fails to state correct mtu

2016-04-29 Thread Dr. Jens Rosenboom

Public bug reported:

Scenario:

Instance is booted on Neutron tenant network with ML2 OVS driver and
encapsulation. The MTU for that network is automatically calculated as
1450. Instance has --config-drive=true set.

Result:

In /openstack/latest/network_data.json we get:

 "links": [{"ethernet_mac_address": "fa:16:3e:36:96:c8", "mtu": null,
"type": "ovs", "id": "tapb989c3aa-5c", "vif_id": "b989c3aa-5c1f-
4d2b-8711-b96c66604902"}]

Expected:

Have "mtu": "1450" instead.

Environment:

OpenStack Mitaka on Ubuntu 16.04

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

Title:
  Network metadata fails to state correct mtu

Status in OpenStack Compute (nova):
  New

Bug description:
  Scenario:

  Instance is booted on Neutron tenant network with ML2 OVS driver and
  encapsulation. The MTU for that network is automatically calculated as
  1450. Instance has --config-drive=true set.

  Result:

  In /openstack/latest/network_data.json we get:

   "links": [{"ethernet_mac_address": "fa:16:3e:36:96:c8", "mtu": null,
  "type": "ovs", "id": "tapb989c3aa-5c", "vif_id": "b989c3aa-5c1f-
  4d2b-8711-b96c66604902"}]

  Expected:

  Have "mtu": "1450" instead.

  Environment:

  OpenStack Mitaka on Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1576713/+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 1576710] [NEW] Glance config generator files need to be updated for oslo_db

2016-04-29 Thread Peter Nordquist

Public bug reported:

The current config generator files at etc/oslo-config-generator/* need
to be updated to import the correct packages for oslo_db.concurrency.
They currently import oslo.db.concurrency which does not exist in the
Mitaka version of oslo.db.  I'm currently using the python2-oslo-
db-4.6.0-1 package in the RDO repositories to attempt to build these
configuration files.

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Glance config generator files need to be updated for oslo_db

Status in Glance:
  New

Bug description:
  The current config generator files at etc/oslo-config-generator/* need
  to be updated to import the correct packages for oslo_db.concurrency.
  They currently import oslo.db.concurrency which does not exist in the
  Mitaka version of oslo.db.  I'm currently using the python2-oslo-
  db-4.6.0-1 package in the RDO repositories to attempt to build these
  configuration files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1576710/+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 1576692] [NEW] fully support package installation in systemd

2016-04-29 Thread Scott Moser

Public bug reported:

in cloud-init users can install packages via cloud-config:
#cloud-config
packages: [apache2]

Due to some intricacies of systemd and service installation that doesn't work 
all that well.
We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

We'd like to have a way to fully support this in cloud-init.


Related bugs:
 * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)

** Affects: cloud-init
 Importance: Medium
 Status: Confirmed

** Affects: cloud-init (Ubuntu)
 Importance: Medium
 Status: Confirmed

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

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

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

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

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  
  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+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 1575055] Re: check_instance_id() error on reboots when using config-drive

2016-04-29 Thread Scott Moser

Thanks for the bug report and the fix.
Committed in trunk.  I will try to get this uploaded to yakkety and to xenial 
today.

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  check_instance_id() error on reboots when using config-drive

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

Bug description:
  Problem Description
  =
  When using a config-drive to provide meta-data to cloud-init on ubuntu (for 
Linux guest running in KVM for z Systems) we get a check_instance_id() error 
whenever we soft reboot after the (successful) initial boot.

  The error shows:

  [5.283203] cloud-init[1637]: Cloud-init v. 0.7.7 running 'init-local' at 
Sat, 23 Apr 2016 00:50:58 +. Up 5.25 seconds.
  [5.283368] cloud-init[1637]: 2016-04-22 20:50:58,839 - util.py[WARNING]: 
failed of stage init-local
  [5.286659] cloud-init[1637]: failed run of stage init-local
  [5.286770] cloud-init[1637]: 

  [5.286849] cloud-init[1637]: Traceback (most recent call last):
  [5.286924] cloud-init[1637]:   File "/usr/bin/cloud-init", line 520, in 
status_wrapper
  [5.286998] cloud-init[1637]: ret = functor(name, args)
  [5.287079] cloud-init[1637]:   File "/usr/bin/cloud-init", line 250, in 
main_init
  [5.287152] cloud-init[1637]: init.fetch(existing=existing)
  [5.287225] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 322, in fetch
  [5.287298] cloud-init[1637]: return 
self._get_data_source(existing=existing)
  [5.287371] cloud-init[1637]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 229, in 
_get_data_source
  [5.287445] cloud-init[1637]: ds.check_instance_id(self.cfg)):
  [5.287518] cloud-init[1637]: TypeError: check_instance_id() takes 1 
positional argument but 2 were given
  [5.287592] cloud-init[1637]: 

  [FAILED] Failed to start Initial cloud-init job (pre-networking).

  
  The failure of the init-local pre-networking does seem to lead to a boot up 
delay as cloud-init tries to search for networking outside of the already saved 
networking data.   

  Otherwise the error is purely cosmetic as later init modules find (or
  let existing IP configuration take over) and bring up the correct
  interfaces.

  The original problem was found outside of openstack with stand-alone
  cloud-config iso images.  But have been able to reproduce the problem
  within an openstack ICM environment.

  Team has had some success getting around the problem by patching the
  check_instance_id function in /usr/lib/python3/dist-
  packages/cloudinit/sources/DataSourceConfigDrive.py so that it
  accepted an extra argument, ex:

  ubuntu@markvercd:~$ sudo cat check_instance_id.patch 
  --- /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py 
2016-04-06 15:29:59.0 +
  +++ 
/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py.new   
  2016-04-11 22:53:47.799867139 +
  @@ -155,7 +155,7 @@
   
   return True
   
  -def check_instance_id(self):
  +def check_instance_id(self,somecfg):
   # quickly (local check only) if self.instance_id is still valid
   return 
sources.instance_id_matches_system_uuid(self.get_instance_id())
   
  ubuntu@markvercd:~$ 

  ---uname output---
  Linux k6mpathcl.pokprv.stglabs.ibm.com 4.4.0-21-generic #37-Ubuntu SMP Mon 
Apr 18 18:31:26 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = KVM guest on a z13 (2827-732) LPAR 

  Steps to Reproduce
  =
   1) set up ubuntu guest image with cloud-init
  2) pass in iso image with cloud-config data in cdrom device
  3) boot up successfully with cloud-config data
  4) attempt a soft reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1575055/+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 1576621] Re: Snapshots are alway made in raw and not qcow2

2016-04-29 Thread Kairat Kushaev

Hello Mark,
glance does not convert images during the upload. It just stores bits.
If you look at the Ceph documentation looks like there is troubles with qcow2:
http://docs.ceph.com/docs/master/rbd/rbd-openstack/

Ceph doesn’t support QCOW2 for hosting a virtual machine disk. Thus if
you want to boot virtual machines in Ceph (ephemeral backend or boot
from volume), the Glance image format must be RAW.

So I guess nova(or Cinder or other component that provides bits for
Glance image) always specifies RAW format always when ceph is used.

I hope this thread also help you.

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

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

Title:
  Snapshots are alway made in raw and not qcow2

Status in Glance:
  Invalid

Bug description:
  Hi,
  I am using the same version of openstack in two deployments. When I take a 
snapshot in one environment its is saved in qcow2 but in the other it is saved 
as raw. The raw format saves an image with the size of the flavour. qcow2 
format saves an image the size of the actual used disk space. 

  The version I am using of openstack is: Version: 2015.1.1

  The version of Glance is: 0.17.1

  I could not ascertain any difference between the glance configuration
  in both environments. The only difference is that the CEPH file system
  is used in the deployment where snapshots are saved in raw. However we
  are able to upload images in qcow2 nonetheless.

  Thank you,
  Mark Donovan

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1576621/+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 1576648] [NEW] horizon-pending-bar decreases performance

2016-04-29 Thread Ivan Lozgachev

Public bug reported:

Steps to reproduce
1. Create 100 volumes
2. Set number of items per page to 100 (in Admin -> Settings -> User Settings 
-> Items Per Page)
3. Open Volumes page (Project -> Compute -> Volumes)
4. Select all volumes and delete them (to get progress bar showed on all 
items). The same could be do by executing simple script which deletes all 
volumes.

The page performance is critically slow. Execution of script

$(".horizon-pending-bar").hide()

significantly improve page performance.

Please do not show "horizon-pending-bar" when number of *pending*
instances on page more than 20~30. This looks ugly and has bad UX.

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

Title:
  horizon-pending-bar decreases performance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce
  1. Create 100 volumes
  2. Set number of items per page to 100 (in Admin -> Settings -> User Settings 
-> Items Per Page)
  3. Open Volumes page (Project -> Compute -> Volumes)
  4. Select all volumes and delete them (to get progress bar showed on all 
items). The same could be do by executing simple script which deletes all 
volumes.

  The page performance is critically slow. Execution of script

  $(".horizon-pending-bar").hide()

  significantly improve page performance.

  Please do not show "horizon-pending-bar" when number of *pending*
  instances on page more than 20~30. This looks ugly and has bad UX.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1576648/+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 1576273] Re: CloudStack datasource fails to find DHCP lease if IPv6 present

2016-04-29 Thread Dan Watkins

Thanks Wido, merged and pushed!

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  CloudStack datasource fails to find DHCP lease if IPv6 present

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  New

Bug description:
  The CloudStack data source looks in /var/lib/dhcp for DHCP lease files
  and compares the timestamps.

  If you have a dhclient.leases and dhclient6.leases file present it
  will look in the dhclient6.leases file for a DHCP server to connect
  to.

  The fix for this is rather simple, change a if-statement so that it
  checks if the leases file starts with 'dhclient.'

  if file_name.startswith("dhclient.") and \
 (file_name.endswith(".lease") or file_name.endswith(".leases")):

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576273/+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 1576640] [NEW] Override max_concurrent_builds constraint

2016-04-29 Thread Prithiv

Public bug reported:

At the moment, Nova has a max concurrent build limit (10, if am not
wrong) as per https://review.openstack.org/#/c/153004/

When using Kolla/devstack with single/multi-node fake compute nodes with
fake libvirt driver, this limitation has to be overridden.

** Affects: nova
 Importance: Undecided
 Status: Opinion

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

Title:
  Override max_concurrent_builds constraint

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  At the moment, Nova has a max concurrent build limit (10, if am not
  wrong) as per https://review.openstack.org/#/c/153004/

  When using Kolla/devstack with single/multi-node fake compute nodes
  with fake libvirt driver, this limitation has to be overridden.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1576640/+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 1576621] [NEW] Snapshots are alway made in raw and not qcow2

2016-04-29 Thread Mark Donovan

Public bug reported:

Hi,
I am using the same version of openstack in two deployments. When I take a 
snapshot in one environment its is saved in qcow2 but in the other it is saved 
as raw. The raw format saves an image with the size of the flavour. qcow2 
format saves an image the size of the actual used disk space. 

The version I am using of openstack is: Version: 2015.1.1

The version of Glance is: 0.17.1

I could not ascertain any difference between the glance configuration in
both environments. The only difference is that the CEPH file system is
used in the deployment where snapshots are saved in raw. However we are
able to upload images in qcow2 nonetheless.

Thank you,
Mark Donovan

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  Snapshots are alway made in raw and not qcow2

Status in Glance:
  New

Bug description:
  Hi,
  I am using the same version of openstack in two deployments. When I take a 
snapshot in one environment its is saved in qcow2 but in the other it is saved 
as raw. The raw format saves an image with the size of the flavour. qcow2 
format saves an image the size of the actual used disk space. 

  The version I am using of openstack is: Version: 2015.1.1

  The version of Glance is: 0.17.1

  I could not ascertain any difference between the glance configuration
  in both environments. The only difference is that the CEPH file system
  is used in the deployment where snapshots are saved in raw. However we
  are able to upload images in qcow2 nonetheless.

  Thank you,
  Mark Donovan

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1576621/+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 1576586] [NEW] Link "Download key pair" regenerates keypair

2016-04-29 Thread Dmitry Dmitriev

Public bug reported:

To reproduce the problem pass the following steps:

- login into Horizon
- click Project
- click Compute
- click Access & Security
- click Key Pairs
- click Create Key Pair
- enter key pair name
- click Generate (in Safari download starts automatically)
- click Download key pair

Expected result:

- Downloads folder contains two copy of the same private key

Actual result:

- Downloads folder contains two different private keys

Workaround:

- generate public key for each of private keys and determine which one is valid
 
Impact:

- user can not get SSH access to new compute nodes

Description of the environment:

- Liberty OpenStack

Ways to solve:

- rename link  "Download key pair" to "Re-generate key pair".

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

Title:
  Link "Download key pair" regenerates keypair

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  To reproduce the problem pass the following steps:

  - login into Horizon
  - click Project
  - click Compute
  - click Access & Security
  - click Key Pairs
  - click Create Key Pair
  - enter key pair name
  - click Generate (in Safari download starts automatically)
  - click Download key pair

  Expected result:

  - Downloads folder contains two copy of the same private key

  Actual result:

  - Downloads folder contains two different private keys

  Workaround:

  - generate public key for each of private keys and determine which one is 
valid
   
  Impact:

  - user can not get SSH access to new compute nodes

  Description of the environment:

  - Liberty OpenStack

  Ways to solve:

  - rename link  "Download key pair" to "Re-generate key pair".

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1576586/+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 1576543] [NEW] nova tests for windows images are failed

2016-04-29 Thread Yury Tregubov

Public bug reported:

Nova tests like
https://mirantis.testrail.com/index.php?/tests/view/4938418_by=cases:section_id_order=asc_id=23073
are failed on CI. However they are passed with manual run on different
server.  Perhaps the problem within the server's environment. And may be
the tests should be tuned a bit to pass on slow environments.

** Affects: mos
 Importance: Undecided
 Status: New


** Tags: area-qa

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

** Project changed: nova => mos

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

** Tags added: area-qa

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

Title:
  nova tests for windows images are failed

Status in Mirantis OpenStack:
  New

Bug description:
  Nova tests like
  
https://mirantis.testrail.com/index.php?/tests/view/4938418_by=cases:section_id_order=asc_id=23073
  are failed on CI. However they are passed with manual run on different
  server.  Perhaps the problem within the server's environment. And may
  be the tests should be tuned a bit to pass on slow environments.

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

43 matches

Mail list logo