incorrect error message when timestamp has expired
Bug #534869 reported by
chris grzegorczyk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
Fix Released
|
Undecided
|
chris grzegorczyk | ||
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Dustin Kirkland |
Bug Description
When a message has expired (the request's timestamp + 5 minutes) the error message generated in the cloud's log files indicates the time incorrectly. For example:
17:03:24 DEBUG [NioServerHandl
com.eucalyptus.
The Deadline should have:
- The correct value for the day and month (off by one)
- Be in UTC
Changed in eucalyptus (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Dustin Kirkland (kirkland) |
Changed in eucalyptus: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
------- ------- ------- ------- ------- ------- ------- ------- ---- ------- ------- ------- ------- ------- ------- ------- ----
revno: 1211 [merge]
committer: decker <decker@hawaii>
branch nick: 1.6.2
timestamp: Mon 2010-03-08 23:04:48 -0800
message:
fix LP: #534869 correct misleading error message
-------