yahoo-eng-team team mailing list archive

[Wade Holler <wade.holler@xxxxxxxxxx>]

Public bug reported:

Description
===========
ScaleIO volumes that were created pre stable/newton ( stable/mitaka ) in my case, 
do not connect or disconnect to/from the hypervisor when nova-compute attempts the 
connection after the upgrade to stable/newton.

This appears to be because the os_brick 1.2 to 1.6 change includes a new attribute 
'scaleIO_volume_id'
This field is not created if the volumes were created at stable/mitaka or before.
In this case, this field is not found in nova.block_device_mappings 'connection_info'
column. This field is created for volumes created after stable/newton upgrade.


Steps to reproduce
==================
1. Install ScaleIO
2. Install openstack via openstack-ansible stable/mitaka
3. Create and connect ScaleIO volumes to instances
4. Upgrade to stable/newton
5. Shutdown a instance
6. Attempt start of a instance

Expected result
===============
The instance should start

Actual result
=============
The instance would not start.
http://pastebin.com/Pvd6HrcL

--after manually adding the 'scaleIO_volume_if' parameter to 
nova.block_device_mapping.connection_info the connect / disconnect
works as expected.

Environment
===========
1. Exact version of OpenStack you are running. See the following
  stable/newton deployed via openstack-ansible 14.0.3

2. Which hypervisor did you use?
   libvirt+kvm

2. Which storage type did you use?
   scaleIO 2.0.1

3. Which networking type did you use?
   neutron with linux bridge

Logs & Configs
==============
http://pastebin.com/Pvd6HrcL

os_brick version with OSA stable/mitaka = 1.2
os_brick version with OSA stable/newton = 1.6

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

Title:
  ScaleIO Volumes Created before Newton, do not connect or disconnect
  after Newton upgrade

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  ScaleIO volumes that were created pre stable/newton ( stable/mitaka ) in my case, 
  do not connect or disconnect to/from the hypervisor when nova-compute attempts the 
  connection after the upgrade to stable/newton.

  This appears to be because the os_brick 1.2 to 1.6 change includes a new attribute 
  'scaleIO_volume_id'
  This field is not created if the volumes were created at stable/mitaka or before.
  In this case, this field is not found in nova.block_device_mappings 'connection_info'
  column. This field is created for volumes created after stable/newton upgrade.

  
  Steps to reproduce
  ==================
  1. Install ScaleIO
  2. Install openstack via openstack-ansible stable/mitaka
  3. Create and connect ScaleIO volumes to instances
  4. Upgrade to stable/newton
  5. Shutdown a instance
  6. Attempt start of a instance

  Expected result
  ===============
  The instance should start

  Actual result
  =============
  The instance would not start.
  http://pastebin.com/Pvd6HrcL

  --after manually adding the 'scaleIO_volume_if' parameter to 
  nova.block_device_mapping.connection_info the connect / disconnect
  works as expected.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    stable/newton deployed via openstack-ansible 14.0.3

  2. Which hypervisor did you use?
     libvirt+kvm

  2. Which storage type did you use?
     scaleIO 2.0.1

  3. Which networking type did you use?
     neutron with linux bridge

  Logs & Configs
  ==============
  http://pastebin.com/Pvd6HrcL

  os_brick version with OSA stable/mitaka = 1.2
  os_brick version with OSA stable/newton = 1.6

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