Actions
Bug #16158
closedBug #14161: Use MB instead of mB for megabytes in the doc
Error message when serching for RAM size says we can use Mo
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:
Description
When searching RAM with Mb,it complains that only Mo or MB are valid.
We don't want the Mo part
Updated by Nicolas CHARLES about 5 years ago
- Subject changed from We cannot search with Mb to Error message when serching for RAM size says we can use Mo
- Description updated (diff)
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2584
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|35edd67ae92e173bbfc4f11e3a4fb2fa37164929.
Updated by Alexis Mousset about 5 years ago
- Name check changed from To do to Reviewed
Updated by Alexis Mousset about 5 years ago
- Fix check changed from To do to Checked
Updated by François ARMAND about 5 years ago
- Fix check changed from Checked to Error - Next version
We need to revert that one for compatibility reason: it may exists installation with "MB" already saved.
We will only keep the error message and test file, revert logic.
Updated by François ARMAND about 5 years ago
- Fix check changed from Error - Next version to Error - Blocking
Updated by François ARMAND about 5 years ago
- Fix check changed from Error - Blocking to Checked
Updated by François ARMAND about 5 years ago
- Fix check changed from Checked to Error - Fixed
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions