Monasca

Monasca API sometimes doesn't preserve milliseconds on timestamp

Bug #1515441 reported by Kaiyan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Monasca
Fix Committed
Medium
Shinya Kawabata

Bug Description

For example when running tempest test test_list_alarms_state_history_with_start_time and test_list_alarms_state_history_with_end_time on java API, the start time and end time in query will get truncated. The listed alarms state history will be wrong since the millisecond information is missing.

Shinya Kawabata (s-kawabata)
Changed in monasca:
assignee: nobody → Shinya Kawabata (s-kawabata)
OpenStack Infra (hudson-openstack)
Changed in monasca:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to monasca-api (master)

Reviewed: https://review.openstack.org/244507
Committed: https://git.openstack.org/cgit/openstack/monasca-api/commit/?id=12c1587f533584fefe190c0bbc33f0a04201fa8f
Submitter: Jenkins
Branch: master

commit 12c1587f533584fefe190c0bbc33f0a04201fa8f
Author: Shinya Kawabata <email address hidden>
Date: Thu Nov 12 17:57:38 2015 +0900

    Monasca API sometimes doesn't preserve milliseconds on timestamp

    Change-Id: Iff623ae49d80a990eedeadc0afb34d44a39a55d4
    Closes-Bug: #1515441

Changed in monasca:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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