[#RHQ-869] CheckForSuspectAgentsJob incorrectly marks resources RED when cloud servers are in different timezones

RHQ Project

CheckForSuspectAgentsJob incorrectly marks resources RED when cloud servers are in different timezones

Created: 22/Sep/08 01:04 PM Updated: 07/Oct/08 09:12 PM

Component/s:

Domain Entities, Database, Core Server, High Availability

Affects Version/s:

1.1pre

Fix Version/s:

1.1

Time Tracking:

Not Specified

Resolution Date:	22/Sep/08 11:10 PM
Date of First Response:	07/Oct/08 09:11 PM
Tester:	Corey Welton
VCS Revision:	1,580

Description

« Hide

solution: stop using timestamp fields and replace them all by persisting epoch millis into numeric fields instead.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 01:08 PM

rev1569 - part 1 - convert Agent.lastAvailabilityReport from timestamp to long (epoch millis);

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 02:05 PM

rev1570 - part 2 - convert AlertDampeningEvent.eventTimestamp from timestamp to long (epoch millis);

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 03:30 PM

rev1574 - fix to failing tests as a result of rev1569 - since lastAvailabilityReport can be null, we need to make the field Long, and always compare values with .equals not ==

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 05:10 PM

rev1576 - part 3 - convert Event.timestamp and Event.ackTime from timestamp to long (epoch millis);

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 08:57 PM

rev1578 - part 4 - convert ContentSource, Channel, InstalledPackage, InstalledPackagedHistory, and PackageVersion timestamp columns to long (epoch millis);

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 09:57 PM

rev1579 - part 5 - convert MeasurementSchedule.mtime from timestamp to long (epoch millis);

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 11:10 PM

barring pushback from QA about regressions, this issue is resolved.

[ Permlink | « Hide ]

Joseph Marques - 22/Sep/08 11:57 PM

rev1580 - part 5 - initial MeasurementSchedule insertion does not populate an mtime, so we need to use Long here and allow for nulls to be filled later;

[ Permlink | « Hide ]

Corey Welton - 07/Oct/08 09:11 PM

QA Verified -- I have had systems in a cloud set to EST, CEST, CST, ADT and GET. Resources did not at any time turn red.