Mistral

ExecutionExpirationPolicy is affected by the local timezone

Bug #1657368 reported by Kupai József on 2017-01-18

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Mistral	Fix Released	High	Kupai József	Mistral ocata-3 "o3"

The updated_at field is stored in UTC, but the expiration date calculation uses the local timezone.

This delays/hastens the execution_expiration_policy.older_than config setting depending on the current timezone.

Sharat Sharma (sharat-sharma) on 2017-01-18

Changed in mistral:
assignee:	nobody → Sharat Sharma (sharat-sharma)

Kupai József (kupsef) on 2017-01-18

Changed in mistral:
assignee:	Sharat Sharma (sharat-sharma) → Kupai József (kupsef)

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-01-18: Fix proposed to mistral (master)

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

Changed in mistral:
status:	New → In Progress

Renat Akhmerov (rakhmerov) on 2017-01-19

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-01-19: Fix merged to mistral (master)

commit fb384c9aba2cf92381530205bbf15f4c96713f5b
Author: Kupai József <email address hidden>
Date: Tue Jan 17 15:49:15 2017 +0100

using utcnow instead of now in expiration policy

Change-Id: I69b507cd9d9d18dcf589d2a832ed4619ee69d09e
Closes-bug: #1657368

Changed in mistral:
status:	In Progress → Fix Released

Revision history for this message

This issue was fixed in the openstack/mistral 4.0.0.0b3 development milestone.

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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