Bug 1890857

Summary: [4.5] invalid syntax errors in prometheus-operator container logs
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Sergiusz Urbaniak <surbania>
Status: CLOSED DUPLICATE QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, spasquie, surbania
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-23 07:45:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
"invalid syntax" errors in prometheus-operator container logs none

Description Junqi Zhao 2020-10-23 05:50:45 UTC
Created attachment 1723688 [details]
"invalid syntax" errors in prometheus-operator container logs

Description of problem:
UPI on openstack baremetal cluster,there are "invalid syntax" errors in prometheus-operator container logs, did not meet it in ipi-on-aws cluster, maybe the issue is not reproducible every time
# oc -n openshift-monitoring logs $(oc -n openshift-monitoring get po | grep prometheus-operator | awk '{print $1}') -c prometheus-operator | grep "invalid syntax" | head -n 3
E1023 03:52:43.205867       1 reflector.go:178] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:486: Failed to list *v1.PodMonitor: resourceVersion: Invalid value: "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": strconv.ParseUint: parsing "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": invalid syntax
E1023 03:52:46.217513       1 reflector.go:178] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:486: Failed to list *v1.PodMonitor: resourceVersion: Invalid value: "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": strconv.ParseUint: parsing "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": invalid syntax
E1023 03:52:52.282390       1 reflector.go:178] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:486: Failed to list *v1.PodMonitor: resourceVersion: Invalid value: "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": strconv.ParseUint: parsing "13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022/13022": invalid syntax


Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-10-20-022340
Prometheus Operator version '0.38.1'

How reproducible:
not sure

Steps to Reproduce:
1. check prometheus-operator logs
2.
3.

Actual results:
invalid syntax error

Expected results:
no issue

Additional info:

Comment 2 Simon Pasquier 2020-10-23 07:45:51 UTC

*** This bug has been marked as a duplicate of bug 1858991 ***

Comment 3 Junqi Zhao 2020-10-26 03:24:05 UTC
@Simon
This bug is happend in 4.5, but closed as a duplicate of bug 1858991 which happened and fixed in 4.6, does this mean we don't want to fix in 4.5?

Comment 4 Simon Pasquier 2020-11-04 08:29:21 UTC
Serg replied in https://bugzilla.redhat.com/show_bug.cgi?id=1891815#c6 that we're not planning to backport on 4.5.