VOLUME_NOT_FOUND_ERROR error code is wrong in ScaleIO driver

Bug #1545023 reported by Xing Yang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
High
Xing Yang

Bug Description

VOLUME_NOT_FOUND_ERROR is wrong in the ScaleIO Cinder driver. It is 78 currently, but the correct error code is 79.

Xing Yang (xing-yang)
Changed in cinder:
assignee: nobody → Xing Yang (xing-yang)
status: New → In Progress
importance: Undecided → High
tags: added: drivers emc scaleio
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/268344
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=eac894c09f31801430e61e89f3dbad127125ed6b
Submitter: Jenkins
Branch: master

commit eac894c09f31801430e61e89f3dbad127125ed6b
Author: Xing Yang <email address hidden>
Date: Sat Nov 21 22:19:12 2015 -0500

    Manage/unmanage volume in ScaleIO driver

    Add support for manage/unmanage volume in the ScaleIO driver.

    Also fixed an error code for volume not found.

    DocImpact
    Implements: blueprint scaleio-manage-existing
    Closes-Bug: #1545023
    Change-Id: I14ad94905aaa7ea2bef7c75011a40c5d057e1cc0

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/cinder 8.0.0.0b3

This issue was fixed in the openstack/cinder 8.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.