from:"jingtao liang"

[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

2016-07-12 Thread jingtao liang

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

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

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

Status in Anchor:
  Fix Released
Status in anvil:
  New
Status in bifrost:
  Fix Released
Status in Blazar:
  In Progress
Status in Ceilometer:
  New
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in dox:
  New
Status in DragonFlow:
  New
Status in Freezer:
  New
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in heat:
  Fix Released
Status in heat-cfntools:
  Fix Released
Status in Heat Translator:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in kolla-mesos:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-brocade:
  New
Status in networking-cisco:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in octavia:
  Fix Released
Status in ooi:
  Fix Released
Status in os-brick:
  In Progress
Status in os-client-config:
  Fix Released
Status in oslo.messaging:
  In Progress
Status in python-barbicanclient:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-cueclient:
  Fix Released
Status in python-designateclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-swiftclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Quark: Money Reinvented:
  New
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  In Progress
Status in Solum:
  Fix Released
Status in Stackalytics:
  Fix Released
Status in OpenStack Object Storage (swift):
  Invalid
Status in taskflow:
  In Progress
Status in tempest:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in tuskar:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  Fix Released
Status in designate package in Ubuntu:
  Fix Released
Status in python-tuskarclient package in Ubuntu:
  Fix Committed

Bug description:
  Replace assertEqual(None, *) with assertIsNone in tests to have
  more clear messages in case of failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

2016-07-11 Thread jingtao liang

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

** Changed in: swift
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

Status in Anchor:
  Fix Released
Status in bifrost:
  Fix Released
Status in Blazar:
  In Progress
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in dox:
  New
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in heat:
  Fix Released
Status in heat-cfntools:
  Fix Released
Status in Heat Translator:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in kolla-mesos:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in octavia:
  Fix Released
Status in ooi:
  Fix Released
Status in os-brick:
  New
Status in os-client-config:
  Fix Released
Status in python-barbicanclient:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-cueclient:
  Fix Released
Status in python-designateclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-swiftclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  New
Status in Solum:
  Fix Released
Status in Stackalytics:
  Fix Released
Status in OpenStack Object Storage (swift):
  New
Status in tempest:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in tuskar:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  Fix Released
Status in designate package in Ubuntu:
  Fix Released
Status in python-tuskarclient package in Ubuntu:
  Fix Committed

Bug description:
  Replace assertEqual(None, *) with assertIsNone in tests to have
  more clear messages in case of failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

2016-07-11 Thread jingtao liang

** Also affects: searchlight
   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/1280522

Title:
  Replace assertEqual(None, *) with assertIsNone in tests

Status in Anchor:
  Fix Released
Status in bifrost:
  Fix Released
Status in Blazar:
  In Progress
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in dox:
  New
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in heat:
  Fix Released
Status in heat-cfntools:
  Fix Released
Status in Heat Translator:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-python-agent:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in kolla-mesos:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-cisco:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in octavia:
  Fix Released
Status in ooi:
  Fix Released
Status in os-brick:
  New
Status in os-client-config:
  Fix Released
Status in python-barbicanclient:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-congressclient:
  Fix Released
Status in python-cueclient:
  Fix Released
Status in python-designateclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-ironicclient:
  Fix Released
Status in python-manilaclient:
  Fix Released
Status in python-neutronclient:
  Fix Released
Status in python-openstackclient:
  Fix Released
Status in OpenStack SDK:
  Fix Released
Status in python-swiftclient:
  Fix Released
Status in python-troveclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  New
Status in Solum:
  Fix Released
Status in Stackalytics:
  Fix Released
Status in tempest:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in tuskar:
  Fix Released
Status in watcher:
  Fix Released
Status in zaqar:
  Fix Released
Status in designate package in Ubuntu:
  Fix Released
Status in python-tuskarclient package in Ubuntu:
  Fix Committed

Bug description:
  Replace assertEqual(None, *) with assertIsNone in tests to have
  more clear messages in case of failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/anchor/+bug/1280522/+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 1600109] [NEW] Unit tests should not perform logging, but some tests still use

2016-07-08 Thread jingtao liang

Public bug reported:

