[Yahoo-eng-team] [Bug 1538448] [NEW] REST api layer doesn't handle TooManyInstances while doing resize

[Eli Qiao]

Public bug reported:

compute_api may raise TooManyInstances if over quota, but no handler in
REST Api layer.

** Affects: nova
 Importance: Low
 Assignee: Eli Qiao (taget-9)
 Status: Confirmed


** Tags: api

** Changed in: nova
 Assignee: (unassigned) => Eli Qiao (taget-9)

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

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

** Tags added: api

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

Title:
  REST api layer doesn't handle TooManyInstances while doing resize

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  compute_api may raise TooManyInstances if over quota, but no handler
  in REST Api layer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538448/+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 1520729] Re: Disassociate floating IP from instance with an interface with no IP fails

[guiyanxing]

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

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

Title:
  Disassociate floating IP from instance with an interface with no IP
  fails

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  If you have an instance with 2 interfaces, and one of them has no IP (e.g. is 
L2 only), then 
  list_target_id_by_instance() fails when you disassociate a floating-ip from 
the first interface.

  This patch resolves.

  index 1478a6f..a026b15 100644
  --- a/openstack_dashboard/api/neutron.py
  +++ b/openstack_dashboard/api/neutron.py
  @@ -506,8 +506,11 @@ class FloatingIpManager(network_base.FloatingIpManager):
   if target['instance_id'] == instance_id]
   else:
   ports = self._target_ports_by_instance(instance_id)
  -return ['{0}_{1}'.format(p.id, p.fixed_ips[0]['ip_address'])
  -for p in ports]
  +v = []
  +for p in ports:
  +if len(p['fixed_ips']):
  +v.append('{0}_{1}'.format(p['id'], 
p['fixed_ips'][0]['ip_address']))
  +return v

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1520729/+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 1538464] [NEW] migrate_data param of _rollback_live_migration should be object.

[lvmxh]

Public bug reported:

when I go through  ComputeManager._rollback_live_migration, I find
migrate_data should be object instead of dict.

Now there are two place to call it.

one is when Exception do  pre_live_migration, it is still use dict.

Another is in driver.live_migration. The _rollback_live_migration as a 
recover_method callback pass to driver.live_migration.
The migrate_data is right here.

** Affects: nova
 Importance: Undecided
 Assignee: lvmxh (shaohef)
 Status: New

** Description changed:

  when I go through  ComputeManager._rollback_live_migration, I find
  migrate_data should be object instead of dict.
  
- Now there are two place call it.
+ Now there are two place to call it.
  
  one is when Exception do  pre_live_migration, it is still use dict.
  
- Another is in driver.live_migration. The _rollback_live_migration as a 
recover_method callback pass to driver.live_migration.  
+ Another is in driver.live_migration. The _rollback_live_migration as a 
recover_method callback pass to driver.live_migration.
  The migrate_data is right here.

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

Title:
  migrate_data param  of _rollback_live_migration should be object.

Status in OpenStack Compute (nova):
  New

Bug description:
  when I go through  ComputeManager._rollback_live_migration, I find
  migrate_data should be object instead of dict.

  Now there are two place to call it.

  one is when Exception do  pre_live_migration, it is still use dict.

  Another is in driver.live_migration. The _rollback_live_migration as a 
recover_method callback pass to driver.live_migration.
  The migrate_data is right here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538464/+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 1481370] Re: system logging module is still in use in many places

[Dougal Matthews]

** Changed in: tuskar
   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/1481370

Title:
  system logging module is still in use in many places

Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in Stackalytics:
  Fix Released
Status in tempest:
  In Progress
Status in Trove:
  Fix Released
Status in tuskar:
  Won't Fix

Bug description:
  The system logging module is still in use in many places, i suggest to
  use the oslo.log library. Form the 1.8 version of oslo.log we can use
  the constants of the log levels (INFO, DEBUG, etc) directly from log
  module instead of system logging module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/murano/+bug/1481370/+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 1285530] Re: exception message should use gettextutils

[Dougal Matthews]

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

** Changed in: tuskar-ui
   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/1285530

Title:
  exception message should use gettextutils

Status in neutron:
  Fix Released
Status in oslo-incubator:
  Won't Fix
Status in oslo.messaging:
  Incomplete
Status in python-neutronclient:
  Incomplete
Status in OpenStack Object Storage (swift):
  In Progress
Status in tuskar:
  Won't Fix
Status in tuskar-ui:
  Won't Fix

Bug description:
  What To Translate

  At present the convention is to translate all user-facing strings.
  This means API messages, CLI responses, documentation, help text, etc.

  There has been a lack of consensus about the translation of log
  messages; the current ruling is that while it is not against policy to
  mark log messages for translation if your project feels strongly about
  it, translating log messages is not actively encouraged.

  Exception text should not be marked for translation, becuase if an
  exception occurs there is no guarantee that the translation machinery
  will be functional.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1285530/+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 1538477] [NEW] "port.delete.start" notification is not thrown.

[Kumar Acharya]

Public bug reported:

We are using juno version of nova.

I have noticed that when a nic is removed from an Instance we should be
getting a notification "port.delete.start" thrown.

But this notification is not getting thrown.

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

Title:
  "port.delete.start" notification is not thrown.

Status in OpenStack Compute (nova):
  New

Bug description:
  We are using juno version of nova.

  I have noticed that when a nic is removed from an Instance we should
  be getting a notification "port.delete.start" thrown.

  But this notification is not getting thrown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538477/+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 1512207] Re: Fix usage of assertions

[Dougal Matthews]

** No longer affects: tuskar

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

Title:
  Fix usage of assertions

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Blazar:
  In Progress
Status in Cinder:
  Invalid
Status in congress:
  Fix Released
Status in Cue:
  Fix Released
Status in Glance:
  Won't Fix
Status in Group Based Policy:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in Ironic Inspector:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in kuryr:
  Fix Released
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in Murano:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Health:
  In Progress
Status in os-brick:
  Fix Released
Status in os-net-config:
  In Progress
Status in os-testr:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.utils:
  In Progress
Status in Packstack:
  Fix Released
Status in python-barbicanclient:
  In Progress
Status in python-ceilometerclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in Rally:
  Fix Released
Status in refstack:
  In Progress
Status in requests-mock:
  In Progress
Status in Sahara:
  Fix Released
Status in shaker:
  Fix Released
Status in Solum:
  Fix Released
Status in Stackalytics:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released
Status in Vitrage:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  Fix Released

Bug description:
  Manila  should use the specific assertion:

self.assertIsTrue/False(observed)

  instead of the generic assertion:

self.assertEqual(True/False, observed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1512207/+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 1508442] Re: LOG.warn is deprecated

[Dougal Matthews]

** No longer affects: tuskar

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

Title:
  LOG.warn is deprecated

Status in anvil:
  In Progress
Status in Aodh:
  In Progress
Status in Astara:
  Fix Released
Status in Barbican:
  In Progress
Status in bilean:
  In Progress
Status in Blazar:
  In Progress
Status in Ceilometer:
  Fix Released
Status in cloud-init:
  In Progress
Status in cloudkitty:
  Fix Released
Status in congress:
  In Progress
Status in Designate:
  Fix Released
Status in django-openstack-auth:
  Fix Released
Status in django-openstack-auth-kerberos:
  New
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  In Progress
Status in Evoque:
  In Progress
Status in gce-api:
  In Progress
Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Gnocchi:
  In Progress
Status in heat:
  Fix Released
Status in heat-cfntools:
  In Progress
Status in OpenStack Identity (keystone):
  Fix Committed
Status in KloudBuster:
  Fix Released
Status in kolla:
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  In Progress
Status in networking-arista:
  In Progress
Status in networking-calico:
  In Progress
Status in networking-cisco:
  In Progress
Status in networking-fujitsu:
  In Progress
Status in networking-odl:
  In Progress
Status in networking-ofagent:
  In Progress
Status in networking-plumgrid:
  In Progress
Status in networking-powervm:
  In Progress
Status in networking-vsphere:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in nova-powervm:
  Fix Released
Status in nova-solver-scheduler:
  In Progress
Status in octavia:
  In Progress
Status in openstack-ansible:
  In Progress
Status in oslo.cache:
  Fix Released
Status in oslo.privsep:
  In Progress
Status in Packstack:
  Fix Released
Status in python-dracclient:
  In Progress
Status in python-magnumclient:
  Fix Released
Status in RACK:
  In Progress
Status in python-watcherclient:
  In Progress
Status in shaker:
  In Progress
Status in Solum:
  Fix Released
Status in tempest:
  In Progress
Status in tripleo:
  In Progress
Status in trove-dashboard:
  In Progress
Status in watcher:
  Fix Released
Status in zaqar:
  In Progress

Bug description:
  LOG.warn is deprecated in Python 3 [1] . But it still used in a few
  places, non-deprecated LOG.warning should be used instead.

  Note: If we are using logger from oslo.log, warn is still valid [2],
  but I agree we can switch to LOG.warning.

  [1]https://docs.python.org/3/library/logging.html#logging.warning
  [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1508442/+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 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()

[Dougal Matthews]

** No longer affects: python-tuskarclient

** No longer affects: tuskar

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

Title:
  assertTrue(isinstance()) in tests should be replace with
  assertIsInstance()

Status in anvil:
  In Progress
Status in Barbican:
  Fix Released
Status in Ceilometer:
  Fix Released
Status in Cinder:
  In Progress
Status in CloudRoast:
  In Progress
Status in congress:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Monasca:
  Fix Released
Status in Murano:
  Fix Released
Status in networking-powervm:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  In Progress
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  In Progress
Status in OpenStack SDK:
  Fix Released
Status in python-rackclient:
  In Progress
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in Trove:
  Fix Released

Bug description:
  some of tests use different method of assertTrue(isinstance(A, B)) or
  assertEqual(type(A), B). The correct way is to use assertIsInstance(A,
  B) provided by testtools

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1268480/+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 1538484] [NEW] Renaming Flavors

[Andrei]

Public bug reported:

I have several problems with renaming a flavor here.


I have the flavor 'astra-test-flavor'.

root@cloud:~# nova flavor-list --all
+--+-+---+--+---+--+---+-+---+
| ID   | Name| Memory_MB | 
Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+--+-+---+--+---+--+---+-+---+
| 1| m1.tiny | 512   | 
1| 0 |  | 1 | 1.0 | True  |
| 2| m1.small| 2048  | 
20   | 0 |  | 1 | 1.0 | True  |
| 3| m1.medium   | 4096  | 
40   | 0 |  | 2 | 1.0 | True  |
| 4| m1.large| 8192  | 
80   | 0 |  | 4 | 1.0 | True  |
| 5| m1.xlarge   | 16384 | 
160  | 0 |  | 8 | 1.0 | True  |
| b3ecba5c-9432-4787-9ff3-ce0e7c08084f | astra-test-flavor   | 512   | 
0| 1 |  | 1 | 1.0 | True  |
+--+-+---+--+---+--+---+-+---+

The flavor is used by the VM 'astra-test-vm'.

root@cloud:~# nova show astra-test-vm
+--++
| Property | Value  
|
+--++
| Int-net network  | 10.0.0.60  
|
| OS-DCF:diskConfig| AUTO   
|
| OS-EXT-AZ:availability_zone  | nova   
|
| OS-EXT-SRV-ATTR:host | kvm1.openstack3.lan
|
| OS-EXT-SRV-ATTR:hypervisor_hostname  | kvm1.openstack3.lan
|
| OS-EXT-SRV-ATTR:instance_name| instance-0066  
|
| OS-EXT-STS:power_state   | 1  
|
| OS-EXT-STS:task_state| -  
|
| OS-EXT-STS:vm_state  | active 
|
| OS-SRV-USG:launched_at   | 2016-01-26T09:19:54.00 
|
| OS-SRV-USG:terminated_at | -  
|
| accessIPv4   |
|
| accessIPv6   |
|
| config_drive |
|
| created  | 2016-01-26T09:19:38Z   
|
| flavor   | astra-test-flavor 
(b3ecba5c-9432-4787-9ff3-ce0e7c08084f)   |
| hostId   | 
42a9413f62afdd8dbfb52086dffdc5f68bbc36c12ecc3740379c9d7d   |
| id   | b3e3f0b6-8b5c-4930-adab-ad5b0cd90d88   
|
| image| Cirros-0.3.2-x86_64 
(d14f288b-f7bf-45e8-8374-f7d98731dbcb) |
| key_name | PS_linux   
|
| metadata | {} 
|
| name | astra-test-vm  
|
| os-extended-volumes:volumes_attached | [] 
|
| progress | 0  
|
| security_groups  | default
|
| status   | ACTIVE 
|
| tenant_id| 27eaa26280904fe09637020a37112e2b   
|
| updated  | 2016-01-26T09:19:54Z   
|
| user_id  | f22a3f9f2235471fb512e50d004cae93   
|
+--+

