Bug 1841150 - text format parsing error in line 3: invalid escape sequence '\\,'
Summary: text format parsing error in line 3: invalid escape sequence '\\,'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: Clayton Coleman
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-28 13:38 UTC by jooho lee
Modified: 2024-03-25 15:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 13:55:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description jooho lee 2020-05-28 13:38:04 UTC
Description of problem:
node exporter have parsing error so telemeter console and cloud.redhat.com does not show any metrics

```
oc -n openshift-monitoring exec -c node-exporter node-exporter-w62hk -- cat /var/node_exporter/textfile/virt.prom
# HELP virt_platform reports one series per detected virtualization type. If no type is detected, the type is "none".
# TYPE virt_platform gauge
virt_platform{type="none",bios_vendor="Cisco Systems\, Inc.",bios_version="C240M5.4.0.4p.0.1112191020",system_manufacturer="Cisco Systems Inc",system_product_name="UCSC-C240-M5SX",system_version="A0",baseboard_manufacturer="Cisco Systems Inc",baseboard_product_name="UCSC-C240-M5SX"} 
```

I think the error happens because fo "Cisco Systems\"

Version-Release number of selected component (if applicable):


How reproducible:
it keeps happening on bare-metal worker node from the customer site

Steps to Reproduce:
1.
2.
3.

Actual results:
2020-05-25T15:48:25.638300316Z time="2020-05-25T15:48:25Z" level=error msg="Error parsing \"/var/node_exporter/textfile/virt.prom\": text format parsing error in line 3: invalid escape sequence '\\,'" source="textfile.go:211"

Expected results:
No errors expected

Additional info:

Comment 1 Pawel Krupa 2020-05-28 13:55:19 UTC
This is fixed in 4.4.5


Note You need to log in before you can comment on or make changes to this bug.