Incorrect error message on creating duplicate table

Bug #1288821 reported by Andrii Ostapenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Fix Released
Low
Serge Kovaleff

Bug Description

actual message: 'The resource which you are attempting to change is in use.'
expected message: 'Attempt to change a resource which is still in use: Duplicate table name: %s' % table_name

Changed in magnetodb:
assignee: nobody → Andrei Ostapenko (aostapenko)
assignee: Andrei Ostapenko (aostapenko) → nobody
Changed in magnetodb:
importance: Undecided → Low
milestone: none → next
Changed in magnetodb:
assignee: nobody → Serge Kovaleff (serge-kovaleff)
Revision history for this message
Serge Kovaleff (serge-kovaleff) wrote :

Is this correct output? "Table test5c972b898e5741faa962127a1fc9 already exists"

Should I change it to "Duplicate table name: %s' % table_name"?

Revision history for this message
Dmitriy Ukhlov (dukhlov) wrote :

Sure. After fixing this bug please move this test to stable subfolder to be checked during CI process
https://github.com/stackforge/magnetodb/blob/master/tempest/api/keyvalue/in_progress/boto/test_tables.py#L66

Changed in magnetodb:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnetodb (master)

Reviewed: https://review.openstack.org/120744
Committed: https://git.openstack.org/cgit/stackforge/magnetodb/commit/?id=1f21bb1b19b0b3bc4b5a82d10395edfafde003ff
Submitter: Jenkins
Branch: master

commit 1f21bb1b19b0b3bc4b5a82d10395edfafde003ff
Author: Ajaya Agrawal <email address hidden>
Date: Thu Sep 11 16:20:40 2014 +0530

    Correct error message on creating duplicate table

    Change-Id: I5932624bb7b8ac523053ac5bcf81966071d8ca7a
    Closes-Bug: #1288821

Changed in magnetodb:
status: Confirmed → Fix Committed
Changed in magnetodb:
milestone: next → juno-rc1
Changed in magnetodb:
status: Fix Committed → Fix Released
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.