[Yahoo-eng-team] [Bug 1538491] [NEW] Angular Launch Instance should use adhere to Horizon theming standards

[Rob Cresswell]

Public bug reported:

The Angular Launch Instance workflow is totally separate from the rest
of the Horizon design and theming. It should use the bootstrap markup
and theming where possible.

** Affects: horizon
 Importance: Wishlist
 Assignee: Rob Cresswell (robcresswell)
 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/1538491

Title:
  Angular Launch Instance should use adhere to Horizon theming standards

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The Angular Launch Instance workflow is totally separate from the rest
  of the Horizon design and theming. It should use the bootstrap markup
  and theming where possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1538491/+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 1538497] [NEW] Race condition: returns 404 when listing ports

[Thomas Herve]

Public bug reported:

I've observed this behavior in heat integration tests:
http://logs.openstack.org/51/271451/1/gate/gate-heat-dsvm-functional-
orig-mysql/9f09db7/logs/

When creating a server, nova calls list_ports and it fails because a
network can't be found: http://logs.openstack.org/51/271451/1/gate/gate-
heat-dsvm-functional-orig-
mysql/9f09db7/logs/screen-n-api.txt.gz?level=ERROR

As it turns out, the network has been removed after the list ports has
started, thus making it failing.

It should handle that NotFound and ignore the error, as there is a
transaction issue somewhere.

http://logs.openstack.org/51/271451/1/gate/gate-heat-dsvm-functional-
orig-mysql/9f09db7/logs/screen-q-svc.txt.gz?level=ERROR is the neutron
side failure.

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Race condition: returns 404 when listing ports

Status in neutron:
  New

Bug description:
  I've observed this behavior in heat integration tests:
  http://logs.openstack.org/51/271451/1/gate/gate-heat-dsvm-functional-
  orig-mysql/9f09db7/logs/

  When creating a server, nova calls list_ports and it fails because a
  network can't be found: http://logs.openstack.org/51/271451/1/gate
  /gate-heat-dsvm-functional-orig-
  mysql/9f09db7/logs/screen-n-api.txt.gz?level=ERROR

  As it turns out, the network has been removed after the list ports has
  started, thus making it failing.

  It should handle that NotFound and ignore the error, as there is a
  transaction issue somewhere.

  http://logs.openstack.org/51/271451/1/gate/gate-heat-dsvm-functional-
  orig-mysql/9f09db7/logs/screen-q-svc.txt.gz?level=ERROR is the neutron
  side failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538497/+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 1536586] Re: Angular: neutron.service getPorts is using the wrong call parameters

[OpenStack Infra]

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

commit 2354efe6caaa2f028bb1587af029410172127ea1
Author: Itxaka 
Date:   Thu Jan 21 12:38:39 2016 +0100

Pass the proper params to getPorts call

Fixes the proper params to pass for the neutron ports
call by accepting a dictionary with param_name:value
as this is whats expected from neutron client/API

Change-Id: I75d63f561cac97d2f8e0370f39f260a40029d685
Closes-Bug: #1536586


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

Title:
  Angular: neutron.service getPorts is using the wrong call parameters

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Looks like our getPorts needs a NetworkId parameter:

  @param {string} networkId
   * The network id to retrieve ports for. Required.

  
  And it passes it directly to the apiService

  return apiService.get('/api/neutron/ports/', networkId)

  
  But looking at other services that accept params for filtering, this does not 
look like the correct way of doing it, see glance getImages for example:

  function getImages(params) {
var config = (params) ? { 'params' : params} : {};
return apiService.get('/api/glance/images/', config)

  
  So when passing anything as networkId, you will always get ALL ports that the 
tenant has access instead of filtering by network_id.

  
  This should be changed so it looks more like the glance service and a random 
number of params can be passed to getPorts.

  Also while networkId is marked in our code as it being required, its not as 
per the neutron documentation:
  http://developer.openstack.org/api-ref-networking-v2.html#ports

  and instead you just use query filtering to filter:
  
https://wiki.openstack.org/wiki/Neutron/APIv2-specification#Filtering_and_Column_Selection

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1536586/+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 1538484] Re: Renaming Flavors

[Augustina Ragwitz]

See http://docs.openstack.org/openstack-ops/content/flavors.html for an
explanation. The dashboard simulates editing a flavor by deleting the
old one and creating a new one, which is why the id changed. Your VM is
still associated with the original flavor because the original flavor
was never actually modified. This is by design and not a bug.

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

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

Title:
  Renaming Flavors

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I have several problems with renaming a flavor here.

  
  I have the flavor 'astra-test-flavor'.

  root@cloud:~# nova flavor-list --all
  
+--+-+---+--+---+--+---+-+---+
  | ID   | Name| Memory_MB 
| Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
  
+--+-+---+--+---+--+---+-+---+
  | 1| m1.tiny | 512   
| 1| 0 |  | 1 | 1.0 | True  |
  | 2| m1.small| 2048  
| 20   | 0 |  | 1 | 1.0 | True  |
  | 3| m1.medium   | 4096  
| 40   | 0 |  | 2 | 1.0 | True  |
  | 4| m1.large| 8192  
| 80   | 0 |  | 4 | 1.0 | True  |
  | 5| m1.xlarge   | 16384 
| 160  | 0 |  | 8 | 1.0 | True  |
  | b3ecba5c-9432-4787-9ff3-ce0e7c08084f | astra-test-flavor   | 512   
| 0| 1 |  | 1 | 1.0 | True  |
  
+--+-+---+--+---+--+---+-+---+

  The flavor is used by the VM 'astra-test-vm'.

  root@cloud:~# nova show astra-test-vm
  
+--++
  | Property | Value
  |
  
+--++
  | Int-net network  | 10.0.0.60
  |
  | OS-DCF:diskConfig| AUTO 
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | kvm1.openstack3.lan  
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | kvm1.openstack3.lan  
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-0066
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2016-01-26T09:19:54.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2016-01-26T09:19:38Z 
  |
  | flavor   | astra-test-flavor 
(b3ecba5c-9432-4787-9ff3-ce0e7c08084f)   |
  | hostId   | 
42a9413f62afdd8dbfb52086dffdc5f68bbc36c12ecc3740379c9d7d   |
  | id   | b3e3f0b6-8b5c-4930-adab-ad5b0cd90d88 
  |
  | image| Cirros-0.3.2-x86_64 
(d14f288b-f7bf-45e8-8374-f7d98731dbcb) |
  | key_name | PS_linux 
  |
  | metadata | {}   
  |
  | name | astra-test-vm
  |
  | os-extended-volumes:volumes_attached | []

[Yahoo-eng-team] [Bug 1538464] Re: migrate_data param of _rollback_live_migration should be object.

[Markus Zoeller (markus_z)]

@lvmxh:
That's already in progress with blueprint [1]. Would be great if you could 
participate in the reviews of that bp's patches.

[1] https://blueprints.launchpad.net/nova/+spec/objectify-live-migrate-
data

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

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

Title:
  migrate_data param  of _rollback_live_migration should be object.

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  when I go through  ComputeManager._rollback_live_migration, I find
  migrate_data should be object instead of dict.

  Now there are two place to call it.

  one is when Exception do  pre_live_migration, it is still use dict.

  Another is in driver.live_migration. The _rollback_live_migration as a 
recover_method callback pass to driver.live_migration.
  The migrate_data is right here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538464/+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 1538002] Re: incorrect info returned when show aggregate info

[Markus Zoeller (markus_z)]

bug skimming
--
It looks like the python-openstackclient handles empty values different than 
the python-novalient CLI. As the Nova API returns the values as is and the 
python-novaclient handles it as expected, I thing the issue (if any) is in the 
python-openstackclient.

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

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

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

Title:
  incorrect info returned when show aggregate info

Status in OpenStack Compute (nova):
  Invalid
Status in python-openstackclient:
  New

Bug description:
  [Summary]
  incorrect info returned when show aggregate info

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  correct info returned when show aggregate info

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) create an aggregate, availability_zone is not specified:
  root@45-59:~# openstack aggregate create agg1
  +---++
  | Field | Value  |
  +---++
  | availability_zone | None   |
  | created_at| 2016-01-26T14:23:24.00 |
  | deleted   | False  |
  | deleted_at| None   |
  | id| 6  |
  | name  | agg1   |
  | updated_at| None   |
  +---++
  root@45-59:~# 
  root@45-59:~# 
  root@45-59:~# openstack aggregate list
  ++--+---+
  | ID | Name | Availability Zone |
  ++--+---+
  |  6 | agg1 | None  |  ISSUE, availability_zone is shown as 
"None"
  ++--+---+
  root@45-59:~#

  ISSUE: availability_zone can be shown as "-"

  2)below is nova cmd for reference:
  root@45-59:~# nova aggregate-details agg1
  ++--+---+---+--+
  | Id | Name | Availability Zone | Hosts | Metadata |
  ++--+---+---+--+
  | 6  | agg1 | - |   |  |
  ++--+---+---+--+
  root@45-59:~# 
  root@45-59:~# nova aggregate-list
  ++--+---+
  | Id | Name | Availability Zone |
  ++--+---+
  | 6  | agg1 | - |
  ++--+---+
  root@45-59:~#

  
  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538002/+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 1538477] Re: "port.delete.start" notification is not thrown.

[Markus Zoeller (markus_z)]

@Kumar:

bug skimming

The Juno release has reached EOL [1] which means we don't do fixes
for that anymore. Because of this I close it as "invalid".
If you see the issue in one of the later, still supported releases,
please reopen this issue and provide the version details of your
environment in the bug report description.

References:
--
[1] http://docs.openstack.org/releases/

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

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

Title:
  "port.delete.start" notification is not thrown.

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  We are using juno version of nova.

  I have noticed that when a nic is removed from an Instance we should
  be getting a notification "port.delete.start" thrown.

  But this notification is not getting thrown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538477/+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 1538522] [NEW] Calls "service walinuxagent start" in Azure data source

[Bastian Blank]

Public bug reported:

Hi

cloud-init calls "service walinuxagent start" in the Azure data source
during "init" phase.

Currently walinuxagent.service in Ubuntu 15.10 specifies:
| After=cloud-final.service
This asks systemd to start if much later, after the "final" phase.

New enough systemd version as available in Ubuntu 15.10 and Debian
Stretch will just ignore the relation, as it is a deadlock and start the
service in this place. Older version as in Debian Jessie will block the
whole boot.

Is there a reason to explicitely start walinuxagent instead of relying
on order in systemd?

Bastian

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

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

Title:
  Calls "service walinuxagent start" in Azure data source

Status in cloud-init:
  New

Bug description:
  Hi

  cloud-init calls "service walinuxagent start" in the Azure data source
  during "init" phase.

  Currently walinuxagent.service in Ubuntu 15.10 specifies:
  | After=cloud-final.service
  This asks systemd to start if much later, after the "final" phase.

  New enough systemd version as available in Ubuntu 15.10 and Debian
  Stretch will just ignore the relation, as it is a deadlock and start
  the service in this place. Older version as in Debian Jessie will
  block the whole boot.

  Is there a reason to explicitely start walinuxagent instead of relying
  on order in systemd?

  Bastian

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1538522/+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 1538527] [NEW] Add support for the random access to images stored in the Rbd store

