Coho driver: test_create_cloned_volume wrong volume order

Bug #1559461 reported by Danny Al-Gaaf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Won't Fix
Low
Unassigned

Bug Description

The test_create_cloned_volume() test of the Coho driver uses the volumes for the drv.create_cloned_volume() in the wrong order.

It's:

drv.create_cloned_volume(VOLUME, CLONE_VOL)

but the driver code assumes as parameter (volume, src_ref) which should lead to:

drv.create_cloned_volume(CLONE_VOL, VOLUME)

This may leads to positive test result while it should may fail.

Changed in cinder:
assignee: nobody → Danny Al-Gaaf (danny-al-gaaf)
status: New → In Progress
Changed in cinder:
importance: Undecided → Low
milestone: none → newton-1
Changed in cinder:
milestone: newton-1 → newton-2
Changed in cinder:
milestone: newton-2 → ocata-1
Changed in cinder:
milestone: ocata-1 → ongoing
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Bug Assignee Expired

Unassigning due to no activity for > 6 months.

Changed in cinder:
assignee: Danny Al-Gaaf (danny-al-gaaf) → nobody
Changed in cinder:
status: In Progress → New
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Coho driver has been removed [0] and apparently no longer exists [1].

[0] https://review.openstack.org/#/c/501327/
[1] https://www.theregister.co.uk/2017/08/31/coho_data_shuts_up_shop/

Changed in cinder:
status: New → Won't Fix
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.