[Yahoo-eng-team] [Bug 1432963] Re: Volume of 'in-use' remain by a timeout during the attach

2015-08-16 Thread Mike Perez 
** Changed in: cinder
   Status: In Progress = Invalid

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

Title:
  Volume of 'in-use' remain by a timeout during the attach

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

Bug description:
  Remain as the 'in-use' volume due to timeout during the 'attach'.
  If the problem occurs, The instance can't detach/attach the volume.
detach - volume_id not found
attach - libvirtError: Requested operation is not valid: target vdb 
already exists 
(other volume)

  This problems are caused by the mismatching DB because c-vol does not 
rollback it when happend the timeout of RPC(CALL).
  At first, c-vol takes time in the attaching process, and the attaching 
process failed in the c-api by timeout.
  But in this time, the attaching process does not failed yet in the c-vol.

  By this, BDM is deleted and volume is updated to in-use.
  (If successful the attaching process in the c-vol.)

  Repro 
  used master
cinder: commit d4b77484c5d41f207d54f40dcdd530fb8a1b1ea6
nova  : commit eaeecdaf4743463888c3ee24fb08128eac15dee7

  1. attach volume
 (in cinder/volume/manage.py def attach_volume)
  note: I reproduced this problem by inserting sleep in this method.
  2. RPC(CALL) timeout in the c-api(attach_volume process takes time beyond the 
rpc_response_timeout)

  About the volume and BDM 
  block_device_mapping
  
+-++-+---+--+-+--+-+
  | deleted_at  | id | device_name | delete_on_termination | volume_id  
  | connection_info | instance_uuid 
   | deleted |
  
+-++-+---+--+-+--+-+
  | NULL|  1 | /dev/vda| 1 | NULL   
  | NULL| 
4683d4fb-758c-459e-9def-b8d247a56954 |   0 |
  | 2015-03-17 06:12:36 |  2 | /dev/vdb| 0 | 
46d1bfbb-bdf2-472f-8bf6-2d2367b1edb1 | NULL| 
4683d4fb-758c-459e-9def-b8d247a56954 |   2 |
  
+-++-+---+--+-+--+-+
  volumes
  
++-+--++---+---+---++
  | deleted_at | deleted | id   | status | 
attach_status | terminated_at | provider_location   
  | provider_auth   
   |
  
++-+--++---+---+---++
  | NULL   |   0 | 46d1bfbb-bdf2-472f-8bf6-2d2367b1edb1 | in-use | 
attached  | NULL  | 192.168.58.172:3260,4 
iqn.2010-10.org.openstack:volume-46d1bfbb-bdf2-472f-8bf6-2d2367b1edb1 1 | CHAP 
2W7r5XQcZJ5BHVctM8YY NogCxmq4VswXWHWE |
  
++-+--++---+---+---++

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1432963/+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 1467589] Re: Remove Cinder V1 supprt

2015-06-23 Thread Mike Perez 
** Also affects: tempest
   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/1467589

Title:
  Remove Cinder V1 supprt

Status in Cinder:
  In Progress
Status in OpenStack Compute (Nova):
  In Progress
Status in Rally:
  In Progress
Status in Tempest:
  New

Bug description:
  Cinder created v2 support in the Grizzly release. This is to track
  progress in removing v1 support in other projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1467589/+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 1467589] [NEW] Remove Cinder V1 supprt

2015-06-22 Thread Mike Perez 
Public bug reported:

Cinder created v2 support in the Grizzly release. This is to track
progress in removing v1 support in other projects.

** Affects: cinder
 Importance: Undecided
 Assignee: Mike Perez (thingee)
 Status: In Progress

** Affects: nova
 Importance: Undecided
 Assignee: Mike Perez (thingee)
 Status: In Progress

** Affects: rally
 Importance: Undecided
 Assignee: Ivan Kolodyazhny (e0ne)
 Status: In Progress

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

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

** Changed in: nova
 Assignee: (unassigned) = Mike Perez (thingee)

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