[Sergey Gotliv]

Public bug reported:

Glance V2 API supports random access to images since Juno, RBD datastore
is still missing that functionality.

** Affects: glance
 Importance: Undecided
 Assignee: Sergey Gotliv (sgotliv)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Sergey Gotliv (sgotliv)

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

Title:
  Add support for the random access to images stored in the Rbd store

Status in Glance:
  New

Bug description:
  Glance V2 API supports random access to images since Juno, RBD
  datastore is still missing that functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1538527/+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 1538169] Re: Quota_server_group_members parameter is not respected by nova

[Augustina Ragwitz]

Juno is EOL [1] so we aren't doing fixes for it anymore. I've closed
this as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.

References:
--
[1] http://docs.openstack.org/releases/

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

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

Title:
  Quota_server_group_members parameter is not respected by nova

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  When I create instances which I want to be in the same server group
  (--hint group=)  with parameter: --num-instances or --min-count
  /--max-count   and I have quota_server_group_members set to 5, nova is
  spawning all instances regardless quota.

   Example:
  nova boot --image $image --flavor small  --hint 
group=528ff1e3-5a6d-475c-826e-c70d7a56e769 --nic net-id= --min-count=2 
--max-count=10  test-instance

  All Instances has spawned correct. In next request I have an error:
  ERROR (Forbidden): Quota exceeded, too many servers in group (HTTP 403) 
(Request-ID: req-f8aa39cd-2a14-486d-95a9-747ed9eecbfc)

  
  Normally request which should spawn 10 instances (but quota is set to 5) 
should give an error with Quota exceeded.
  The same situation is with  --num-instances parameter.

  
  I check it many times in Juno release and on devstack using nova master 
branch.

  
  I added simple patch to forbidden creating new instances over quota, but it's 
should be changed and it's not working correctly with --min-count/--max-count 
parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538169/+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 1528756] Re: nova instance was read-only mode

[Augustina Ragwitz]

Juno is EOL [1] so we aren't doing fixes for it anymore. I've cosed this
as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.

References:
--
[1] http://docs.openstack.org/releases/

** Changed in: nova
 Assignee: Elhay Efrat (elhayefrat) => (unassigned)

** Tags removed: volumes

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

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

Title:
  nova instance was read-only mode

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Our Openstack brief Information & Issue

  1. Version : Juno

  2. Management(Nova, CInder, LB etc) & Compute Node OS ver : Ubuntu
  14.04

  3. H/W Model
   - Management Server : Dell R720
   - Compute Node : HP C7000 (Blade 460C *6ea)
   - Storage : Netapp FAS 8020
   - Switch : Nexus 4568

  4. Issues
   - nova instance was read-only mode.
   - then we did reboot all instances except for Bootable Volume Instances.
   - I have thought that the NAS volume what have nova instance images 
temporarily disconnected.

  there are two Instance type we have
   1) First type instance(OS) is launched from nfs (glance images)
   2) Second is installed by cinder volume (Bootable Volume OS)

  5. cause analysis
   - After Rebooting instances, all instances were normal status.
   - But there were no logs about NFS N/W disconnection in Compute Node, 
Storage, Switch.
   -  And no Performance Issues (CPU, MEM, Disk IO, N/W traffic)

   - VM kernel I/O Error log
  kernel: end_request: I/O error, dev vda, sector 12523664
  kernel: Buffer I/O error on device dm-1, logical block 388370
  kernel: lost page write due to I/O error on dm-1
  kernel: end_request: I/O error, dev vda, sector 36124456
  kernel: Buffer I/O error on device dm-1, logical block 3338469
  kernel: lost page write due to I/O error on dm-1

  6. etc
  - nfs client version
  # dpkg -l |grep nfs
  ii  libnfsidmap2:amd640.25-5  
  amd64NFS idmapping library
  ii  nfs-common1:1.2.8-6ubuntu1.1  
  amd64NFS support files common to client and server

  What is causing NFS temporary disconnection?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1528756/+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 1515727] Re: nova list/show does not show floatingip information updated from horizon

[Augustina Ragwitz]

Juno is EOL [1] so we aren't doing fixes for it anymore. I've cosed this
as invalid, but if you still have this issue in a later, supported
release, please feel free to reopen this issue and provide the updated
version details of your environment in the description.

References:
--
[1] http://docs.openstack.org/releases/

** Tags removed: solaris

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

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

Title:
  nova list/show does not show floatingip information updated from
  horizon

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  
  Using Solaris 11.3 with Juno (0.2014.2.2)

  When I associate a floating-ip address using Horizon, the ip does not
  appear in nova show or nova list until after I have issued a 'nova
  refresh-network' on the instance (or until I do a 'nova reboot').

  However 'nova floating-ip-list' does correctly show the floating ip as
  associated, as does horizon and 'neutron floatingip-list'

  If I make the association using 'nova floating-ip-associate' no
  refresh-network is required.

  
  The same issue arises with disassociating a floating-ip. 

  The issue appears to be that 'nova list/show' read from the
  nova.instance_info_caches table and when the floating ip is associated
  via horizon that cache is not updated.

  Either associating a floating ip in horizon should update this cache,
  or nova list/show should update it before displaying information.

  Specifically to reproduce:
  1. Create an instance either via command line or horizon, verify with nova 
list:
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1  | 
ACTIVE | -  | Running | internal_network=10.10.10.112   
  
  2. Associate a floating IP via horizon
  3. run 'nova list' or 'nova show' - the floating ip address will not be 
listed.
  4. 'nova floating-ip-list' will show the floating ip proving that 'nova list' 
is presenting out of date information
  nova list:
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1  | 
ACTIVE | -  | Running | internal_network=10.10.10.112   
  || 129.156.230.17  | 54c45d69-eacd-4add-a717-dc925d876053 | 10.10.10.112 | 
external_network |

  5. 'nova refresh-network' will force the cache to be updated and nova list 
will only then show the correct information.
  nova refresh-network 54c45d69-eacd-4add-a717-dc925d876053
  | 54c45d69-eacd-4add-a717-dc925d876053 | fiptest1  | 
ACTIVE | -  | Running | internal_network=10.10.10.112, 
129.156.230.17 |

  This is an inconsistency between how floating ips are associated and
  also with the information nova itself knows about an instance (show
  versus  floating-ip-list reporting different things). I would expect
  nova list to show the floating-ip without the need for refresh-network
  or a reboot since nova floating-ip-list etc. can display the correct
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1515727/+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 1538528] [NEW] Containers: swift_create_subfolder funciton removed but its still called in the code

[Itxaka Serrano]

Public bug reported:

The function swift_create_subfolder from
openstack_dashboard/api/swift.py was removed on commit
https://github.com/openstack/horizon/commit/b36a285938a0d98978eeb992f5144788d5ce11ff

but its still in the code, only in a patch that doesnt seem to be called 
anymore:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/containers/forms.py#L76


We should remove that code path if its not being used anymore.

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

Title:
  Containers: swift_create_subfolder funciton removed but its still
  called in the code

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The function swift_create_subfolder from
  openstack_dashboard/api/swift.py was removed on commit
  
https://github.com/openstack/horizon/commit/b36a285938a0d98978eeb992f5144788d5ce11ff

  but its still in the code, only in a patch that doesnt seem to be called 
anymore:
  
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/containers/forms.py#L76

  
  We should remove that code path if its not being used anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1538528/+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 1537661] Re: devstack with stable/liberty and neutron lbaas v2 is failing

[Anant Patil]

I could bring up a setup when I change the enable_plugin to include the
branch

# Load the external LBaaS plugin.
enable_plugin neutron-lbaas https://git.openstack.org/openstack/neutron-lbaas 
stable/liberty
enable_plugin octavia https://git.openstack.org/openstack/octavia stable/liberty

I was confused with the NEUTON_LBAAS_BRANCH and OCTAVIA_BRANCH and
thought they should take care of checking out the right branch.


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

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

** Changed in: octavia
   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/1537661

Title:
  devstack with stable/liberty and neutron lbaas v2 is failing

Status in devstack:
  Invalid
Status in neutron:
  Invalid
Status in octavia:
  Invalid

Bug description:
  I am using following localrc

  KEYSTONE_BRANCH=stable/liberty
  NOVA_BRANCH=stable/liberty
  GLANCE_BRANCH=stable/liberty
  CINDER_BRANCH=stable/liberty
  NEUTRON_BRANCH=stable/liberty
  HEAT_BRANCH=stable/liberty
  CEILOMETER_BRANCH=stable/liberty
  SWIFT_BRANCH=2.3.0
  OCTAVIA_BRANCH=stable/liberty
  NEUTRON_LBAAS_BRANCH=stable/liberty

  # Logging
  LOGFILE=$DEST/logs/stack.sh.log
  VERBOSE=True
  LOGDAYS=1
  LOG_COLOR=False
  SCREEN_LOGDIR=/opt/stack/logs

  # Load the external LBaaS plugin.
  enable_plugin neutron-lbaas https://git.openstack.org/openstack/neutron-lbaas
  enable_plugin octavia https://git.openstack.org/openstack/octavia

  # Pre-requisite
  ENABLED_SERVICES=rabbit,mysql,key
  # Nova
  ENABLED_SERVICES+=,n-api,n-crt,n-cpu,n-cond,n-sch
  # Glance
  ENABLED_SERVICES+=,g-api,g-reg
  # Neutron
  ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta
  # Enable LBaaS v2
  ENABLED_SERVICES+=,q-lbaasv2
  ENABLED_SERVICES+=,octavia,o-cw,o-hk,o-hm,o-api
  # Cinder
  ENABLED_SERVICES+=,c-api,c-vol,c-sch
  # Heat
  ENABLED_SERVICES+=,h-api,h-api-cfn,h-eng
  # Tempest
  ENABLED_SERVICES+=,tempest   

  
  neutron fails to start with "Plugin not found" error and hence devstack fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1537661/+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 1456493] Re: the comment of pci_stats is misleading

[OpenStack Infra]

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

commit a54f10a0c2fd5f8c3e5d0068eb8b830d34fa9b63
Author: karimb 
Date:   Wed Jun 10 00:09:51 2015 +0200

Fix misleading comment of pci_stats

make sure the comment around pci_stats reports the correct type for this 
variable

Change-Id: I889c0b3cf84685f529ec0ef6062b4ec658ff8269
Closes-Bug: 1456493


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

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

Title:
  the comment of pci_stats is misleading

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Version: Juno 2014.2.1
  In nova/db/sqlalchemy/Models.py,  there is a variable pci_stats in class 
ComputeNode

  # Note(yongli): json string PCI Stats
  # '{"vendor_id":"8086", "product_id":"1234", "count":3 }'
  pci_stats = Column(Text)
  In fact,  the type of pci_stats is not  dict.  the type is list.

  so I suggect modification as follow 
  # Note(yongli): json string PCI Stats
  # '[{"vendor_id":"8086", "product_id":"1234", "count":3 }, ...]'
  pci_stats = Column(Text)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1456493/+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 1516283] Re: API extension is an Abstract Class but doesn't use abstractmethod

[OpenStack Infra]

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

commit 6f0cadc380f64e6efad8b41b29cbe82a4afb5097
Author: Gerard Braad 
Date:   Fri Jan 15 04:14:32 2016 +

Decorate methods in ExtensionDescriptor with abstractmethod

Change-Id: I1cbde0c622d5595664f8547284c2c765de2f4c70
Closes-Bug:1516283


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

Title:
  API extension is an Abstract Class but doesn't use abstractmethod

Status in neutron:
  Fix Released

Bug description:
  ExtensionDescriptor in neutron/api/extensions.py is ABC class but
  methods are not decorated with abstractmethod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1516283/+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 1534644] Re: 'Nova restore ' accepts only ID of server, not its name

[OpenStack Infra]

Reviewed:  https://review.openstack.org/272508
Committed: 
https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=6791a8be69529cc9557761183ea8cb00d253fe51
Submitter: Jenkins
Branch:master