We shuld remove the logging

** Affects: cinder
 Importance: Undecided
 Assignee: jingtao liang (liang-jingtao)
 Status: New

** Affects: glance
 Importance: Undecided
 Assignee: weiweigu (gu-weiwei)
 Status: New

** Changed in: cinder
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

** Changed in: glance
 Assignee: (unassigned) => weiweigu (gu-weiwei)

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

Title:
  Unit tests should not perform logging,but some tests still use

Status in Cinder:
  New
Status in Glance:
  New

Bug description:
  We shuld remove the logging

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1600109/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

2016-07-07 Thread jingtao liang

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

** Changed in: pycadf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Some tests use assertEqual(observed, expected) , the argument order is
  wrong

Status in Astara:
  Fix Released
Status in Barbican:
  In Progress
Status in Blazar:
  New
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in daisycloud-core:
  New
Status in Designate:
  Fix Released
Status in Freezer:
  In Progress
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in Higgins:
  New
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in networking-calico:
  New
Status in networking-infoblox:
  In Progress
Status in networking-l2gw:
  In Progress
Status in networking-sfc:
  In Progress
Status in OpenStack Compute (nova):
  Won't Fix
Status in os-brick:
  In Progress
Status in PBR:
  New
Status in pycadf:
  New
Status in python-barbicanclient:
  In Progress
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-glanceclient:
  Fix Released
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Rally:
  New
Status in Sahara:
  Fix Released
Status in Solum:
  In Progress
Status in sqlalchemy-migrate:
  New
Status in SWIFT:
  New
Status in tacker:
  In Progress
Status in tempest:
  New
Status in zaqar:
  Fix Released

Bug description:
  The test cases will produce a confusing error message if the tests
  ever fail, so this is worth fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/astara/+bug/1259292/+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 1596131] [NEW] Py3 do not support "exception, e" , we should correct it with "exception as e".

2016-06-24 Thread jingtao liang

Public bug reported:

use py3 run the test:

try:
a > 1
except Exception, e:
print 1

SyntaxError: invalid syntax

** Affects: nova
 Importance: Undecided
 Assignee: jingtao liang (liang-jingtao)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Py3 do not support "exception, e"  ,we should correct it with
  "exception as e".

Status in OpenStack Compute (nova):
  New

Bug description:
  use py3 run the test:

  try:
  a > 1
  except Exception, e:
  print 1

  SyntaxError: invalid syntax

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1596131/+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 1595786] Re: Make string.letters PY3 compatible

2016-06-24 Thread jingtao liang

** Project changed: swift-swf => swift

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

Title:
  Make  string.letters PY3 compatible

Status in  Fuel Contrail plugin:
  New
Status in Fuel Plugins:
  New
Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  In Progress
Status in OpenStack Object Storage (swift):
  New

Bug description:
  String.letters and related.Lowercase and.Uppercase are removed, please
  switch to string.ascii_letters, etc.

  
  as:
  
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

To manage notifications about this bug go to:
https://bugs.launchpad.net/fuel-plugin-contrail/+bug/1595786/+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 1595786] Re: Make string.letters PY3 compatible

2016-06-23 Thread jingtao liang

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Make  string.letters PY3 compatible

Status in OpenStack Compute (nova):
  New
Status in python-novaclient:
  New
Status in SWIFT:
  New

Bug description:
  String.letters and related.Lowercase and.Uppercase are removed, please
  switch to string.ascii_letters, etc.

  
  as:
  
https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1595786/+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 1595773] Re: Make print py3 compatible

2016-06-23 Thread jingtao liang

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  In Progress
Status in python-cinderclient:
  New
Status in Rally:
  New
Status in SWIFT:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1595773] Re: Make print py3 compatible

2016-06-23 Thread jingtao liang

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

** Changed in: glance
   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/1595773

Title:
  Make print py3 compatible

Status in Cinder:
  New
Status in Glance:
  Invalid
Status in glance_store:
  New
Status in OpenStack Identity (keystone):
  New
Status in OpenStack Compute (nova):
  New
Status in python-cinderclient:
  New
Status in Rally:
  New

