Actions
Bug #5789
closed
Frequency displayed for agent run schedule is missing leading 0s (ex: 4:0 instead of 04:00)
Status:
Released
Priority:
2
Assignee:
Category:
Web - Maintenance
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Since #5434, the new tab in Node details allows to change the agent run frequency. However, the global setting is displayed without leading 0s:
The current global setting is to run every 5 minutes, starting at 0:0, with a maximum delay after scheduled run time (random interval) of 0:5.
Please add 2 digits to all time displays (this should be "starting at 00:00, with a maximum delay after scheduled run time (random interval) of 00:05")
Updated by Jonathan CLARKE about 10 years ago
- Target version changed from 3.0.0~beta1 to 3.0.0~beta2
- Parent task deleted (
#5434)
This was introduced in #5434
Updated by Nicolas CHARLES about 10 years ago
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Updated by Nicolas CHARLES about 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/684/files
Updated by Nicolas CHARLES about 10 years ago
- Pull Request changed from https://github.com/Normation/rudder/pull/684/files to https://github.com/Normation/rudder/pull/684
Updated by Nicolas CHARLES about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 4a38bd3f9c6d8b13a2eadd1834d7a427073d3ffc.
Updated by François ARMAND about 10 years ago
Applied in changeset d7054b0e21440760d9dd3a7c515223e3d67b0040.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions