Cisco Bug: CSCvi02040 - Changing the timezone in PI doesn't change job last run and next run times
Mar 12, 2018
- Cisco Prime Infrastructure
Known Affected Releases
3.1(7) 3.2(2.0) 3.3(0.0)
Symptom: If the timezone is changed in Prime Infrastructure, the next start and last run times of all the jobs do not update. This can cause many jobs to run at once, or none of the jobs to run for at least one hour, depending on which direction the time zone shifts. Conditions: Must change the time zone Prime Infrastructure is configured to use to a different time zone.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases