collect logs with date range should warn if range is invalid (and not just revert to collecting all)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Victor Romano |
Bug Description
Brief Description
-----------------
Currently, no feedback or warning provided in the case the collection date range is invalid.
Severity
--------
standard
Steps to Reproduce
------------------
System has been running for multiple days for this test
Performed a collect operation specifying a start and end date where the dates specified would be an invalid range...
For example the start date and end date values are reversed
$ collect controller-0 --start-date 20210914 --end-date 20210913
Expected Behavior
------------------
At minimum a warning should be given to the admin as it will not actually be using the range specified
Actual Behavior
----------------
No feedback or warning provided in the case the range is invalid.
Reproducibility
---------------
100% reproducible
System Configuration
-------
It was tested on DC standalone, but all systems have this behavior.
Branch/Pull Time/Commit
-------
NA
Last Pass
---------
NA
Timestamp/Logs
--------------
2021-09-
2021-09-
2021-09-
2021-09-
2021-09-
2021-09-
2021-09-
2021-09-
Test Activity
-------------
NA
Workaround
----------
No workaround. If the user entered an invalid date or invalid date range, the system will revert to collect all.
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.tools |
tags: | added: stx.9.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /utilities/ +/871634
Review: https:/