commit 6791a8be69529cc9557761183ea8cb00d253fe51
Author: jichenjc 
Date:   Sat Jan 23 22:06:48 2016 +0800

Allow restore command with name param

when we try to restore an instance, it's already deleted state,
so we need to add 'delete=True' as default to restore command,
otherwise, the search function can't find the instance
whose state is deleted with the given name

Change-Id: I81cdc46897d76333452069a691824264ad504518
Closes-Bug: 1534644


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

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

Title:
  'Nova restore ' accepts only ID of server, not its name

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

Bug description:
  For softly-deleted instance 'nova restore ' command returns:
  root@node-7:~# nova restore vm1
  ERROR (CommandError): No server with a name or ID of 'vm1' exists.

  Steps to reproduce:

  1. On every controller and compute add the
  reclaim_instance_interval=86400 line to [DEFAULT] section of
  /etc/nova/nova.conf

  2. Restart nova-api service on controllers and nova-compute service on
  computes

  3. Create net01: net01__subnet, 192.168.1.0/24:
  neutron net-create net01
  neutron subnet-create net01 192.168.1.0/24 --enable-dhcp --name net01__subnet

  4. Boot instance vm1 in net01:
  NET_ID=$(neutron net-list | grep 'net01' | awk '{print $2}')
  nova boot --flavor m1.micro --image TestVM --nic net-id=$NET_ID  
--security-groups default vm1

  5. Create a volume and attach it to an instance vm1:
  cinder create 10 --display-name test-volume --availability-zone nova
  VM_ID=$(nova show vm1 | grep '| id ' | awk  '{print $4}')
  VOL_ID=$(cinder list | grep 'test-volume'| awk '{print $2}')
  nova volume-attach $VM_ID $VOL_ID /dev/vdb

  6. Delete instance vm1:
  nova delete vm1

  7. Check that instance vm1 is really in SOFT-DELETE state:
  root@node-7:~# curl -s -H "X-Auth-Token: $TOKEN" 
$NOVA_ENDPOINT/servers/395ae0d7-59d9-4475-876d-3da1d0acc430
  {"server": {"status": "SOFT_DELETED", "updated": "2016-01-15T14:57:10Z", 
"hostId": "4ab2af2839510dd4a32c0c0225646b8ce4d865161930fd9d0d075c68", 
"OS-EXT-SRV-ATTR:host": "node-9.test.domain.local", "addresses": {"net01": 
[{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:b6:98:bc", "version": 4, "addr": 
"192.168.1.43", "OS-EXT-IPS:type": "fixed"}]}, "links": [{"href": 
"http://10.109.13.3:8774/v2/65d0c9e644ac4c518e76bc9922ef47ee/servers/395ae0d7-59d9-4475-876d-3da1d0acc430";,
 "rel": "self"}, {"href": 
"http://10.109.13.3:8774/65d0c9e644ac4c518e76bc9922ef47ee/servers/395ae0d7-59d9-4475-876d-3da1d0acc430";,
 "rel": "bookmark"}], "key_name": null, "image": {"id": 
"06c7e85d-5023-43ef-a738-8f9aef71fd7a", "links": [{"href": 
"http://10.109.13.3:8774/65d0c9e644ac4c518e76bc9922ef47ee/images/06c7e85d-5023-43ef-a738-8f9aef71fd7a";,
 "rel": "bookmark"}]}, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": 
"soft-delete", "OS-EXT-SRV-ATTR:instance_name": "instance-004b", 
"OS-SRV-USG:launched_at": "2016-01-15T1
 4:53:52.00", "OS-EXT-SRV-ATTR:hypervisor_hostname": 
"node-9.test.domain.local", "flavor": {"id": 
"11ecb4f1-144a-4bb9-96ff-89bedcd5acde", "links": [{"href": 
"http://10.109.13.3:8774/65d0c9e644ac4c518e76bc9922ef47ee/flavors/11ecb4f1-144a-4bb9-96ff-89bedcd5acde";,
 "rel": "bookmark"}]}, "id": "395ae0d7-59d9-4475-876d-3da1d0acc430", 
"security_groups": [{"name": "default"}], "OS-SRV-USG:terminated_at": null, 
"OS-EXT-AZ:availability_zone": "nova", "user_id": 
"7f0fce3a7e3f479b9933eff3df35649d", "name": "vm1", "created": 
"2016-01-15T14:53:17Z", "tenant_id": "65d0c9e644ac4c518e76bc9922ef47ee", 
"OS-DCF:diskConfig": "MANUAL", "os-extended-volumes:volumes_attached": [{"id": 
"ebcbb2f9-5125-4ef7-a507-3b7dfaa997bd"}], "accessIPv4": "", "accessIPv6": "", 
"OS-EXT-STS:power_state": 4, "config_drive": "", "metadata": {}}}root@node-7:~# 
nova restore 395ae0d7-59d9-4475-876d-3da1d0acc430

  8. Try to restore the previously-deleted instance with its name as an 
argument:
  nova restore vm1
  The result is:
  ERROR (CommandError): No server with a name or ID of 'vm1' exists

  9. Try to restore the previously-deleted instance again with its  ID as an 
argument:
  nova restore 395ae0d7-59d9-4475-876d-3da1d0acc430
  The result is:
  root@node-7:~# nova list | grep vm1
  | 395ae0d7-59d9-4475-876d-3da1d0acc430 | vm1  | ACTIVE | -  | Running 
| net01=192.168.1.43 |

  In total,
  Expected result: both name and ID of server are accepted and processed 
correctly by 'nova restore' command
  Actual result: only ID of server is accepted, not its name

  Nova version - 

[Yahoo-eng-team] [Bug 1504166] Re: Update network with New Qos-Policy isn't working with SR-IOV agent

[OpenStack Infra]

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

commit 7084fa8a17510a7a1a5221736fb3bd330b0ad86c
Author: Yalei Wang 
Date:   Mon Nov 30 22:13:08 2015 +0800

Add network_update RPC into SR-IOV agent

SR-IOV agent doesn't listen for network_update notification, but it's
desired in QOS when network updated with a new QOS policy. This patch
adds it into this agent.

Change-Id: I06a7ca411da31bccabddec9c0adca6b8e6eab7cc
Closes-Bug: #1504166


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

Title:
  Update network with New Qos-Policy isn't working with SR-IOV agent

Status in neutron:
  Fix Released

Bug description:
  The User try to switch Qos-Policy on Exist Network to another Qos-
  Policy.

  #neutron net-update network_1 --qos-policy Policy_BW_5G_4G

  No Indication in log, The "update" Action Failed!

  My Environment:

  - 2 Servers (All in one and Compute).
  - OS : CentOS Linux release 7.1.1503 (Core)
  - Kernel version : 3.10.0-123.el7.x86_64
  - Openstack Version : Trunk

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1504166/+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 1538169] Re: Quota_server_group_members parameter is not respected by nova

[Dan P]

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

Title:
  Quota_server_group_members parameter is not respected by nova

Status in OpenStack Compute (nova):
  New

Bug description:
  When I create instances which I want to be in the same server group
  (--hint group=)  with parameter: --num-instances or --min-count
  /--max-count   and I have quota_server_group_members set to 5, nova is
  spawning all instances regardless quota.

   Example:
  nova boot --image $image --flavor small  --hint 
group=528ff1e3-5a6d-475c-826e-c70d7a56e769 --nic net-id= --min-count=2 
--max-count=10  test-instance

  All Instances has spawned correct. In next request I have an error:
  ERROR (Forbidden): Quota exceeded, too many servers in group (HTTP 403) 
(Request-ID: req-f8aa39cd-2a14-486d-95a9-747ed9eecbfc)

  
  Normally request which should spawn 10 instances (but quota is set to 5) 
should give an error with Quota exceeded.
  The same situation is with  --num-instances parameter.

  
  I check it many times in Juno release and on devstack using nova master 
branch.

  
  I added simple patch to forbidden creating new instances over quota, but it's 
should be changed and it's not working correctly with --min-count/--max-count 
parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538169/+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 1537076] Re: Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

[Dmitry Tantsur]

New finding: it looks like keystone does not even start when the failure
happens. We should probably NOT fail Nova on start up if we can't
connect to it...

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

** Tags added: ironic

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

Title:
  Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova
  Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

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

Bug description:
  e.g. seems like http://logs.openstack.org/61/246161/12/check/gate-
  tempest-dsvm-ironic-pxe_ipa-
  ipxe/169b905/logs/screen-n-cpu.txt.gz?#_2016-01-22_09_01_00_240 causes
  http://logs.openstack.org/61/246161/12/check/gate-tempest-dsvm-ironic-
  pxe_ipa-ipxe/169b905/logs/devstacklog.txt.gz#_2016-01-22_09_08_19_910

  Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 
115, in wait
  listener.cb(fileno)
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 
214, in main
  result = function(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_service/service.py", line 
671, in run_service
  service.start()
File "/opt/stack/new/nova/nova/service.py", line 198, in start
  self.manager.pre_start_hook()
File "/opt/stack/new/nova/nova/compute/manager.py", line 1340, in 
pre_start_hook
  self.update_available_resource(nova.context.get_admin_context())
File "/opt/stack/new/nova/nova/compute/manager.py", line 6290, in 
update_available_resource
  nodenames = set(self.driver.get_available_nodes())
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 554, in 
get_available_nodes
  self._refresh_cache()
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 537, in 
_refresh_cache
  for node in self._get_node_list(detail=True, limit=0):
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 476, in 
_get_node_list
  node_list = self.ironicclient.call("node.list", **kwargs)
File "/opt/stack/new/nova/nova/virt/ironic/client_wrapper.py", line 136, in 
call
  client = self._get_client(retry_on_conflict=retry_on_conflict)
File "/opt/stack/new/nova/nova/virt/ironic/client_wrapper.py", line 86, in 
_get_client
  cli = ironic.client.get_client(CONF.ironic.api_version, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/ironicclient/client.py", line 
86, in get_client
  _ksclient = _get_ksclient(**ks_kwargs)
File "/usr/local/lib/python2.7/dist-packages/ironicclient/client.py", line 
35, in _get_ksclient
  insecure=kwargs.get('insecure'))
File 
"/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 
166, in __init__
  self.authenticate()
File "/usr/local/lib/python2.7/dist-packages/keystoneclient/utils.py", line 
337, in inner
  return func(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/keystoneclient/httpclient.py", 
line 589, in authenticate
  resp = self.get_raw_token_from_identity_service(**kwargs)
File 
"/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 
210, in get_raw_token_from_identity_service
  _("Authorization Failed: %s") % e)
  AuthorizationFailure: Authorization Failed: Unable to establish connection to 
http://127.0.0.1:35357/v2.0/tokens

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1537076/+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 1538565] [NEW] Guest CPU does not support 1Gb hugepages with explicit models

[Tapio Tallgren]

Public bug reported:

The CPU flag pdpe1gb indicates that the CPU model supports 1 GB
hugepages - without it, the Linux operating system refuses to allocate 1
GB huge pages (and other things might go wrong if it did).

Not all Intel CPU models support 1 GB huge pages, so the qemu options
-cpu Haswell and -cpu Broadwell give you a vCPU that does not have the
pdpe1gb flag. This is the correct thing to do, since the VM might be
running on a Haswell that does not have 1GB huge pages.

Problem is that Nova flavor extra specs with the libvirt driver for
qemu/kvm only allow to define the CPU model, either an explicit model or
"host". The host option means that all CPU flags in the host CPU are
passed to the vCPU. However, the host option complicates VM migration
since the CPU would change after migration.

In conclusion, there is no good way to specify a CPU model that would
imply the pdpe1gb flag.

Huge pages are used eg with dpdk. They improve the performance of the VM
mainly by reducing tlb size.

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

Title:
  Guest CPU does not support 1Gb hugepages with explicit models

Status in OpenStack Compute (nova):
  New