Bug description:
  In PY3,

  Remove the print "", join the print () function to achieve the same
  function.

  Python 3:

  #!/usr/bin/python
  # -*- coding: utf-8 -*-
  print ("cinder")

  print "cinder"

  
File "code", line 5
  print "cinder"
   ^
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1595773/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

2016-06-23 Thread jingtao liang

** Also affects: swift-swf
   Importance: Undecided
   Status: New

** Changed in: swift-swf
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  Some tests use assertEqual(observed, expected) , the argument order is
  wrong

Status in Astara:
  In Progress
Status in Barbican:
  In Progress
Status in Blazar:
  New
Status in Ceilometer:
  Invalid
Status in Cinder:
  Fix Released
Status in congress:
  Fix Released
Status in Designate:
  Fix Released
Status in Freezer:
  In Progress
Status in Glance:
  Fix Released
Status in glance_store:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  Fix Released
Status in Magnum:
  Fix Released
Status in Manila:
  Fix Released
Status in Mistral:
  Fix Released
Status in Murano:
  Fix Released
Status in OpenStack Compute (nova):
  Won't Fix
Status in os-brick:
  In Progress
Status in python-ceilometerclient:
  Invalid
Status in python-cinderclient:
  Fix Released
Status in python-designateclient:
  Fix Committed
Status in python-glanceclient:
  In Progress
Status in python-mistralclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in Python client library for Zaqar:
  Fix Released
Status in Sahara:
  Fix Released
Status in sqlalchemy-migrate:
  New
Status in SWIFT:
  New
Status in tacker:
  New
Status in tempest:
  New
Status in zaqar:
  Fix Released

Bug description:
  The test cases will produce a confusing error message if the tests
  ever fail, so this is worth fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/astara/+bug/1259292/+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 1585122] [NEW] Uploading image failed but print successful log

2016-05-24 Thread jingtao liang

Public bug reported:

description:

When uploading image by the way of  "copy-from" failed because of "Remote 
server where the image is present is unavailable".The function return, the  
process will work on and print the log like this:
"Uploaded data of image 952a0e62-500e-44fb-bbc4-f8cc17b5b6a4 from request 
payload successfully"
That is unreasonable.

glance/api/v1/images.py

if copy_from:
try:
image_data, image_size = self._get_from_store(req.context,
  copy_from,
  dest=store)
except Exception:
upload_utils.safe_kill(req, image_meta['id'], 'queued')
msg = (_LE("Copy from external source '%(scheme)s' failed for "
   "image: %(image)s") %
   {'scheme': scheme, 'image': image_meta['id']})
LOG.exception(msg)
return

** Affects: glance
 Importance: Undecided
 Assignee: jingtao liang (liang-jingtao)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

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

Title:
  Uploading image failed but print successful log

Status in Glance:
  In Progress

Bug description:
  description:

  When uploading image by the way of  "copy-from" failed because of "Remote 
server where the image is present is unavailable".The function return, the  
process will work on and print the log like this:
  "Uploaded data of image 952a0e62-500e-44fb-bbc4-f8cc17b5b6a4 from request 
payload successfully"
  That is unreasonable.

  glance/api/v1/images.py

  if copy_from:
  try:
  image_data, image_size = self._get_from_store(req.context,
copy_from,
dest=store)
  except Exception:
  upload_utils.safe_kill(req, image_meta['id'], 'queued')
  msg = (_LE("Copy from external source '%(scheme)s' failed for 
"
 "image: %(image)s") %
 {'scheme': scheme, 'image': image_meta['id']})
  LOG.exception(msg)
  return

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1585122/+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 1560756] [NEW] galnce image-show could show the deleted images.That is not reasonable

2016-03-22 Thread jingtao liang

Public bug reported:

version :2015.1
description:

I can't see the image:

[root@2C5_10_DELL05 ~(keystone_admin)]# glance image-list| grep 
000be9f8-6463-484d-b136-7f8ea9c6785c
[root@2C5_10_DELL05 ~(keystone_admin)]# 

but I can show the image :