Title:
  Remove Cinder V1 supprt

Status in Cinder:
  In Progress
Status in OpenStack Compute (Nova):
  In Progress
Status in Rally:
  In Progress

Bug description:
  Cinder created v2 support in the Grizzly release. This is to track
  progress in removing v1 support in other projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1467589/+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 1415087] Re: [OSSA 2015-011] Format-guessing and file disclosure in image convert (CVE-2015-1850, CVE-2015-1851)

2015-06-17 Thread Mike Perez 
** Also affects: cinder/icehouse
   Importance: Undecided
   Status: New

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

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

** Changed in: cinder
Milestone: None = liberty-1

** Changed in: cinder/icehouse
 Assignee: (unassigned) = Eric Harney (eharney)

** Changed in: cinder/juno
 Assignee: (unassigned) = Eric Harney (eharney)

** Changed in: cinder/kilo
 Assignee: (unassigned) = Eric Harney (eharney)

** Changed in: cinder/icehouse
   Importance: Undecided = High

** Changed in: cinder/juno
   Importance: Undecided = High

** Changed in: cinder/kilo
   Status: New = Fix Committed

** Changed in: cinder/kilo
   Importance: Undecided = High

** Changed in: cinder/icehouse
   Status: New = Fix Committed

** Changed in: cinder/juno
   Status: New = Fix Committed

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

Title:
  [OSSA 2015-011] Format-guessing and file disclosure in image convert
  (CVE-2015-1850, CVE-2015-1851)

Status in Cinder:
  Fix Committed
Status in Cinder icehouse series:
  Fix Committed
Status in Cinder juno series:
  Fix Committed
Status in Cinder kilo series:
  Fix Committed
Status in OpenStack Compute (Nova):
  Triaged
Status in OpenStack Security Advisories:
  Fix Committed

Bug description:
  Cinder does not provide input format to several calls of qemu-img
  convert. This allows the attacker to play the format guessing by
  providing a volume with a qcow2 signature. If this signature contains
  a base file, this file will be read by a process running as root and
  embedded in the output. This bug is similar to CVE-2013-1922.

  Tested with: lvm backed volume storage, it may apply to others as well
  Steps to reproduce:
  - create volume and attach to vm,
  - create a qcow2 signature with base-file[1] from within the vm and
  - trigger upload to glance with cinder upload-to-image --disk-type qcow2[2].
  The image uploaded to glance will have /etc/passwd from the cinder-volume 
host embedded.
  Affected versions: tested on 2014.1.3, found while reading 2014.2.1

  Fix: Always specify both input -f and output format -O to qemu-
  img convert. The code is in module cinder.image.image_utils.

  Bastian Blank

  [1]: qemu-img create -f qcow2 -b /etc/passwd /dev/vdb
  [2]: The disk-type != raw triggers the use of qemu-img convert

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1415087/+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 1432490] Re: TestEncryptedCinderVolumes cryptsetup name is too long

2015-03-16 Thread Mike Perez 
Going to take John's suggestion of just passing a uuid instead of the
volume name in the iqn.

** Changed in: cinder
   Status: New = Incomplete

** Changed in: nova
   Status: New = Invalid

** Changed in: cinder
   Status: Incomplete = Invalid

** Changed in: tempest
   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/1432490

Title:
  TestEncryptedCinderVolumes cryptsetup name is too long

Status in Cinder:
  Invalid
Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  Invalid

