Versioned server notifications don't include updated_at

Bug #1684860 reported by Steve McLellan on 2017-04-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Balazs Gibizer

Bug Description

Looking at the example payloads on, updated_at is missing. This field's quite important as it can help with notifications processed out of order.

If it is present in payloads (I don't see it in 1.1 notifications), it would be good to update the documentation.

Balazs Gibizer (balazs-gibizer) wrote :

Seems like we missed the udpate_at field during the transformation of the instance notifications.

Changed in nova:
status: New → Confirmed
tags: added: low-hanging-fruit
Changed in nova:
assignee: nobody → Takashi NATSUME (natsume-takashi)

Fix proposed to branch: master

Changed in nova:
status: Confirmed → In Progress
Matt Riedemann (mriedem) on 2017-07-17
Changed in nova:
importance: Undecided → Medium
tags: added: notifications
removed: low-hanging-fruit
Changed in nova:
assignee: Takashi NATSUME (natsume-takashi) → Balazs Gibizer (balazs-gibizer)

Submitter: Jenkins
Branch: master

commit bf17be9e8ffc393a3af1dbd88b0c0623658b0979
Author: Takashi NATSUME <email address hidden>
Date: Mon Jun 19 13:49:25 2017 +0900

    Add 'updated_at' field to InstancePayload in notifications

    Change-Id: Iddc5ec3b5053ddf5dce73c86edca26c4552d451b
    Implements: bp versioned-notification-transformation-pike
    Closes-Bug: #1684860

Changed in nova:
status: In Progress → Fix Released

This issue was fixed in the openstack/nova development milestone.

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

Other bug subscribers