Bug description:
  The CPU flag pdpe1gb indicates that the CPU model supports 1 GB
  hugepages - without it, the Linux operating system refuses to allocate
  1 GB huge pages (and other things might go wrong if it did).

  Not all Intel CPU models support 1 GB huge pages, so the qemu options
  -cpu Haswell and -cpu Broadwell give you a vCPU that does not have the
  pdpe1gb flag. This is the correct thing to do, since the VM might be
  running on a Haswell that does not have 1GB huge pages.

  Problem is that Nova flavor extra specs with the libvirt driver for
  qemu/kvm only allow to define the CPU model, either an explicit model
  or "host". The host option means that all CPU flags in the host CPU
  are passed to the vCPU. However, the host option complicates VM
  migration since the CPU would change after migration.

  In conclusion, there is no good way to specify a CPU model that would
  imply the pdpe1gb flag.

  Huge pages are used eg with dpdk. They improve the performance of the
  VM mainly by reducing tlb size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538565/+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 1538572] Re: Neutron api test fails with raise TypeError("Invalid credentials")

[Matthew Treinish]

I see nothing in that stacktrace which is importing tempest. All the
code in this error is from the neutron repo

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

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

** No longer affects: tempest

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

Title:
  Neutron api test fails with raise TypeError("Invalid credentials")

Status in neutron:
  New

Bug description:
  Neutron api test case fails with below error

  2016-01-27 14:16:18.979 8049 WARNING oslo_config.cfg [-] Option 
"allow_tenant_isolation" from group "compute" is deprecated. Use option 
"allow_tenant_isolation" from group "auth".
  v2
  http://10.11.6.32:5000/v2.0/
  {'username': None, 'tenant_name': None, 'password': None, 'user_id': None, 
'tenant_id': None}
  ==
  ERROR: test suite for 
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 208, in run
  self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 291, in setUp
  self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 314, in 
setupContext
  try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
  return func()
File "/opt/stack/neutron/neutron/tests/tempest/test.py", line 260, in 
setUpClass
  cls.resource_setup()
File "/opt/stack/neutron/neutron/tests/api/test_networks.py", line 65, in 
resource_setup
  super(NetworksTestJSON, cls).resource_setup()
File "/opt/stack/neutron/neutron/tests/api/base.py", line 65, in 
resource_setup
  os = cls.get_client_manager()
File "/opt/stack/neutron/neutron/tests/tempest/test.py", line 391, in 
get_client_manager
  force_tenant_isolation=force_tenant_isolation,
File "/opt/stack/neutron/neutron/tests/tempest/common/credentials.py", line 
37, in get_isolated_credentials
  network_resources=network_resources)
File "/opt/stack/neutron/neutron/tests/tempest/common/isolated_creds.py", 
line 39, in __init__
  self._get_admin_clients())
File "/opt/stack/neutron/neutron/tests/tempest/common/isolated_creds.py", 
line 48, in _get_admin_clients
  os = clients.AdminManager()
File "/opt/stack/neutron/neutron/tests/api/clients.py", line 115, in 
__init__
  'identity_admin'),
File "/opt/stack/neutron/neutron/tests/tempest/common/cred_provider.py", 
line 64, in get_configured_credentials
  credentials = get_credentials(fill_in=fill_in, **params)
File "/opt/stack/neutron/neutron/tests/tempest/common/cred_provider.py", 
line 93, in get_credentials
  **params)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 489, in 
get_credentials
  ca_certs=ca_certs, trace_requests=trace_requests)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 188, in 
__init__
  super(KeystoneAuthProvider, self).__init__(credentials)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 42, in 
__init__
  raise TypeError("Invalid credentials")
  TypeError: Invalid credentials

  --
  Ran 0 tests in 0.016s

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538572/+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 1538572] Re: Neutron api test fails with raise TypeError("Invalid credentials")

[Assaf Muller]

Fixed with https://review.openstack.org/#/c/263400/.

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

** Changed in: neutron
 Assignee: (unassigned) => Assaf Muller (amuller)

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

Title:
  Neutron api test fails with raise TypeError("Invalid credentials")

Status in neutron:
  Fix Released

Bug description:
  Neutron api test case fails with below error

  2016-01-27 14:16:18.979 8049 WARNING oslo_config.cfg [-] Option 
"allow_tenant_isolation" from group "compute" is deprecated. Use option 
"allow_tenant_isolation" from group "auth".
  v2
  http://10.11.6.32:5000/v2.0/
  {'username': None, 'tenant_name': None, 'password': None, 'user_id': None, 
'tenant_id': None}
  ==
  ERROR: test suite for 
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 208, in run
  self.setUp()
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 291, in setUp
  self.setupContext(ancestor)
File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 314, in 
setupContext
  try_run(context, names)
File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
  return func()
File "/opt/stack/neutron/neutron/tests/tempest/test.py", line 260, in 
setUpClass
  cls.resource_setup()
File "/opt/stack/neutron/neutron/tests/api/test_networks.py", line 65, in 
resource_setup
  super(NetworksTestJSON, cls).resource_setup()
File "/opt/stack/neutron/neutron/tests/api/base.py", line 65, in 
resource_setup
  os = cls.get_client_manager()
File "/opt/stack/neutron/neutron/tests/tempest/test.py", line 391, in 
get_client_manager
  force_tenant_isolation=force_tenant_isolation,
File "/opt/stack/neutron/neutron/tests/tempest/common/credentials.py", line 
37, in get_isolated_credentials
  network_resources=network_resources)
File "/opt/stack/neutron/neutron/tests/tempest/common/isolated_creds.py", 
line 39, in __init__
  self._get_admin_clients())
File "/opt/stack/neutron/neutron/tests/tempest/common/isolated_creds.py", 
line 48, in _get_admin_clients
  os = clients.AdminManager()
File "/opt/stack/neutron/neutron/tests/api/clients.py", line 115, in 
__init__
  'identity_admin'),
File "/opt/stack/neutron/neutron/tests/tempest/common/cred_provider.py", 
line 64, in get_configured_credentials
  credentials = get_credentials(fill_in=fill_in, **params)
File "/opt/stack/neutron/neutron/tests/tempest/common/cred_provider.py", 
line 93, in get_credentials
  **params)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 489, in 
get_credentials
  ca_certs=ca_certs, trace_requests=trace_requests)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 188, in 
__init__
  super(KeystoneAuthProvider, self).__init__(credentials)
File "/opt/stack/neutron/neutron/tests/tempest/auth.py", line 42, in 
__init__
  raise TypeError("Invalid credentials")
  TypeError: Invalid credentials

  --
  Ran 0 tests in 0.016s

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538572/+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 1538619] [NEW] Fix up argument order in remove_volume_connection()

[Chris Friesen]

Public bug reported:

The RPC API function for remove_volume_connection() uses a different argument 
order than the ComputeManager function of the same name.

The normal RPC code uses named arguments, but the _ComputeV4Proxy version 
doesn't, and it has the order wrong.  This causes problems when called by 
_rollback_live_migration().

The fix seems to be trivial:
diff --git a/nova/compute/manager.py b/nova/compute/manager.py
index d6efd18..65c1b75 100644
--- a/nova/compute/manager.py
+++ b/nova/compute/manager.py
@@ -6870,7 +6870,8 @@ class _ComputeV4Proxy(object):
   instance)
 
 def remove_volume_connection(self, ctxt, instance, volume_id):
-return self.manager.remove_volume_connection(ctxt, instance, volume_id)
+# The RPC API uses different argument order than the local API.
+return self.manager.remove_volume_connection(ctxt, volume_id, instance)
 
 def rescue_instance(self, ctxt, instance, rescue_password,
 rescue_image_ref, clean_shutdown):

Given that this only applies to stable/kilo I'm guessing there's no
point in trying to push a patch, but I thought I'd include this here in
case anyone else runs into it.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: compute

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

Title:
  Fix up argument order in remove_volume_connection()

Status in OpenStack Compute (nova):
  New

Bug description:
  The RPC API function for remove_volume_connection() uses a different argument 
order than the ComputeManager function of the same name.
  
  The normal RPC code uses named arguments, but the _ComputeV4Proxy version 
doesn't, and it has the order wrong.  This causes problems when called by 
_rollback_live_migration().

  The fix seems to be trivial:
  diff --git a/nova/compute/manager.py b/nova/compute/manager.py
  index d6efd18..65c1b75 100644
  --- a/nova/compute/manager.py
  +++ b/nova/compute/manager.py
  @@ -6870,7 +6870,8 @@ class _ComputeV4Proxy(object):
 instance)
   
   def remove_volume_connection(self, ctxt, instance, volume_id):
  -return self.manager.remove_volume_connection(ctxt, instance, 
volume_id)
  +# The RPC API uses different argument order than the local API.
  +return self.manager.remove_volume_connection(ctxt, volume_id, 
instance)
   
   def rescue_instance(self, ctxt, instance, rescue_password,
   rescue_image_ref, clean_shutdown):

  Given that this only applies to stable/kilo I'm guessing there's no
  point in trying to push a patch, but I thought I'd include this here
  in case anyone else runs into it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538619/+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 1538626] [NEW] Fix trust test cases for redelegation and add test for impersonation

[Jorge Munoz]

Public bug reported:

Test under class TestTrustRedelegation in test_v3_auth.py do not test
redelegation since trust are created with impersonation set to true.
Also, no test class exist for testing impersonation.

Incorrect  boolean value:
https://github.com/openstack/keystone/blob/1e44004c4028bd314ea59a084d4c898e2815c9de/keystone/tests/unit/test_v3_auth.py#L2931

** Affects: keystone
 Importance: Undecided
 Assignee: Jorge Munoz (jorge-munoz)
 Status: New

** Changed in: keystone
 Assignee: (unassigned) => Jorge Munoz (jorge-munoz)

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

Title:
  Fix trust test cases for redelegation and add test for impersonation

Status in OpenStack Identity (keystone):
  New

Bug description:
  Test under class TestTrustRedelegation in test_v3_auth.py do not test
  redelegation since trust are created with impersonation set to true.
  Also, no test class exist for testing impersonation.

  Incorrect  boolean value:
  
https://github.com/openstack/keystone/blob/1e44004c4028bd314ea59a084d4c898e2815c9de/keystone/tests/unit/test_v3_auth.py#L2931

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1538626/+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 1538625] [NEW] glance-api.conf kilo limit

[Maurice Schreiber]

Public bug reported:

The example glance-api.conf is missing the api_limit_max and
limit_param_default [DEFAULT] parameters.

This got fixed in Liberty, but not back in Kilo, where this parameters
were already present, too.

I want to take care of the implementation myself.

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

Title:
  glance-api.conf kilo limit

Status in Glance:
  New

Bug description:
  The example glance-api.conf is missing the api_limit_max and
  limit_param_default [DEFAULT] parameters.

  This got fixed in Liberty, but not back in Kilo, where this parameters
  were already present, too.

  I want to take care of the implementation myself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1538625/+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 1538623] [NEW] lack of required extensions should be fatal

[Armando Migliaccio]

Public bug reported:

The extension framework has the ability to describe which extension
depends on which, and if the requirements are not met it's hard to see
how the server could work correctly.

[1]
https://github.com/openstack/neutron/blob/master/neutron/api/extensions.py#L443

** Affects: neutron
 Importance: Wishlist
 Assignee: Armando Migliaccio (armando-migliaccio)
 Status: Confirmed

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

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

** Changed in: neutron
 Assignee: (unassigned) => Armando Migliaccio (armando-migliaccio)

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

** Changed in: neutron
   Importance: Low => Wishlist

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

Title:
  lack of required extensions should be fatal

Status in neutron:
  Confirmed

Bug description:
  The extension framework has the ability to describe which extension
  depends on which, and if the requirements are not met it's hard to see
  how the server could work correctly.

  [1]
  
https://github.com/openstack/neutron/blob/master/neutron/api/extensions.py#L443

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538623/+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 1369465] Re: nova resize doesn't resize(extend) rbd disk files when using rbd disk backend

[Bryan Quigley]

** Also affects: nova (Ubuntu)
   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/1369465