Bug description:
  First off, while I understand this is not reproducible with the
  reference implementation LVM, this seems like a unknown limitation
  today since we're not enforcing any length on the IQN or recommending
  anything.

  When running Datera storage with Cinder and the following
  TestEncryptedCinderVolumes tests:

  {0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup
  {0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks

  cryptsetup complains about the name being too long:

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

  Nova uses the device name that's in /dev/disk-by-path, which in this
  case is the returned iqn from the backend:

  ip-172.30.128.2:3260-iscsi-iqn.2013-05.com.daterainc:OpenStack-
  TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-lun-0

  Already started talking Matt Treinish about this on IRC last week.
  Unsure where the fix should actual go into.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1432490/+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 1432490] [NEW] TestEncryptedCinderVolumes cryptsetup name is too long

2015-03-15 Thread Mike Perez 
Public bug reported:

When running Datera storage with Cinder and the following
TestEncryptedCinderVolumes tests:

{0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup
 
{0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks

cryptsetup complains about the name being too long:

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

Nova uses the device name that's in /dev/disk-by-path, which in this
case is the returned iqn from the backend:

ip-172.30.128.2:3260-iscsi-iqn.2013-05.com.daterainc:OpenStack-
TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-lun-0

Already started talking Matt Treinish about this on IRC last week.
Unsure where the fix should actual go into. While I understand this is
not reproducible with the reference implementation LVM, this seems like
a unknown limitation today since we're not enforcing any length on the
IQN or recommending anything.

** Affects: cinder
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: tempest
 Importance: Undecided
 Status: New

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

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

Title:
  TestEncryptedCinderVolumes cryptsetup name is too long

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  New

Bug description:
  When running Datera storage with Cinder and the following
  TestEncryptedCinderVolumes tests:

  {0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup
 
  {0} 
tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks

  cryptsetup complains about the name being too long:

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

  Nova uses the device name that's in /dev/disk-by-path, which in this
  case is the returned iqn from the backend:

  ip-172.30.128.2:3260-iscsi-iqn.2013-05.com.daterainc:OpenStack-
  TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-lun-0

  Already started talking Matt Treinish about this on IRC last week.
  Unsure where the fix should actual go into. While I understand this is
  not reproducible with the reference implementation LVM, this seems
  like a unknown limitation today since we're not enforcing any length
  on the IQN or recommending anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1432490/+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 1380806] Re: Shouldn't use unicode() when exception used in msgs

2015-01-19 Thread Mike Perez 
** Also affects: cinder
   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/1380806

Title:
  Shouldn't use unicode() when exception used in msgs

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

Bug description:
  There are cases (identified by mriedem) where an exception is used as
  replacement text and is coerced using unicode():

  
http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/manager.py?id=2014.2.rc2#n3264

 reason=_(Driver Error: %s) % unicode(e))

  
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/ec2/__init__.py?id=2014.2.rc2#n89

 LOG.exception(_(FaultWrapper: %s), unicode(ex))

  doing this can interfere with translation by causing things to be
  prematurely translated.

  Need to scan for and correct any occurrences.  Also need to look at
  adding/updating a hacking check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1380806/+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 1398588] Re: volume_attach action registers volume attachment even on failure

2015-01-02 Thread Mike Perez 
Reporter didn't provide a version. Using the latest from master, I was
not able to reproduce this issue (see below). Since the reporter
mentioned that Cinder does not know about this false attachment, but
Nova does, I would bet something is being set on the Nova side.

ubuntu@mount-issue:~/devstack$ nova list
c+--+-+++-+--+
| ID   | Name| Status | Task State | Power 
State | Networks |
+--+-+++-+--+
| 57304c45-101d-4ce0-8f4b-6b7ad853d135 | server1 | ACTIVE | -  | 
Running | private=10.0.0.2 |
| 1cb270bd-2131-42fa-9f99-ed95cd077cde | server2 | ACTIVE | -  | 
Running | private=10.0.0.3 |
+--+-+++-+--+
iubuntu@mount-issue:~/devstack$ cinder list
+--+---+--+--+-+--+-+
|  ID  |   Status  | Name | Size | Volume Type 
| Bootable | Attached to |
+--+---+--+--+-+--+-+
| 2a57f161-0828-4b68-8f93-cd4493ff725b | available | None |  1   | lvmdriver-1 
|  false   | |
+--+---+--+--+-+--+-+
ubuntu@mount-issue:~/devstack$ nova volume-attach server1 
2a57f161-0828-4b68-8f93-cd4493ff725b
+--+--+
| Property | Value|
+--+--+
| device   | /dev/vdb |
| id   | 2a57f161-0828-4b68-8f93-cd4493ff725b |
| serverId | 57304c45-101d-4ce0-8f4b-6b7ad853d135 |
| volumeId | 2a57f161-0828-4b68-8f93-cd4493ff725b |
+--+--+
ubuntu@mount-issue:~/devstack$ nova volume-attach server2 
2a57f161-0828-4b68-8f93-cd4493ff725b
ERROR (BadRequest): Invalid volume: volume 
'2a57f161-0828-4b68-8f93-cd4493ff725b' status must be 'available'. Currently in 
'in-use' (HTTP 400) (Request-ID: req-bfa40f00-56f9-4535-a4d1-23a8cb69b908)
ubuntu@mount-issue:~/devstack$ nova volume-attach server2 
2a57f161-0828-4b68-8f93-cd4493ff725b
ERROR (BadRequest): Invalid volume: volume 
'2a57f161-0828-4b68-8f93-cd4493ff725b' status must be 'available'. Currently in 
'in-use' (HTTP 400) (Request-ID: req-83736950-ff20-4d93-b512-ab7ffc25c7bc)
ubuntu@mount-issue:~/devstack$ cinder list
+--++--+--+-+--+--+
|  ID  | Status | Name | Size | Volume Type | 
Bootable | Attached to  |
+--++--+--+-+--+--+
| 2a57f161-0828-4b68-8f93-cd4493ff725b | in-use | None |  1   | lvmdriver-1 |  
false   | 57304c45-101d-4ce0-8f4b-6b7ad853d135 |
+--++--+--+-+--+--+
ubuntu@mount-issue:~/devstack$ http 
http://localhost:8774/v2/b9903b32e6e94a5ab2ee40e217be0fab/servers/1cb270bd-2131-42fa-9f99-ed95cd077cde/os-volume_attachments
 X-Auth-Token:'e08bc40fd5f148cf817f99c1133da8aa'
HTTP/1.1 200 OK
Content-Length: 25
Content-Type: application/json
Date: Fri, 02 Jan 2015 18:37:27 GMT
X-Compute-Request-Id: req-5d213be2-60af-450a-b521-8f979d5a80e6

{
volumeAttachments: []
}

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

** Changed in: cinder
   Status: Confirmed = Invalid

** Changed in: cinder
   Status: Invalid = Incomplete

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

Title:
  volume_attach action registers volume attachment even on failure

Status in Cinder:
  Incomplete
Status in OpenStack Compute (Nova):
  New

Bug description:
  When attaching volumes to instances, if the volume attachment fails, it is 
still noted as successful by the system in some cases.
  This is the information reflected when requesting the details of a servers 
volume attachments
  http://developer.openstack.org/api-ref-compute-v2-ext.html
  /v2/​{tenant_id}​/servers/​{server_id}​/os-volume_attachments
  Show volume attachment details

  In the example, I have 2 test servers and 1 test volume.
  I attach the volume to test_server1 and it is successful (though please see: 
https://bugs.launchpad.net/cinder/+bug/1398583)
  Next, I try to attach the same volume to test_server2.
  This call fails as expected, but the mountpoint / attachment is still 
registered.

  To demonstrate, I

[Yahoo-eng-team] [Bug 1370297] Re: volume/snapshot allows name with only white spaces

2014-10-06 Thread Mike Perez 
** Changed in: cinder
 Assignee: Liyingjun (liyingjun) = (unassigned)

** Changed in: cinder
   Status: In Progress = 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/1370297

Title:
  volume/snapshot allows name with only white spaces

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

Bug description:
  When create or edit volume or snapshot, it allows name field with only
  white spaces.

  How to reproduce:

  Just go to project - volume to create a volume with only white spaces
  a name, the volume shows up in the volume table with an empty name.

  
  same for snapshot

  Expect:

  form should not allow empty name when create/edit volume or snapshot

  
  This is split from https://bugs.launchpad.net/horizon/+bug/1357586 since 
volume and snapshot name is different from volume type name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1370297/+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 1368910] Re: intersphinx requires network access which sometimes fails

2014-09-12 Thread Mike Perez 
** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
 Assignee: (unassigned) = Andreas Jaeger (jaegerandi)

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

Title:
  intersphinx requires network access  which sometimes fails

Status in Cinder:
  In Progress
Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  The intersphinx module requires internet access, and periodically
  causes docs jobs to fail.

  This module also prevents docs from being built without internet
  access.

  Since we don't actually use intersphinx for much (if anything), lets
  just remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1368910/+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 1321376] [NEW] Keystone race certificate lookup gets a 404

