Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
When calling lctl get_param obdfilter.*OST*.job_stats there may be values that fill all left padded space. For example:
- job_id: 56796601 snapshot_time: 1596652184 read_bytes: { samples: 62829, unit: bytes, min: 4096, max:16777216, sum: 141697982464 } write_bytes: { samples: 2146, unit: bytes, min: 955, max: 1154584, sum: 320832894 } getattr: { samples: 0, unit: reqs } setattr: { samples: 0, unit: reqs } punch: { samples: 1, unit: reqs } sync: { samples: 0, unit: reqs } destroy: { samples: 0, unit: reqs } create: { samples: 0, unit: reqs } statfs: { samples: 0, unit: reqs } get_info: { samples: 0, unit: reqs } set_info: { samples: 0, unit: reqs } quotactl: { samples: 0, unit: reqs }
The max value (max:16777216) has no space between the key and value and is now considered a scalar instead of a key value mapping.
Attachments
Issue Links
- is related to
-
LU-15826 jobstats output can produce invalid yaml ( part 2 )
- Resolved