[root@2C5_10_DELL05 ~(keystone_admin)]# glance image-show 
000be9f8-6463-484d-b136-7f8ea9c6785c
+--+--+
| Property | Value|
+--+--+
| container_format | bare |
| created_at   | 2016-01-29T02:01:38.00   |
| deleted  | True |
| deleted_at   | 2016-01-29T02:01:39.00   |
| disk_format  | raw  |
| id   | 000be9f8-6463-484d-b136-7f8ea9c6785c |
| is_public| False|
| min_disk | 0|
| min_ram  | 0|
| name | image-603465735  |
| owner| 3280818cc4ac47ed9505bcdadf8f8a0a |
| protected| False|
| status   | deleted  |
| updated_at   | 2016-01-29T02:01:39.00   |
+--+--+

** Affects: glance
 Importance: Undecided
 Assignee: jingtao liang (liang-jingtao)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => jingtao liang (liang-jingtao)

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

Title:
  galnce image-show could show the deleted images.That is not reasonable

Status in Glance:
  New

Bug description:
  version :2015.1
  description:

  I can't see the image:

  [root@2C5_10_DELL05 ~(keystone_admin)]# glance image-list| grep 
000be9f8-6463-484d-b136-7f8ea9c6785c
  [root@2C5_10_DELL05 ~(keystone_admin)]# 

  but I can show the image :

  [root@2C5_10_DELL05 ~(keystone_admin)]# glance image-show 
000be9f8-6463-484d-b136-7f8ea9c6785c
  +--+--+
  | Property | Value|
  +--+--+
  | container_format | bare |
  | created_at   | 2016-01-29T02:01:38.00   |
  | deleted  | True |
  | deleted_at   | 2016-01-29T02:01:39.00   |
  | disk_format  | raw  |
  | id   | 000be9f8-6463-484d-b136-7f8ea9c6785c |
  | is_public| False|
  | min_disk | 0|
  | min_ram  | 0|
  | name | image-603465735  |
  | owner| 3280818cc4ac47ed9505bcdadf8f8a0a |
  | protected| False|
  | status   | deleted  |
  | updated_at   | 2016-01-29T02:01:39.00   |
  +--+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1560756/+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 1536453] [NEW] swap volume failed because block copy still active

2016-01-20 Thread jingtao liang

Public bug reported:

version : kilo

description:

I migrate a volume which is in in-use status on lvm to another VG . It will be 
error in most time . I don‘t know why .
Becasuse when I don't use the volume on lvm to migrate .It will be ok.


product steps:

1 create a volume on VG
2 create a vm
3 attach the volume to the vm
4 migrate the volume to another VG.

error logs:

2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5582, in 
_swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] resize_to)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1232, in 
swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] self._swap_volume(virt_dom, disk_dev, 
conf.source_path, resize_to)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1203, in 
_swap_volume
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] self._conn.defineXML(xml)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 183, in doit
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] result = proxy_call(self._autowrap, 
f, *args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 141, in proxy_call
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] rv = execute(f, *args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 122, in execute
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] six.reraise(c, e, tb)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 80, in tworker
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] rv = meth(*args, **kwargs)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd]   File 
"/usr/lib64/python2.7/site-packages/libvirt.py", line 3632, in defineXML
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] if ret is None:raise 
libvirtError('virDomainDefineXML() failed', conn=self)
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] libvirtError: block copy still active: 
domain has active block job
2016-01-21 11:13:40.918 27863 TRACE nova.compute.manager [instance: 
35158835-9b79-49e9-9a92-e6bbfaba50dd] 
2016-01-21 11:13:41.686 27863 INFO nova.scheduler.client.report 
[req-c59264b3-9223-472e-b1c4-bfc3f5643393 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Compute_service record updated for 
('2C5_19_CG2', '2C5_19_CG2')
2016-01-21 11:13:41.687 27863 ERROR oslo_messaging.rpc.dispatcher 
[req-c59264b3-9223-472e-b1c4-bfc3f5643393 9134a1a11e5441c29e37757231f36450 
32bfe3124bb2478aad3e6aa1cee09f14 - - -] Exception during message handling: 
block copy still active: domain has active block job
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher Traceback 
(most recent call last):
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, 
in _dispatch_and_reply
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, 
in _dispatch
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 130, 
in _do_dispatch
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
2016-01-21 11:13:41.687 27863 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 8262,

[Yahoo-eng-team] [Bug 1522667] [NEW] when nova-compute.service start .If the instance's disk is not avilable.It will cause the service failed.That is not reasonable

2015-12-03 Thread jingtao liang

Public bug reported:

version : 2015.1

details:

nova-compute.service starts,It will do something like update_available_resource 
.Including get_disk_over_committed_size_total and
get_instance_disk_info .If the instance's iscsi_path is not available or the ip 
is unable to connect.That will cause the nova-comute.service inactive.I think 
It's not reasonable for user.


logs:

2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup Traceback 
(most recent call last):
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/openstack/commot
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
x.wait()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/openstack/commot
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return self.thread.wait()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthreadt
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return self._exit_event.wait()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/eventlet/event.py", t
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return hubs.get_hub().switch()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/eventlet/hubs/hub.pyh
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return self.greenlet.switch()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/eventlet/greenthreadn
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
result = function(*args, **kwargs)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/openstack/commoe
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
service.start()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/service.py", lit
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
self.manager.pre_start_hook()
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/compute/managerk
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
self.update_available_resource(nova.context.get_admin_con)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/compute/managere
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
rt.update_available_resource(context)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/compute/resource
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
resources = self.driver.get_available_resource(self.noden)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/dre
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
disk_over_committed = self._get_disk_over_committed_size_)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/drl
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
self._get_instance_disk_info(dom.name(), xml))
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/dro
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
dk_size = lvm.get_volume_size(path)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/lve
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
run_as_root=True)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/ute
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return utils.execute(*args, **kwargs)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/nova/utils.py", linee
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
return processutils.execute(*cmd, **kwargs)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup   File 
"/usr/lib/python2.7/site-packages/oslo_concurrency/proe
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
cmd=sanitized_cmd)
2015-12-03 17:21:23.508 15646 TRACE nova.openstack.common.threadgroup 
ProcessExecutionError: Unexpected error while running

[Yahoo-eng-team] [Bug 1515457] [NEW] when delete an instance created from the volume.It will be unsuccessful because the connection_info has no volume_id

2015-11-11 Thread jingtao liang

Public bug reported:

description:
when delete an instance created from the volume. It will get the volume 
metadata like this :
volume_id = connection_info['data']['volume_id']
But the connection_info has no volume_id. It will be error.

version :2014.1.

Relevant log :
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2587, in 
do_terminate_instance
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] self._delete_instance(context, 
instance, bdms, quotas)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/hooks.py", line 103, in inner
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] rv = f(*args, **kwargs)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2556, in 
_delete_instance
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] quotas.rollback()
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/openstack/common/excutils.py", line 68, 
in __exit__
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] six.reraise(self.type_, self.value, 
self.tb)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2528, in 
_delete_instance
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] self._shutdown_instance(context, 
db_inst, bdms)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2463, in 
_shutdown_instance
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] requested_networks)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/openstack/common/excutils.py", line 68, 
in __exit__
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] six.reraise(self.type_, self.value, 
self.tb)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2453, in 
_shutdown_instance
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] block_device_info)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1009, in 
destroy
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] destroy_disks)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1098, in 
cleanup
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] volume_meta = 
self._get_volume_metadata(context, connection_info)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3642, in 
_get_volume_metadata
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] raise 
exception.InvalidBDMVolume(id=volume_id)
2015-11-12 17:03:52.676 6137 TRACE nova.compute.manager [instance: 
4d6213cb-4761-49fb-a993-37833f5a6add] UnboundLocalError: local variable 
'volume_id' referenced before assignment

Reproduce steps:
1 create a volume named a from an image
2 create an instance from the volume a
3 delete the instance

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

Title:
  when delete an instance created from the volume.It will be
  unsuccessful because the connection_info has no volume_id

Status in OpenStack Compute (nova):
  New

Bug description:
  description:
  when delete an instance created from the volume. It will get the volume 
metadata like this :

[Yahoo-eng-team] [Bug 1505476] Re: when live-migrate failed, remove_volume_connection function accept incorrect arguments order in kilo

2015-10-16 Thread jingtao liang

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

