Bug 2089831 - [sig-instrumentation] Prometheus when installed on the cluster should report telemetry if a cloud.openshift.com token is present [Late] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
Summary: [sig-instrumentation] Prometheus when installed on the cluster should report ...
Keywords:
Status: VERIFIED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.11.0
Assignee: Nikolaos Leandros Moraitis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 14:13 UTC by Dennis Periquet
Modified: 2022-06-06 12:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27165 0 None open Bug 2089831: Temporarily disable telemetry token test. 2022-05-24 14:20:50 UTC

Description Dennis Periquet 2022-05-24 14:13:30 UTC 
Description of problem:

this test is failing (probably) due to bad credentials from an ex-employee:

[sig-instrumentation] Prometheus when installed on the cluster should report telemetry if a cloud.openshift.com token is present [Late] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]

It is causing payload rejections.

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

4.11 and probably all the way down to 4.6

How reproducible:

Very

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

slack thread: https://coreos.slack.com/archives/C01CQA76KMX/p1653321132263609
Comment 3 Devan Goodwin 2022-06-06 12:05:17 UTC 
This is resolved by getting the server side folks to bump limits for the account now in use. Moving to verified.
Note You need to log in before you can comment on or make changes to this bug.