Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1974906

Summary: "[sig-instrumentation] Prometheus when installed on the cluster should report telemetry if a cloud.openshift.com token is present" is permafailing in CSI migration job
Product: OpenShift Container Platform Reporter: Fabio Bertinatto <fbertina>
Component: StorageAssignee: Fabio Bertinatto <fbertina>
Storage sub component: Storage QA Contact: Wei Duan <wduan>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs
Version: 4.8   
Target Milestone: ---   
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: 2021-08-19 13:32:57 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:

Comment 1 Fabio Bertinatto 2021-06-22 18:57:13 UTC
It's not clear yet who is the culprit here, but the last successful run was with openshift-tests version 4.8.0-202106120024.p0.git.da8e324.assembly.stream-da8e324. Apparently it started permafailing after openshift-tests version 4.8.0-202106130124.p0.git.da8e324.assembly.stream-da8e324.

Comment 2 Fabio Bertinatto 2021-06-23 17:23:36 UTC
Looking at the must-gather logs, I see this:

2021-06-22T11:09:44.766168988Z E0622 11:09:44.766137       1 attach_detach_controller.go:439] Error creating spec for volume "prometheus-data", pod "openshift-monitoring"/"prometheus-k8s-1": error performing CSI migration checks and translation for PVC "openshift-monitoring"/"prometheus-data-prometheus-k8s-1": nodeName is empty

However, it eventually succeeds attaching the volume:

2021-06-22T11:10:06.759187131Z I0622 11:10:06.759167       1 event.go:291] "Event occurred" object="openshift-monitoring/prometheus-k8s-1" kind="Pod" apiVersion="v1" type="Normal" reason="SuccessfulAttachVolume" message="AttachVolume.Attach succeeded for volume \"pvc-b58e7cf0-a515-4116-a158-0ed20b2c0f44\" "

Comment 3 Fabio Bertinatto 2021-08-19 13:32:57 UTC

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