Fix potentially broken test test_backup_incremental_metadata

Bug #1491093 reported by Amrith Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Amrith Kumar

Bug Description

It isn't really clear what this test (test_backup_incremental_metadata) is aiming to do and the problem with the test is masked by the fact that logging isn't enabled properly. Therefore, one doesn't know that the test actually fails silently with this ...

ERROR:trove.guestagent.backup.backupagent:Error saving backup: 123.
Traceback (most recent call last):
  File "trove/guestagent/backup/backupagent.py", line 106, in stream_backup_to_storage
    meta['datastore'] = backup_info['datastore']
KeyError: 'datastore'

This is related to 1491075

Revision history for this message
Istimsak (saqman2060) wrote : Re: [Bug 1491093] [NEW] Fix potentially broken test test_backup_incremental_metadata

Www
On Sep 1, 2015 3:10 PM, "Amrith" <email address hidden> wrote:
>
> Public bug reported:
>
> It isn't really clear what this test (test_backup_incremental_metadata)
> is aiming to do and the problem with the test is masked by the fact that
> logging isn't enabled properly. Therefore, one doesn't know that the
> test actually fails silently with this ...
>
> ERROR:trove.guestagent.backup.backupagent:Error saving backup: 123.
> Traceback (most recent call last):
> File "trove/guestagent/backup/backupagent.py", line 106, in
stream_backup_to_storage
> meta['datastore'] = backup_info['datastore']
> KeyError: 'datastore'
>
> This is related to 1491075
>
> ** Affects: trove
> Importance: Undecided
> Assignee: Amrith (amrith)
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> OpenStack.
> Matching subscriptions: istimsak
> https://bugs.launchpad.net/bugs/1491093
>
> Title:
> Fix potentially broken test test_backup_incremental_metadata
>
> Status in Trove:
> New
>
> Bug description:
> It isn't really clear what this test
> (test_backup_incremental_metadata) is aiming to do and the problem
> with the test is masked by the fact that logging isn't enabled
> properly. Therefore, one doesn't know that the test actually fails
> silently with this ...
>
> ERROR:trove.guestagent.backup.backupagent:Error saving backup: 123.
> Traceback (most recent call last):
> File "trove/guestagent/backup/backupagent.py", line 106, in
stream_backup_to_storage
> meta['datastore'] = backup_info['datastore']
> KeyError: 'datastore'
>
> This is related to 1491075
>
Datastore is referred to by two tags. What is datastore?
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/trove/+bug/1491093/+subscriptions

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/219544

Changed in trove:
status: New → In Progress
Changed in trove:
importance: Undecided → Medium
milestone: none → liberty-rc1
Revision history for this message
Nikhil Manchanda (slicknik) wrote :

This is related to a unit test and is not a blocker for Liberty-RC1.

Changed in trove:
milestone: liberty-rc1 → next
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/219544
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=34ce70e299f57018b370ea0b8aa457f737f470b7
Submitter: Jenkins
Branch: master

commit 34ce70e299f57018b370ea0b8aa457f737f470b7
Author: Amrith Kumar <email address hidden>
Date: Sat Oct 17 18:29:57 2015 -0400

    Correct errors resulting in "No handlers ..." error message

    This is a checkin for the issue of having errors that read "No
    handlers could be found for logger X.Y.Z" when running tests. While
    being annoying, it is also a serious issue in that some times, the
    lack of logging masks errors in the tests. One such example is fixed
    in this chkin (see bug 1491093).

    Change-Id: I4066d226aefbd23248e88692db109d31f5c150e9
    Partial-Bug: #1491075
    Closes-Bug: #1491093

Changed in trove:
status: In Progress → Fix Committed
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/trove 5.0.0.0b1

This issue was fixed in the openstack/trove 5.0.0.0b1 development milestone.

Changed in trove:
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.