Bug #3345
closed
Search nodes should accept the "m" notation in memory size
Added by Arthur ANGLADE over 11 years ago.
Updated over 11 years ago.
Category:
Web - Nodes & inventories
Description
ie : when searching "8m" for memory size, an error occurs it should be working (it works in 2.3)
- Category set to Web - Nodes & inventories
- Target version changed from 2.4.4 to 2.4.5
- Target version changed from 2.4.5 to 2.4.6
Using the notation "m" is not working in 2.3:
- I have a Node with 91Mo of Ram
- In both => searching node for 91mo returns my node => Working fine
- In 2.4 => searching for 91m throws an error ("Invalide memory size : '496M', expecting '300 Mo', '16KB', etc")
- In 2.3 => searching for 91m does not display any result.
As it is not working in 2.3, It's far better to have an error message.
We should add the possibility to handle 'm/k/g' and other unities (omitting the O/B)
- Status changed from New to In progress
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Priority changed from N/A to 2
- Pull Request set to https://github.com/Normation/ldap-inventory/pull/18
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset ldap-inventory:commit:d148a765473a6064ff36c9c69c2478c97b792bde.
Applied in changeset ldap-inventory:commit:980623ab1b9f9012d81d365cedffe0562ce804ac.
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by Arthur ANGLADE 
Updated by Nicolas PERRON 
Updated by 
Updated by Anonymous