Title:
  nova resize doesn't resize(extend) rbd disk files when using rbd disk
  backend

Status in OpenStack Compute (nova):
  Fix Released
Status in nova package in Ubuntu:
  New

Bug description:
  tested with nova trunk commit eb860c2f219b79e4f4c5984415ee433145197570

  Configured Nova to use rbd disk backend

  nova.conf

  [libvirt]
  images_type=rbd

  instances booted successfully and instance disks are in rbd pools,
  when perform a nova resize  to an existing instance,  memory and CPU
  changed to be new flavors but instance disks size doesn't change

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1538620] Re: Attach with host and instance_uuid not backwards compatible

[John Griffith]

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

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

Title:
  Attach with host and instance_uuid not backwards compatible

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  In Progress

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

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

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1538695] [NEW] sriov-mech: Introduce a new VIF type for PF vnic type

[OpenStack Infra]

Public bug reported:

https://review.openstack.org/262604
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

commit 4a431f75a01fbdd0b802c86e27a93a6daaf70399
Author: Nikola Dipanov 
Date:   Wed Dec 30 19:48:33 2015 +

sriov-mech: Introduce a new VIF type for PF vnic type

We need to tell Nova to use a specific VIF type for full PF passthrough
(this is the recently added VNIC_DIRECT_PHYSICAL vnic type).

Make sure that when binding ports with this vnic type, we set the
appropriate vif type for Nova to be able to provision those ports
correctly.

Nova change that adds a vif driver for this vif type:

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

DocImpact: Exposes a new vif type for PF passtrhough vnic type

Change-Id: I895dab98e5e5a9369771539e51ba5c500bfe0045
Related-blueprint: sriov-pf-passthrough-neutron-port

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: doc 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/1538695

Title:
  sriov-mech: Introduce a new VIF type for PF vnic type

Status in neutron:
  New

Bug description:
  https://review.openstack.org/262604
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 4a431f75a01fbdd0b802c86e27a93a6daaf70399
  Author: Nikola Dipanov 
  Date:   Wed Dec 30 19:48:33 2015 +

  sriov-mech: Introduce a new VIF type for PF vnic type
  
  We need to tell Nova to use a specific VIF type for full PF passthrough
  (this is the recently added VNIC_DIRECT_PHYSICAL vnic type).
  
  Make sure that when binding ports with this vnic type, we set the
  appropriate vif type for Nova to be able to provision those ports
  correctly.
  
  Nova change that adds a vif driver for this vif type:
  
  https://review.openstack.org/#/c/262583/
  
  DocImpact: Exposes a new vif type for PF passtrhough vnic type
  
  Change-Id: I895dab98e5e5a9369771539e51ba5c500bfe0045
  Related-blueprint: sriov-pf-passthrough-neutron-port

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

[OpenStack Infra]

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

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

commit fb8bedc3754ec5b10f3026b0f0f7afefd94e6a3a
Author: Itxaka 
Date:   Mon Jan 25 13:50:01 2016 +0100

fix ClientException call

We were calling cinder.ClientException even when the import
had changed to be cinder.cinder_exception.ClientException
Adds 3 tests for the methods calling that exception so
failures will be tested as well.

Co-Authored-By: zhurong 
Change-Id: I8c415eb8ef847f6dc34fa56fca3181560ead366b
Closes-Bug: #1537713
Closes-Bug: #1535215


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

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

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  
  In openstack_dashboard/usage/quotas.py 
(https://github.com/openstack/horizon/blob/master/openstack_dashboard/usage/quotas.py)
  there is a couple of calls to cinder.ClientException which is not the proper 
route.

  Proper route is cinder.cinder_exception.ClientException


  [25/Jan/2016 10:46:12] "GET /project/instances/launch HTTP/1.1" 200 23987
  Internal Server Error: /project/instances/launch
  Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 
132, in get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/mrunge/work/horizon/horizon/decorators.py", line 36, in dec
  return view_func(request, *args, **kwargs)
File "/home/mrunge/work/horizon/horizon/decorators.py", line 52, in dec
  return view_func(request, *args, **kwargs)
File "/home/mrunge/work/horizon/horizon/decorators.py", line 36, in dec
  return view_func(request, *args, **kwargs)
File "/home/mrunge/work/horizon/horizon/decorators.py", line 84, in dec
  return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 
71, in view
  return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 
89, in dispatch
  return handler(request, *args, **kwargs)
File "/home/mrunge/work/horizon/horizon/workflows/views.py", line 167, in 
post
  context = self.get_context_data(**kwargs)
File "/home/mrunge/work/horizon/horizon/workflows/views.py", line 91, in 
get_context_data
  workflow = self.get_workflow()
File "/home/mrunge/work/horizon/horizon/workflows/views.py", line 81, in 
get_workflow
  entry_point=entry_point)
File "/home/mrunge/work/horizon/horizon/workflows/base.py", line 651, in 
__init__
  valid = step.action.is_valid()
File "/usr/lib/python2.7/site-packages/django/forms/forms.py", line 184, in 
is_valid
  return self.is_bound and not self.errors
File "/usr/lib/python2.7/site-packages/django/forms/forms.py", line 176, in 
errors
  self.full_clean()
File "/usr/lib/python2.7/site-packages/django/forms/forms.py", line 393, in 
full_clean
  self._clean_form()
File "/usr/lib/python2.7/site-packages/django/forms/forms.py", line 417, in 
_clean_form
  cleaned_data = self.clean()
File 
"/home/mrunge/work/horizon/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py",
 line 368, in clean
  self._check_quotas(cleaned_data)
File 
"/home/mrunge/work/horizon/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py",
 line 210, in _check_quotas
  usages = quotas.tenant_quota_usages(self.request)
File "/home/mrunge/work/horizon/horizon/utils/memoized.py", line 90, in 
wrapped
  value = cache[key] = func(*args, **kwargs)
File "/home/mrunge/work/horizon/openstack_dashboard/usage/quotas.py", line 
371, in tenant_quota_usages
  tenant_id=tenant_id):
File "/home/mrunge/work/horizon/openstack_dashboard/usage/quotas.py", line 
171, in get_tenant_quota_data
  tenant_id=tenant_id)
File "/home/mrunge/work/horizon/openstack_dashboard/usage/quotas.py", line 
150, in _get_quota_data
  except cinder.ClientException:
  AttributeError: 'module' object has no attribute 'ClientException'
  [25/Jan/2016 10:46:23] "POST /project/instances/launch HTTP/1.1" 500 98732

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

[Yahoo-eng-team] [Bug 1535215] Re: AttributeError: 'module' object has no attribute 'ClientException'

[OpenStack Infra]

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

commit fb8bedc3754ec5b10f3026b0f0f7afefd94e6a3a
Author: Itxaka 
Date:   Mon Jan 25 13:50:01 2016 +0100

fix ClientException call

We were calling cinder.ClientException even when the import
had changed to be cinder.cinder_exception.ClientException
Adds 3 tests for the methods calling that exception so
failures will be tested as well.

Co-Authored-By: zhurong 
Change-Id: I8c415eb8ef847f6dc34fa56fca3181560ead366b
Closes-Bug: #1537713
Closes-Bug: #1535215


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

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

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Launch instance give the error:
File "/home/openstack/horizon-murano/horizon/utils/memoized.py", line 90, 
in wrapped
  value = cache[key] = func(*args, **kwargs)
File "/home/openstack/horizon-murano/openstack_dashboard/usage/quotas.py", 
line 371, in tenant_quota_usages
  tenant_id=tenant_id):
File "/home/openstack/horizon-murano/openstack_dashboard/usage/quotas.py", 
line 171, in get_tenant_quota_data
  tenant_id=tenant_id)
File "/home/openstack/horizon-murano/openstack_dashboard/usage/quotas.py", 
line 150, in _get_quota_data
  except cinder.ClientException:
  AttributeError: 'module' object has no attribute 'ClientException'

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535215/+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 1438822] Re: Table widget should show a default message when filtering yields no items

[OpenStack Infra]

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

commit d37f1a899679fd7efe87ffbbb0bd4d9cb4e0c44f
Author: Cindy Lu 
Date:   Mon Aug 3 15:33:12 2015 -0700

Add Angular Directive to show msg for empty tables

Ideally smart-table would have a default message when filtering
yields no results, but it does not.  This patch provides a general
directive that allows Angular tables to specify a custom message, or
uses a default "No items to display" message if not.

To test, set DISABLED = False in
 _3031_identity_users_panel.py, and/or
 _1051_project_ng_images_panel.py and/or
 _2081_admin_flavors_panel.py

Then go to the last Users panel in the Identity menu,
last Images Panel in Project menu, respectively.

Co-Authored-By: Rajat Vig 
Co-Authored-By: Cindy Lu 

Change-Id: Ia086bb791d6c74af738209795195ff3ea1860981
Closes-bug: #1438822


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

Title:
  Table widget should show a default message when filtering yields no
  items

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Currently angular tables are filterable using the smart-table feature.
  However, table widget should show a default message when filtering
  yields no items. This is currently not the case and need to be amend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1438822/+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 1403034] Re: Horizon should accept an IPv6 address as a VIP Address for LB Pool

[OpenStack Infra]

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

commit dbf251e16e9e518a85991c07d030aa8b2070c9fc
Author: nikunj2512 
Date:   Thu Dec 18 11:16:54 2014 +0530

Adds support to accept IPv6 in VIP Address for LB Pool

In VIP assignment for a LB pool, it now allows users to assign a
IPv6 IP address also.

Change-Id: I8e7f047c410cde5c13c14a18e27ed25c6c767eb5
Closes-bug: #1403034


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

Title:
  Horizon should accept an IPv6 address as a VIP Address for LB Pool

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Description of problem:
  ===
  Horizon should accept an IPv6 address as a VIP Address for LB Pool.

  Version-Release number of selected component (if applicable):
  =
  RHEL-OSP6: 2014-12-12.1
  python-django-horizon-2014.2.1-2.el7ost.noarch

  How reproducible:
  =
  Always

  Steps to Reproduce:
  ===
  0. Have an IPv6 subnet.

  1. Browse to: http:///dashboard/project/loadbalancers/

  2. Create a Load Balancing Pool.

  3. Add VIP as follows:
 - Name: test
 - VIP Subnet: Select your IPv6 subnet
 - Specify a free IP address from the selected subnet: IPv6 address such 
as: 2001:65:65:65::a
 - Protocol Port: 80
 - Protocol: HTTP
 - Admin State: UP

  Actual results:
  ===
  Error: Invalid version for IP address

  Expected results:
  =
  Should work OK, this is supported in the python-neutronclient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1403034/+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 1538740] [NEW] SIGTERM on neutron-l3 agent process causes stacktrace

[Sean M. Collins]

Public bug reported:

vagrant@vagrant-ubuntu-wily-32:/opt/stack/logs$ pkill l3


Log:

2016-01-27 20:45:39.152 14651 DEBUG neutron.agent.linux.utils [-] Exit code: 0 
execute /opt/stack/neutron/neutron/agent/linux/utils.py:142
2016-01-27 20:45:50.012 DEBUG oslo_concurrency.lockutils 
[req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Acquired semaphore 
"singleton_lock" lock 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212
2016-01-27 20:45:50.014 DEBUG oslo_concurrency.lockutils 
[req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Releasing semaphore 
"singleton_lock" lock 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225
2016-01-27 20:45:50.015 14651 ERROR oslo.messaging._drivers.impl_rabbit [-] 
Failed to consume message from queue: 'NoneType' object has no attribute 'info'
2016-01-27 20:45:50.015 14651 ERROR root [-] Unexpected exception occurred 1 
time(s)... retrying.
2016-01-27 20:45:50.015 14651 ERROR root Traceback (most recent call last):
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 234, in 
wrapper
2016-01-27 20:45:50.015 14651 ERROR root return infunc(*args, **kwargs)
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_executors/impl_pooledexecutor.py",
 line 98, in _runner
2016-01-27 20:45:50.015 14651 ERROR root 
prefetch_size=self.dispatcher.batch_size)
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/base.py", line 
45, in wrapper
2016-01-27 20:45:50.015 14651 ERROR root msg = func(in_self, 
timeout=watch.leftover(return_none=True))
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 212, in poll
2016-01-27 20:45:50.015 14651 ERROR root self.conn.consume(timeout=timeout)
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py",
 line 904, in consume
2016-01-27 20:45:50.015 14651 ERROR root error_callback=_error_callback)
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py",
 line 689, in ensure
