lv_lockargs parsing error about prometheus-lvm-exporter HOT 3 CLOSED

I've tagged version 0.3.3 including commit e501804.

from prometheus-lvm-exporter.

Likely similar to #2 and #29. There are so many fields it's very difficult to find all possibilities (all instances of lv_lockargs in current test data are empty).

I'm happy to submit a fix similar to commit a855fad. Would you be able to provide me with a raw JSON snippet with real values for use in tests? One or two LVs are sufficient.

The command would be as follows (apply sudo, etc. as necessary):

/usr/sbin/lvm lvs --all --config 'global/suffix=false global/units=b report/binary_values_as_numeric=1 report/output_format=json report/buffered=false report/time_format=%s' \
  --configreport lv --options \
  lv_uuid,lv_name,lv_lockargs

from prometheus-lvm-exporter.

Here is the result limited to 2 LV plus the special LV lvmlock (which is used internally by lvmlockd and has no value for lv_lockargs):

  {
      "report": [
          {
              "lv": [
                  {"lv_uuid":"YvnAc9-CH9k-Fq5F-WfTl-oONA-5njZ-t1ChZm", "lv_name":"alpinetest", "lv_lockargs":"1.0.0:570425344"},
                  {"lv_uuid":"FmOsEf-s4PL-qNOn-KSLb-GAIG-kuuP-ErGbTp", "lv_name":"lvtest", "lv_lockargs":"1.0.0:620756992"},
                  {"lv_uuid":"PN2YZw-aWgL-O0Rc-Vkbx-Dx09-lvDp-fhpbXe", "lv_name":"[lvmlock]", "lv_lockargs":""}
              ]
          }
      ]
  }

from prometheus-lvm-exporter.