2014-05-20 Thread Mike Perez 
Public bug reported:

http://paste.openstack.org/show/81017/
http://logs.openstack.org/33/94233/1/check/check-grenade-dsvm/9f3206c/console.html

** Affects: tempest
 Importance: Undecided
 Status: New

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

** No longer affects: keystone

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

Title:
  Keystone race certificate lookup gets a 404

Status in Tempest:
  New

Bug description:
  http://paste.openstack.org/show/81017/
  
http://logs.openstack.org/33/94233/1/check/check-grenade-dsvm/9f3206c/console.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/tempest/+bug/1321376/+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 1279881] Re: Cannot send scheduler.run_instance events

2014-03-24 Thread Mike Perez 
Cinder patch: https://review.openstack.org/#/c/81696/

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

** Changed in: cinder
   Importance: Undecided = Critical

** Changed in: cinder
 Assignee: (unassigned) = John Griffith (john-griffith)

** Changed in: cinder
Milestone: None = icehouse-rc1

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

Title:
  Cannot send scheduler.run_instance events

Status in Cinder:
  In Progress
Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When launching an instance I'm able to trigger the following error
  with notifications active:

  2014-02-13 16:26:39.974 ERROR oslo.messaging.notify._impl_messaging
  [-] Could not send notification to notifications.
  Payload={'_context_roles': [u'admin'], '_context_request_id': u'req-
  7d0ca56f-f609-40ef-91e1-acf7d5a4a607', '_context_quota_class': None,
  'event_type': 'scheduler.run_instance', '_context_service_catalog':
  [{u'endpoints': [{u'adminURL':
  u'http://162.209.87.220:8776/v1/8c5cfa81726043afb5641ec3d6665f27',
  u'region': u'RegionOne', u'id': u'125bb6de586c435eb4e14e5e62090b43',
  u'internalURL':
  u'http://162.209.87.220:8776/v1/8c5cfa81726043afb5641ec3d6665f27',
  u'publicURL':
  u'http://162.209.87.220:8776/v1/8c5cfa81726043afb5641ec3d6665f27'}],
  u'endpoints_links': [], u'type': u'volume', u'name': u'cinder'}],
  'timestamp': '2014-02-13 16:26:39.970161', '_context_user':
  u'b6bbfab520dc4f6b91a95cd819f0316c', '_unique_id':
  '447230aa40904dd1aa2b6a9319b57f56', '_context_instance_lock_checked':
  False, '_context_user_id': u'b6bbfab520dc4f6b91a95cd819f0316c',
  'payload': {'instance_id': u'84a4f45c-3f85-4527-ae85-6f323e136d01',
  'state': 'error', 'request_spec': {u'num_instances': 1,
  u'block_device_mapping': [{u'instance_uuid': u'84a4f45c-
  3f85-4527-ae85-6f323e136d01', u'guest_format': None, u'boot_index': 0,
  u'delete_on_termination': True, u'no_device': None,
  u'connection_info': None, u'snapshot_id': None, u'device_name': None,
  u'disk_bus': None, u'image_id': u'0fbb3b3b-
  7d69-42d2-8bc7-3b87073e69b2', u'source_type': u'image',
  u'device_type': u'disk', u'volume_id': None, u'destination_type':
  u'local', u'volume_size': None}], u'image': {u'status': u'active',
  u'name': u'ubuntu1310', u'deleted': False, u'container_format':
  u'bare', u'created_at': u'2014-02-13T15:50:11.00', u'disk_format':
  u'raw', u'updated_at': u'2014-02-13T15:50:17.00', u'id': u
  '0fbb3b3b-7d69-42d2-8bc7-3b87073e69b2', u'owner':
  u'8c5cfa81726043afb5641ec3d6665f27', u'min_ram': 0, u'checksum':
  u'5c7a196274f24cd40100eac98f661057', u'min_disk': 0, u'is_public':
  True, u'deleted_at': None, u'properties': {}, u'size': 244711424},
  u'instance_type': {u'root_gb': 40, u'name': u'm1.medium',
  u'ephemeral_gb': 0, u'memory_mb': 4096, u'vcpus': 2, u'extra_specs':
  {}, u'swap': 0, u'rxtx_factor': 1.0, u'flavorid': u'3',
  u'vcpu_weight': None, u'id': 1}, u'instance_properties': {u'vm_state':
  u'building', u'availability_zone': u'nova', u'terminated_at': None,
  u'ephemeral_gb': 0, u'instance_type_id': 1, u'user_data': None,
  u'cleaned': False, u'vm_mode': None, u'deleted_at': None,
  u'reservation_id': u'r-6sv4oy43', u'id': 2, u'security_groups':
  [{u'project_id': u'8c5cfa81726043afb5641ec3d6665f27', u'user_id':
  u'b6bbfab520dc4f6b91a95cd819f0316c', u'description': u'default',
  u'deleted': False, u'created_at': u'2014-02-13T15:50:52.00',
  u'updated_at': None, u'deleted_at': None, u'id': 1, u'name':
  u'default'}], u'disable_terminate': False, u'display_name': u'lol',
  u'uuid': u'84a4f45c-3f85-4527-ae85-6f323e136d01',
  u'default_swap_device': None, u'info_cache': {u'instance_uuid': u
  '84a4f45c-3f85-4527-ae85-6f323e136d01', u'deleted': False,
  u'created_at': u'2014-02-13T16:26:39.00', u'updated_at': None,
  u'network_info': [], u'deleted_at': None}, u'hostname': u'lol',
  u'launched_on': None, u'display_description': u'lol', u'key_data':
  None, u'kernel_id': u'', u'power_state': 0,
  u'default_ephemeral_device': None, u'progress': 0, u'project_id':
  u'8c5cfa81726043afb5641ec3d6665f27', u'launched_at': None,
  u'scheduled_at': None, u'node': None, u'ramdisk_id': u'',
  u'access_ip_v6': None, u'access_ip_v4': None, u'deleted': False,
  u'key_name': None, u'updated_at': None, u'host': None,
  u'ephemeral_key_uuid': None, u'architecture': None, u'user_id':
  u'b6bbfab520dc4f6b91a95cd819f0316c', u'system_metadata':
  {u'image_min_disk': u'40', u'instance_type_memory_mb': u'4096',
  u'instance_type_swap': u'0', u'instance_type_vcpu_weight': None,
  u'instance_type_root_gb': u'40', u'instance_type_id': u'1',
  u'instance_type_name': u'm1.medium', u'instance_type_ephemeral_gb':
  u'0', u'instance_type_rxtx_factor': u'1.0', u'instance_type_flavorid':
  u'3',

[Yahoo-eng-team] [Bug 1294132] Re: Volume status set to error extending when driver fails to extend the volume

2014-03-24 Thread Mike Perez 
Santiago, that was exactly my point earlier. Those are the only places
that this happens and I don't think it's as simple as you've discussed
to recover. I do agree with Cory in the review that this issue needs to
be addressed, but I think for cases where the other operations to the
backend that would take place while the extend is in progress would
result in false positives of recovering.

** Changed in: cinder
   Status: New = Opinion

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

Title:
  Volume status set to error extending when driver fails to extend the
  volume

Status in Cinder:
  Opinion
Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If the driver can't extend the volume because there's no enough space,
  the volume status is set to error_extending and the volume becomes
  unusable. The only options to the users are to delete the volume and
  create it again.

  Expected behavior would be: if the back-end doesn't have enough
  capacity to extend the volume, warn user with proper information and
  set volume status back to 'available' since the volume is untouched.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1294132/+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 1291926] Re: MismatchError test_update_all_quota_resources_for_tenant

2014-03-18 Thread Mike Perez 
*** This bug is a duplicate of bug 1291162 ***
https://bugs.launchpad.net/bugs/1291162

Since Havana, if you create a volume in cinder that has a specified
volume type, it will introduce new default quotas. Seeing that these
tests were introduced in tempest 2014-02-20, I'm guessing some race
condition is hit where if these tests are ran before volume creation
tests, you would pass.

** Changed in: cinder
   Status: New = Invalid

** Changed in: tempest
   Status: New = Confirmed

** Changed in: tempest
 Assignee: (unassigned) = Mike Perez (thingee)

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

Title:
  MismatchError test_update_all_quota_resources_for_tenant

Status in Cinder:
  Invalid
Status in OpenStack Neutron (virtual network service):
  Invalid
Status in Tempest:
  Confirmed

Bug description:
  Observed in the Neutron full job

  2014-03-13 02:08:54.390 | Traceback (most recent call last):
  2014-03-13 02:08:54.390 |   File 
tempest/api/volume/admin/test_volume_quotas.py, line 67, in 
test_update_all_quota_resources_for_tenant
  2014-03-13 02:08:54.390 | self.assertEqual(new_quota_set, quota_set)
  2014-03-13 02:08:54.391 |   File 
/usr/local/lib/python2.7/dist-packages/testtools/testcase.py, line 321, in 
assertEqual
  2014-03-13 02:08:54.391 | self.assertThat(observed, matcher, message)
  2014-03-13 02:08:54.391 |   File 
/usr/local/lib/python2.7/dist-packages/testtools/testcase.py, line 406, in 
assertThat
  2014-03-13 02:08:54.392 | raise mismatch_error
  2014-03-13 02:08:54.392 | MismatchError: !=:
  2014-03-13 02:08:54.392 | reference = {'gigabytes': 1009, 'snapshots': 11, 
'volumes': 11}
  2014-03-13 02:08:54.393 | actual= {'gigabytes': 1009,
  2014-03-13 02:08:54.393 |  'gigabytes_volume-type--928001277': -1,
  2014-03-13 02:08:54.393 |  'snapshots': 11,
  2014-03-13 02:08:54.394 |  'snapshots_volume-type--928001277': -1,
  2014-03-13 02:08:54.394 |  'volumes': 11,
  2014-03-13 02:08:54.394 |  'volumes_volume-type--928001277': -1}

  Example here http://logs.openstack.org/82/67382/3/check/check-tempest-
  dsvm-neutron-full/8ffd266/console.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1291926/+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 1262424] Re: Files without code should not contain copyright notices

2013-12-30 Thread Mike Perez 
** Also affects: cinder
   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/1262424

Title:
  Files without code should not contain copyright notices

Status in OpenStack Telemetry (Ceilometer):
  New
Status in Cinder:
  New
Status in Orchestration API (Heat):
  New
Status in OpenStack Neutron (virtual network service):
  In Progress
Status in OpenStack Compute (Nova):
  New
Status in Oslo - a Library of Common OpenStack Code:
  Fix Committed

Bug description:
  Due to a recent policy change in HACKING
  (http://docs.openstack.org/developer/hacking/#openstack-licensing),
  empty files should no longer contain copyright notices.

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