2016-01-27 20:45:50.015 14651 ERROR root ret, channel = autoretry_method()
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 449, in 
_ensured
2016-01-27 20:45:50.015 14651 ERROR root errback and errback(exc, 0)
2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/impl_rabbit.py",
 line 625, in on_error
2016-01-27 20:45:50.015 14651 ERROR root info.update(self.connection.info())
2016-01-27 20:45:50.015 14651 ERROR root AttributeError: 'NoneType' object has 
no attribute 'info'
2016-01-27 20:45:50.015 14651 ERROR root
2016-01-27 20:45:50.021 INFO oslo_rootwrap.client 
[req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Stopping rootwrap daemon 
process with pid=14684

** Affects: neutron
 Importance: Low
 Status: New

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

** Description changed:

+ vagrant@vagrant-ubuntu-wily-32:/opt/stack/logs$ pkill l3
+ 
+ 
+ Log:
+ 
  2016-01-27 20:45:39.152 14651 DEBUG neutron.agent.linux.utils [-] Exit code: 
0 execute /opt/stack/neutron/neutron/agent/linux/utils.py:142
  2016-01-27 20:45:50.012 DEBUG oslo_concurrency.lockutils 
[req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Acquired semaphore 
"singleton_lock" lock 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212
  2016-01-27 20:45:50.014 DEBUG oslo_concurrency.lockutils 
[req-3c4051c2-ceb6-404b-9086-ccc17569bfdd None None] Releasing semaphore 
"singleton_lock" lock 
/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225
  2016-01-27 20:45:50.015 14651 ERROR oslo.messaging._drivers.impl_rabbit [-] 
Failed to consume message from queue: 'NoneType' object has no attribute 'info'
  2016-01-27 20:45:50.015 14651 ERROR root [-] Unexpected exception occurred 1 
time(s)... retrying.
  2016-01-27 20:45:50.015 14651 ERROR root Traceback (most recent call last):
  2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 234, in 
wrapper
  2016-01-27 20:45:50.015 14651 ERROR root return infunc(*args, **kwargs)
  2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_executors/impl_pooledexecutor.py",
 line 98, in _runner
  2016-01-27 20:45:50.015 14651 ERROR root 
prefetch_size=self.dispatcher.batch_size)
  2016-01-27 20:45:50.015 14651 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/base.py", line 
45, in wrapper
  2016-01-27 20:45:50.015 14651 ERROR root msg = func(in_self, 
timeout=

[Yahoo-eng-team] [Bug 1538746] [NEW] tempest v2 scenario tests not passing config to serviceclient and support netcat using cirros 0.3.3 image

[Madhusudhan Kandadai]

Public bug reported:

1. neutron-lbaas tempest v2  scenario tests doesn't pick config values
from standard tempest.conf. Instead, the config values are hardcoded in
the scenario/base.py. For example,

  self.client_args = [auth_provider, 'network', 'regionOne']

The above values doesn't work on non-devstack environment. Setting and
pick the config values from tempest.conf works both devstack and non-
devstack environment.

2. netcat doesnt support persistent listening 'll' option on cirros
0.3.3. image. hence change it to 'l' listening option, so the cloud can
use any cirros image either 3.3/3.4. Also, change the behavior of the
netcat script to make it work against 3.3.

** Affects: neutron
 Importance: Undecided
 Assignee: Madhusudhan Kandadai (madhusudhan-kandadai)
 Status: New


** Tags: lbaas

** Changed in: neutron
 Assignee: (unassigned) => Madhusudhan Kandadai (madhusudhan-kandadai)

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

Title:
  tempest v2 scenario tests not passing config to serviceclient and
  support netcat using cirros 0.3.3 image

Status in neutron:
  New

Bug description:
  1. neutron-lbaas tempest v2  scenario tests doesn't pick config values
  from standard tempest.conf. Instead, the config values are hardcoded
  in the scenario/base.py. For example,

self.client_args = [auth_provider, 'network',
  'regionOne']

  The above values doesn't work on non-devstack environment. Setting and
  pick the config values from tempest.conf works both devstack and non-
  devstack environment.

  2. netcat doesnt support persistent listening 'll' option on cirros
  0.3.3. image. hence change it to 'l' listening option, so the cloud
  can use any cirros image either 3.3/3.4. Also, change the behavior of
  the netcat script to make it work against 3.3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538746/+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 1538754] [NEW] keystone should convert host CONF.federation.trusted_dashboard to lower case before comparing

[apal]

Public bug reported:

https://github.com/openstack/keystone/blob/master/keystone/federation/controllers.py#L272
keystone should convert it to lower case before comparing

It should not be case sensitive. Otherwise some uppercase hostname would
fail to auth from browser etc.

** Affects: keystone
 Importance: Undecided
 Assignee: Roxana Gherle (roxana-gherle)
 Status: New

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

Title:
  keystone should convert host CONF.federation.trusted_dashboard to
  lower case before comparing

Status in OpenStack Identity (keystone):
  New

Bug description:
  
https://github.com/openstack/keystone/blob/master/keystone/federation/controllers.py#L272
  keystone should convert it to lower case before comparing

  It should not be case sensitive. Otherwise some uppercase hostname
  would fail to auth from browser etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1538754/+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 1538767] [NEW] Users cannot create extra-routes with nexthop on ext-net

[Cedric Brandily]

Public bug reported:

Non-admin users cannot create extra-routes on a router with a nexthop on
ext-net subnet:

  # With admin user
  neutron net-create pub --router-:external
  neutron subnet-create pub 192.168.0.0/16

  # With non-admin user
  neutron router-create router
  neutron router-gateway-set router pub
  neutron router-update router --routes 
nexthop=192.168.0.99,destination=10.10.10.0/24
  >> Invalid format for routes: [{u'destination': u'10.10.10.0/24', u'nexthop': 
u'192.168.0.99'}], the nexthop is not connected with router

But it succeeds with an admin user.

nexthop validation gets all ports connected to the router to check if
nexthop is on a subnet connected to the router BUT non-admin users are
only allowed to get internal ports!

** Affects: neutron
 Importance: Undecided
 Assignee: Cedric Brandily (cbrandily)
 Status: New


** Tags: l3-ipam-dhcp

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

Title:
  Users cannot create extra-routes with nexthop on ext-net

Status in neutron:
  New

Bug description:
  Non-admin users cannot create extra-routes on a router with a nexthop
  on ext-net subnet:

# With admin user
neutron net-create pub --router-:external
neutron subnet-create pub 192.168.0.0/16

# With non-admin user
neutron router-create router
neutron router-gateway-set router pub
neutron router-update router --routes 
nexthop=192.168.0.99,destination=10.10.10.0/24
>> Invalid format for routes: [{u'destination': u'10.10.10.0/24', 
u'nexthop': u'192.168.0.99'}], the nexthop is not connected with router

  But it succeeds with an admin user.

  nexthop validation gets all ports connected to the router to check if
  nexthop is on a subnet connected to the router BUT non-admin users are
  only allowed to get internal ports!

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538767/+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 1537076] Re: Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

[OpenStack Infra]

Reviewed:  https://review.openstack.org/273129
Committed: 
https://git.openstack.org/cgit/openstack/ironic/commit/?id=fde62528afd5c88737999a3deabeba6c2d389e88
Submitter: Jenkins
Branch:master

commit fde62528afd5c88737999a3deabeba6c2d389e88
Author: Dmitry Tantsur 
Date:   Wed Jan 27 17:10:58 2016 +0100

[devstack] Restart nova compute before checking hypervisor stats

Nova compute may fail if it was unable to fetch nodes list from Ironic
during startup. This change makes sure we restart it.

Change-Id: Ibddd34faa0eeb9b42fe0e8d73f14907b1df11734
Closes-Bug: #1537076


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

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

Title:
  Timed out waiting for Nova hypervisor-stats count >= 1 due to Nova
  Unable to establish connection to http://127.0.0.1:35357/v2.0/tokens

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

Bug description:
  e.g. seems like http://logs.openstack.org/61/246161/12/check/gate-
  tempest-dsvm-ironic-pxe_ipa-
  ipxe/169b905/logs/screen-n-cpu.txt.gz?#_2016-01-22_09_01_00_240 causes
  http://logs.openstack.org/61/246161/12/check/gate-tempest-dsvm-ironic-
  pxe_ipa-ipxe/169b905/logs/devstacklog.txt.gz#_2016-01-22_09_08_19_910

  Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 
115, in wait
  listener.cb(fileno)
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 
214, in main
  result = function(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_service/service.py", line 
671, in run_service
  service.start()
File "/opt/stack/new/nova/nova/service.py", line 198, in start
  self.manager.pre_start_hook()
File "/opt/stack/new/nova/nova/compute/manager.py", line 1340, in 
pre_start_hook
  self.update_available_resource(nova.context.get_admin_context())
File "/opt/stack/new/nova/nova/compute/manager.py", line 6290, in 
update_available_resource
  nodenames = set(self.driver.get_available_nodes())
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 554, in 
get_available_nodes
  self._refresh_cache()
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 537, in 
_refresh_cache
  for node in self._get_node_list(detail=True, limit=0):
File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 476, in 
_get_node_list
  node_list = self.ironicclient.call("node.list", **kwargs)
File "/opt/stack/new/nova/nova/virt/ironic/client_wrapper.py", line 136, in 
call
  client = self._get_client(retry_on_conflict=retry_on_conflict)
File "/opt/stack/new/nova/nova/virt/ironic/client_wrapper.py", line 86, in 
_get_client
  cli = ironic.client.get_client(CONF.ironic.api_version, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/ironicclient/client.py", line 
86, in get_client
  _ksclient = _get_ksclient(**ks_kwargs)
File "/usr/local/lib/python2.7/dist-packages/ironicclient/client.py", line 
35, in _get_ksclient
  insecure=kwargs.get('insecure'))
File 
"/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 
166, in __init__
  self.authenticate()
File "/usr/local/lib/python2.7/dist-packages/keystoneclient/utils.py", line 
337, in inner
  return func(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/keystoneclient/httpclient.py", 
line 589, in authenticate
  resp = self.get_raw_token_from_identity_service(**kwargs)
File 
"/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 
210, in get_raw_token_from_identity_service
  _("Authorization Failed: %s") % e)
  AuthorizationFailure: Authorization Failed: Unable to establish connection to 
http://127.0.0.1:35357/v2.0/tokens

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1537076/+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 1526244] Re: Able to create objects by admin in the particular domain, for incorrect domain Id field name "domain-id".

[OpenStack Infra]

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

commit 93788e057b26dd05bb50c93d10196d5b9d5f6bed
Author: Dolph Mathews 
Date:   Wed Dec 16 16:05:45 2015 +

Test hyphens instead of underscores in request attributes

This illustrates the current behavior described in bug 1526244 (which
Keystone has implemented since essex). Right or wrong, this patch makes
no attempt to change that behavior.

Change-Id: I136aa0490ddb3e0ca210f7e61d8bbb7052c972ba
Closes-Bug: 1526244


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

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

Title:
  Able to create objects by admin in the particular domain, for
  incorrect domain Id field name "domain-id".

Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  Admin is able to create objects(user,group,.) in a particular domain,
  though field name is misspelt as "domain-id" instead of "domain_id".

  Step Followed: User creation by admin with incorrect field name
  "domain-id"

  ubuntu@ubuntu:~$ curl -i -k -X POST -H "Content-Type: application/json" -H 
