Bug 1804179

Summary:	[RHOCP4.3] Creation of prometheus failed with creationTimestamp: Invalid value: "null" error.
Product:	OpenShift Container Platform	Reporter:	Sergiusz Urbaniak <surbania>
Component:	Monitoring	Assignee:	Sergiusz Urbaniak <surbania>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, rh-container, surbania
Target Milestone:	---
Target Release:	4.4.0
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-05-13 21:59:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 3 Junqi Zhao 2020-02-26 11:38:32 UTC

Tested with 4.4.0-0.nightly-2020-02-23-191320, in order to create PVC before Prometheus, do
# while true; do oc -n openshift-monitoring delete prometheus/k8s; done

then use cluster-monitoring-config configmap to create PVCs, after all the PVCs are created, stop the first command, check the cluster-monitoring-operator pod's log, there is not "sync "openshift-monitoring/cluster-monitoring-config" failed: running task Updating Prometheus-k8s failed: reconciling Prometheus object failed: creating Prometheus object failed: Prometheus.monitoring.coreos.com "k8s" is invalid: spec.storage.volumeClaimTemplate.metadata.creationTimestamp: Invalid value: "null": spec.storage.volumeClaimTemplate.metadata.creationTimestamp in body must be of type string: "null" " error and the prometheus resource is created 
# oc -n openshift-monitoring get prometheus/k8s

Comment 5 errata-xmlrpc 2020-05-13 21:59:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581