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

Bug 2050866

Summary:	RHOCP@GCP - Service Level Agreement (SLA) shows status "Unknown"
Product:	OpenShift Container Platform	Reporter:	Maciej Florczyk <mflorczy>
Component:	Management Console	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	aos-bugs, jhadvig, xiyuzhao, xtian
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:	2022-02-22 13:14:06 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:

Description Maciej Florczyk 2022-02-04 19:44:53 UTC

Description of problem:
RHOCP Cluster Settings Service Level Agreement (SLA) shows status "Unknown" even though one can see the SLA="Standard" status on the console.redhat.com webpage.

Version-Release number of selected component (if applicable):
RHOCP 4.10.0-fc.4

How reproducible:

Steps to Reproduce:
1. Install RHOCP 4.10.0-fc.4 in the Google Cloud Platform (GCP) using IPI install method.
2. RHOCP -> Administration -> Cluster Settings -> Details -> Service Level Agreement (SLA) = Unknown
3. RHOCP -> Administration -> Cluster Settings -> Details -> Service Level Agreement (SLA) -> Manage Subscription Settings -> console.redhat.com -> Subscription settings shows Service Level Agreement (SLA) = Standard.

Actual results:
RHOCP -> Administration -> Cluster Settings -> Details -> Service Level Agreement (SLA) = Unknown
Expected results:
RHOCP -> Administration -> Cluster Settings -> Details -> Service Level Agreement (SLA) = Standard

Additional info:

Comment 1 Jakub Hadvig 2022-02-07 09:19:08 UTC

Maciej thanks for reporting this issue.
Could I ask how did you provisioned cluster on which you reproduce the issue? Using cluster-bot ?

Comment 2 Maciej Florczyk 2022-02-07 12:00:45 UTC

Hello Jakub,

I was not using cluster-bot to spin up the cluster. Just an IPI deployment in GCP.

1. Downloaded the RHOCP 4.10.0-fc.4 image from the mirror registry provided.
2. Then just run "./openshift-install create cluster" towards GCP used for testing - filling the details like cluster name, pull-secret, region etc.

Comment 3 Maciej Florczyk 2022-02-07 12:00:45 UTC

Hello Jakub,

I was not using cluster-bot to spin up the cluster. Just an IPI deployment in GCP.

1. Downloaded the RHOCP 4.10.0-fc.4 image from the mirror registry provided.
2. Then just run "./openshift-install create cluster" towards GCP used for testing - filling the details like cluster name, pull-secret, region etc.

Comment 4 Robb Hamilton 2022-02-22 13:14:06 UTC


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