"X-AUTH-TOKEN:ae5ed453cf444969953850532cb9b581" /v3/users -d '{
  > "user":
  > {
  > "name":"User Pwr Ranger 50",
  > "password":"pwd",
  > "description":"User Creation in another domain",
  > "domain-id":"37a09709db404e7d97f8a211ebebc93f"
  > }
  > }'
  HTTP/1.1 201 Created
  Date: Fri, 13 Nov 2015 12:38:22 GMT
  Server: Apache/2.4.7 (Ubuntu)
  Vary: X-Auth-Token
  x-openstack-request-id: req-1cc05a23-065f-4a25-9fcd-90fa827722d3
  Content-Length: 290
  Content-Type: application/json

  {"user": {"links": {"self":
  "/v3/users/90776556002948dfb44227aef3b042e7"},
  "description": "User Creation in another domain", "name": "User Pwr
  Ranger 50", "enabled": true, "id": "90776556002948dfb44227aef3b042e7",
  "domain_id": "37a09709db404e7d97f8a211ebebc93f"}}

  The user got created in a specified domain "domain-
  id":"37a09709db404e7d97f8a211ebebc93f", even though domain Id field is
  misspelt as "domain-id" instead of "domain_id".

  Hence the issue has to be resolved by creating objects in "default"
  domain when the field name is spelt wrongly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1526244/+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 1536535] Re: global requirement sync should be enable for specs repo

[Ghanshyam Mann]

Yea, manually  updating specs repo seems better approach. because of
unnecessary addition of doc dependency in g-r.

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

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

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

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

Title:
  global requirement sync should be enable for specs repo

Status in Mistral:
  Invalid
Status in OpenStack Compute (nova):
  Invalid
Status in tempest:
  Invalid

Bug description:
  All OpenStack projects spec repo are using requirements and those are
  not automatically synced from global requirement.

  specs repo requirement should be up to date with g-r

To manage notifications about this bug go to:
https://bugs.launchpad.net/mistral/+bug/1536535/+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 1538837] [NEW] raise ComputeServiceNotExist instead of ComputeServiceUnavailable if host is not found

[javeme]

Public bug reported:

raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
host is not found.

When performing a live migration, I passed a wrong host parameter, and then I 
got a wrong result like this:
"Compute service of host-1 is unavailable at this time".
I thought the compute service stopped, but the fact was I passed a host id 
instead of a host name, therefore it could not find the host.

In order to distinguish the error "host not found" from the error
"service not available", I think we should raise a different exception
like ComputeServiceNotExist.

** Affects: nova
 Importance: Undecided
 Assignee: javeme (javaloveme)
 Status: In Progress

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

Title:
  raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
  host is not found

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  raise ComputeServiceNotExist instead of ComputeServiceUnavailable if
  host is not found.

  When performing a live migration, I passed a wrong host parameter, and then I 
got a wrong result like this:
  "Compute service of host-1 is unavailable at this time".
  I thought the compute service stopped, but the fact was I passed a host id 
instead of a host name, therefore it could not find the host.

  In order to distinguish the error "host not found" from the error
  "service not available", I think we should raise a different exception
  like ComputeServiceNotExist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538837/+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 1532068] Re: Quota: Set total instances be unlimited but "no quota" displayed

[OpenStack Infra]

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

commit f2e990632def6fdf391c3bbb036d6c4922c4a160
Author: Bo Wang 
Date:   Fri Jan 8 11:39:43 2016 +0800

Replace "no quota" with "No Limit"

Modify project quota, set value of instances be unlimited.
On ng-launchinstance page, "Total Instances (no quota)" displayed
that confuse user.

Change it to "No Limit" which is consistent with what displayed
on Project/Compute/Overview page.
refer to: https://github.com/openstack/horizon/blob/master/
horizon/templates/horizon/common/_limit_summary.html#L23

Change-Id: Ia536933a4c30be246adf81787991019ca6a1ef56
Closes-Bug: #1532068


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

Title:
  Quota: Set total instances be unlimited but "no quota" displayed

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Modify project quota, set value of instances be unlimited.
  Create vm in ng-launchinstance page, it displayed "Total Instances (no 
quota)",  that make user misunderstood.

  IMO,  "Total Instances (No Limit)" is better that is consistent with what 
displayed in Project/Compute/Overview page.
  refer to: 
https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/common/_limit_summary.html#L23

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1532068/+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 1538896] [NEW] nova flavor-show raises 500 error if flavor is deleted

[Abhishek Kekane]

Public bug reported:

Reproducible on latest master.

Tried to show deleted flavor then it raises 500 error.

Steps to reproduce:

1. Create flavor
$ nova flavor-create m2.test 10 1200 12 8

2. Delete flavor
$ nova flavor-delete 10

3. Show deleted flavor
$ nova flavor-show 10

ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: req-
4f77f74c-2234-4beb-9875-157364bdd964)

Nova api logs:
-

 from (pid=31454) _http_log_response 
/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:254
2016-01-27 15:28:14.067 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Calling method '>' from (pid=31454) _process_stack 
/opt/stack/nova/nova/api/openstack/wsgi.py:699
2016-01-27 15:28:14.082 ERROR nova.api.openstack.extensions 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Unexpected exception in 
API method
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions return f(*args, 
**kwargs)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/compute/flavors_extraspecs.py", line 60, in 
index
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions return 
self._get_extra_specs(context, flavor_id)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/compute/flavors_extraspecs.py", line 39, in 
_get_extra_specs
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions flavor = 
common.get_flavor(context, flavor_id)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/common.py", line 543, in get_flavor
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions raise 
exc.HTTPNotFound(explanation=error.format_message())
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions HTTPNotFound: 
Flavor 122 could not be found.
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions
2016-01-27 15:28:14.085 INFO nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] HTTP exception thrown: 
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and 
attach the Nova API log if possible.

2016-01-27 15:28:14.086 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Returning 500 to user: 
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and 
attach the Nova API log if possible.
 from (pid=31454) __call__ 
/opt/stack/nova/nova/api/openstack/wsgi.py:1070
2016-01-27 15:28:14.097 INFO nova.osapi_compute.wsgi.server 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] 10.69.4.177 "GET 
/v2.1/982e2fc081364cf889d959b27d4bd510/flavors/122/os-extra_specs HTTP/1.1" 
status: 500 len: 499 time: 0.1559708

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  nova flavor-show  raises 500 error if flavor is deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  Reproducible on latest master.

  Tried to show deleted flavor then it raises 500 error.

  Steps to reproduce:

  1. Create flavor
  $ nova flavor-create m2.test 10 1200 12 8

  2. Delete flavor
  $ nova flavor-delete 10

  3. Show deleted flavor
  $ nova flavor-show 10

  ERROR (ClientException): Unexpected API Error. Please report this at
  http://bugs.launchpad.net/nova/ and attach the Nova API log if
  possible.  (HTTP 500) (Request-ID:
  req-4f77f74c-2234-4beb-9875-157364bdd964)

  Nova api logs:
  -

   from (pid=31454) _http_log_response 
/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:254
  2016-01-27 15:28:14.067 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Calling method '>' from (pid=31454) _process_stack 
/opt/stack/nova/nova/api/openstack/wsgi.py:699
  2016-01-27 15:28:14.082 ERROR nova.api.openstack.extensions 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Unexpected exception in 
API method
  2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
  2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
  2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions return 
f(*args, **kwargs)
  2016-01-27 15:28:14.082 

[Yahoo-eng-team] [Bug 1534048] [NEW] there is useless 'u' in the error info of "glance member-update"

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Summary]
there is useless 'u' in the error info of "glance member-update"

[Topo]
devstack all-in-one node

[Description and expect result]
no useless 'u' in the error info of "glance member-update"

[Reproduceable or not]
reproduceable 

[Recreate Steps]
1) there is useless 'u' in the error info of "glance member-update":
root@45-59:/opt/stack/devstack# glance member-update 
d362e24d-3d77-42ea-96ae-d1a1721e7d41 ebbcdabd911340efa9a3430488c43304 active
usage: glance member-update   
glance member-update: error: argument : invalid choice: 
u'active' (choose from 'accepted', 'rejected', 'pending')
root@45-59:/opt/stack/devstack#


[Configration]
reproduceable bug, no need

[logs]
reproduceable bug, no need

[Root cause anlyze or debug inf]
reproduceable bug

[Attachment]
None

** Affects: glance
 Importance: Undecided
 Assignee: linwei,wu (wlwwu)
 Status: New

-- 
there is useless 'u' in the error info of "glance member-update"
https://bugs.launchpad.net/bugs/1534048
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to Glance.

-- 
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 1534048] Re: there is useless 'u' in the error info of "glance member-update"

[linwei,wu]

** Project changed: python-glanceclient => glance

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

Title:
  there is useless 'u' in the error info of "glance member-update"

Status in Glance:
  New

Bug description:
  [Summary]
  there is useless 'u' in the error info of "glance member-update"

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  no useless 'u' in the error info of "glance member-update"

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) there is useless 'u' in the error info of "glance member-update":
  root@45-59:/opt/stack/devstack# glance member-update 
d362e24d-3d77-42ea-96ae-d1a1721e7d41 ebbcdabd911340efa9a3430488c43304 active
  usage: glance member-update   
  glance member-update: error: argument : invalid choice: 
u'active' (choose from 'accepted', 'rejected', 'pending')
  root@45-59:/opt/stack/devstack#


  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1534048/+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 1538913] [NEW] failed to attach interface for instance and then interface is deleted

[zhanghaixia]

Public bug reported:

1. version: openstack-nova-novncproxy-2015.1.2
   openstack-nova-console-2015.1.2
   openstack-nova-scheduler-2015.1.2
   openstack-nova-api-2015.1.2
   openstack-nova-compute-2015.1.2
   openstack-nova-cert-2015.1.2

   python-novaclient-2.23.0

2.Reproduce steps:
* create new port 
* the port is attached to the instance
* when failed to attach, the port is deleted

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

Title:
  failed to  attach interface for  instance  and then interface is
  deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  1. version: openstack-nova-novncproxy-2015.1.2
 openstack-nova-console-2015.1.2
 openstack-nova-scheduler-2015.1.2
 openstack-nova-api-2015.1.2
 openstack-nova-compute-2015.1.2
 openstack-nova-cert-2015.1.2

 python-novaclient-2.23.0

  2.Reproduce steps:
  * create new port 
  * the port is attached to the instance
  * when failed to attach, the port is deleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1538913/+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 1538932] [NEW] source.scss file does not take effect since it does not match source.html

[Wang Bo]

Public bug reported:

openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/source/source.html:

  ...


But currently the source.scss is:
[ng-controller="LaunchInstanceSourceController"] {
  td.hi-light {
color: #0084d1;
  }
  ...
}

Any change of scss file(such as:  color: red) does not take effect since
the two files do not match.

** Affects: horizon
 Importance: Undecided
 Assignee: Wang Bo (chestack)
 Status: In Progress

** Changed in: horizon
 Assignee: (unassigned) => Wang Bo (chestack)

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

Title:
  source.scss file does not take effect since it  does not match
  source.html

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  
openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/source/source.html:
  
...
  

  But currently the source.scss is:
  [ng-controller="LaunchInstanceSourceController"] {
td.hi-light {
  color: #0084d1;
}
...
  }

  Any change of scss file(such as:  color: red) does not take effect
  since the two files do not match.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1538932/+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 1538935] [NEW] Alert message is coming twice in the glance

[Pankaj Mishra]

Public bug reported:

While adding image from dashboard, pass the wrong location URL, alert message 
is coming twice.  
For more details please refer attached file.

** Affects: horizon
 Importance: Undecided
 Assignee: Pankaj Mishra (pankaj-mishra)
 Status: New

** Attachment added: "glance_create_image.JPG"
   
https://bugs.launchpad.net/bugs/1538935/+attachment/4558148/+files/glance_create_image.JPG

** Changed in: horizon
 Assignee: (unassigned) => Pankaj Mishra (pankaj-mishra)

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

Title:
  Alert message is coming twice in the glance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  While adding image from dashboard, pass the wrong location URL, alert message 
is coming twice.  
  For more details please refer attached file.

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