Title:
  when live-migrate failed,remove_volume_connection function  accept
  incorrect arguments order  in kilo

Status in OpenStack Compute (nova):
  New

Bug description:
  Openstack Version : kilo 2015.1.0

  Reproduce steps:

  please see the paths of codes:openstack/nova/nova/compute/manager.py

  def _rollback_live_migration(self, context, instance,dest,
  block_migration, migrate_data=None):

  ..
  for bdm in bdms:
  if bdm.is_volume:
  self.compute_rpcapi.remove_volume_connection(
  context, instance, bdm.volume_id, dest)
  ..
   
  Actual result:

  def remove_volume_connection(self, context, volume_id, instance):
  ..
  ..

  Expected result:

  def remove_volume_connection(self, context, instance, volume_id):

  
  pelease check this bug , thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1505476/+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 1505476] [NEW] when live-migrate failed, remove_volume_connection function accept incorrect arguments order in kilo

2015-10-12 Thread jingtao liang

Public bug reported:

Openstack Version : kilo 2015.1.0

Reproduce steps:

please see the paths of codes:openstack/nova/nova/compute/manager.py

def _rollback_live_migration(self, context, instance,dest,
block_migration, migrate_data=None):

..
for bdm in bdms:
if bdm.is_volume:
self.compute_rpcapi.remove_volume_connection(
context, instance, bdm.volume_id, dest)
..
 
Actual result:

def remove_volume_connection(self, context, volume_id, instance):
..
..

Expected result:

def remove_volume_connection(self, context, instance, volume_id):


pelease check this bug , thanks.

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

Title:
  when live-migrate failed,remove_volume_connection function  accept
  incorrect arguments order  in kilo

Status in OpenStack Compute (nova):
  New

Bug description:
  Openstack Version : kilo 2015.1.0

  Reproduce steps:

  please see the paths of codes:openstack/nova/nova/compute/manager.py

  def _rollback_live_migration(self, context, instance,dest,
  block_migration, migrate_data=None):

  ..
  for bdm in bdms:
  if bdm.is_volume:
  self.compute_rpcapi.remove_volume_connection(
  context, instance, bdm.volume_id, dest)
  ..
   
  Actual result:

  def remove_volume_connection(self, context, volume_id, instance):
  ..
  ..

  Expected result:

  def remove_volume_connection(self, context, instance, volume_id):

  
  pelease check this bug , thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1505476/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

[Yahoo-eng-team] [Bug 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests

[Yahoo-eng-team] [Bug 1600109] [NEW] Unit tests should not perform logging, but some tests still use

[Yahoo-eng-team] [Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

[Yahoo-eng-team] [Bug 1596131] [NEW] Py3 do not support "exception, e" , we should correct it with "exception as e".

[Yahoo-eng-team] [Bug 1595786] Re: Make string.letters PY3 compatible

[Yahoo-eng-team] [Bug 1595786] Re: Make string.letters PY3 compatible

[Yahoo-eng-team] [Bug 1595773] Re: Make print py3 compatible

[Yahoo-eng-team] [Bug 1595773] Re: Make print py3 compatible

[Yahoo-eng-team] [Bug 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong

[Yahoo-eng-team] [Bug 1585122] [NEW] Uploading image failed but print successful log

[Yahoo-eng-team] [Bug 1560756] [NEW] galnce image-show could show the deleted images.That is not reasonable

[Yahoo-eng-team] [Bug 1536453] [NEW] swap volume failed because block copy still active

[Yahoo-eng-team] [Bug 1522667] [NEW] when nova-compute.service start .If the instance's disk is not avilable.It will cause the service failed.That is not reasonable

[Yahoo-eng-team] [Bug 1515457] [NEW] when delete an instance created from the volume.It will be unsuccessful because the connection_info has no volume_id

[Yahoo-eng-team] [Bug 1505476] Re: when live-migrate failed, remove_volume_connection function accept incorrect arguments order in kilo

[Yahoo-eng-team] [Bug 1505476] [NEW] when live-migrate failed, remove_volume_connection function accept incorrect arguments order in kilo

18 matches

Site Navigation

Mail list logo

Footer information