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

Bug 1788437

Summary: no cluster_infrastructure_provider result after upgrade from 4.1.29 to 4.2.13
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: InstallerAssignee: Abhinav Dahiya <adahiya>
Installer sub component: openshift-installer QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: alegrand, anpicker, aos-bugs, erooth, kakkoyun, lcosic, mfojtik, mloibl, nagrawal, pkrupa, surbania
Version: 4.2.zKeywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.5.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-22 15:32:28 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
scrape targets none

Description Junqi Zhao 2020-01-07 07:59:37 UTC 
Description of problem:
after upgrade from 4.1.29 to 4.2.13, there is not result for cluster_infrastructure_provider.
see the steps below, there was resulf for cluster_infrastructure_provider in 4.1.29, but no resulf after upgraded to 4.2.13
************************
# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.29    True        False         4h      Cluster version is 4.1.29


# oc -n openshift-kube-apiserver-operator get ep
NAME      ENDPOINTS         AGE
metrics   10.130.0.8:8443   4h15m

# oc -n openshift-kube-apiserver-operator get pod
NAME                                       READY   STATUS    RESTARTS   AGE
kube-apiserver-operator-67f4f657bf-jsprw   1/1     Running   1          4h16m


# token=`oc -n openshift-monitoring sa get-token prometheus-k8s`
# oc -n openshift-kube-apiserver-operator exec kube-apiserver-operator-67f4f657bf-jsprw -- curl -k -H "Authorization: Bearer $token" 'https://10.130.0.8:8443/metrics' | grep cluster_infrastructure_provider
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 73557  100 73557    0     0   489k      0 --:--:-- --:--:-- --:--:--  492k
# HELP cluster_infrastructure_provider Reports whether the cluster is configured with an infrastructure provider. type is unset if no cloud provider is recognized or set to the constant used by the Infrastructure config. region is set when the cluster clearly identifies a region within the provider. The value is 1 if a cloud provider is set or 0 if it is unset.
# TYPE cluster_infrastructure_provider gauge
cluster_infrastructure_provider{region="",type="AWS"} 1
************************

# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.13    True        False         4m38s   Cluster version is 4.2.13

# oc -n openshift-kube-apiserver-operator get ep
NAME      ENDPOINTS          AGE
metrics   10.129.0.90:8443   5h3m

# oc -n openshift-kube-apiserver-operator get pod
NAME                                       READY   STATUS    RESTARTS   AGE
kube-apiserver-operator-68579686bb-258kq   1/1     Running   0          11m

# token=`oc -n openshift-monitoring sa get-token prometheus-k8s`
# oc -n openshift-kube-apiserver-operator exec kube-apiserver-operator-68579686bb-258kq -- curl -k -H "Authorization: Bearer $token" 'https://10.129.0.90:8443/metrics' | grep cluster_infrastructure_provider
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  156k    0  156k    0     0  1095k      0 --:--:-- --:--:-- --:--:-- 1097k


Version-Release number of selected component (if applicable):
upgrade from 4.1.29 to 4.2.13

How reproducible:
always

Steps to Reproduce:
1. See the description
2.
3.

Actual results:
not result for cluster_infrastructure_provider.

Expected results:
should have result for cluster_infrastructure_provider.

Additional info:
Comment 1 Michal Fojtik 2020-01-13 11:47:15 UTC 
Moving this to monitoring team to assist you figuring out whether the metrics are being scraped from the kube-apiserver-operator or not in this version.
Comment 4 Sergiusz Urbaniak 2020-01-20 09:42:11 UTC 
Created attachment 1653850 [details]
scrape targets
Comment 7 Michal Fojtik 2020-05-12 10:54:22 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

As such, we're marking this bug as "LifecycleStale".

If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 8 Junqi Zhao 2020-05-12 10:57:31 UTC 
(In reply to Michal Fojtik from comment #7)
> This bug hasn't had any activity in the last 30 days. Maybe the problem got
> resolved, was a duplicate of something else, or became less pressing for
> some reason - or maybe it's still relevant but just hasn't been looked at
> yet.
> 
> As such, we're marking this bug as "LifecycleStale".
> 
> If you have further information on the current state of the bug, please
> update it, otherwise this bug will be automatically closed in 7 days. The
> information can be, for example, that the problem still occurs, that you
> still want the feature, that more information is needed, or that the bug is
> (for whatever reason) no longer relevant.

still hit the issue for upgrade OCP from 4.1 to 4.2
Comment 9 Venkata Siva Teja Areti 2020-05-20 15:35:56 UTC 
This bug is actively being worked on.
Comment 10 Venkata Siva Teja Areti 2020-05-21 13:44:11 UTC 
The issue is related to platformStatus field not being set. Another BZ tracks the same issue.

https://bugzilla.redhat.com/show_bug.cgi?id=1814332

I can see that a fix was made for 4.5. But, I am not sure about the behavior in older versions. Do operators need to fall back to the old field or migration controller would set the platformStatus in 4.2? I am assuming it is the later and moving this to the installer team.
Comment 11 Abhinav Dahiya 2020-05-22 15:32:28 UTC 
the migration controller is only run as part of for 4.5 version upgrade. https://bugzilla.redhat.com/show_bug.cgi?id=1814332

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