Bug 1384628

Summary: Unexpected Exception during refresh: HTTP status code 403 - OpenShift Provider
Product: Red Hat CloudForms Management Engine Reporter: Thomas Hennessy <thenness>
Component: ProvidersAssignee: Federico Simoncelli <fsimonce>
Status: CLOSED NOTABUG QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: carnott, fsimonce, jcutter, jdeubel, jfrey, jhardy, jocarter, myoder, obarenbo, saali
Target Milestone: GA   
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard: container
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-14 21:52:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:

Description Thomas Hennessy 2016-10-13 17:35:20 UTC 
Description of problem: Unexpected Exception during refresh: HTTP status code 403 for Openshift provider


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I have processed the CFME logs and isolated the process logs for the two items identified in the case description:

from the logs associated with dz2lrcfp405.divbiz.net

the refresh worker process - 30183 => http error
Unexpected Exception during refresh: HTTP status code 403, User "system:serviceaccount:management-infra:management-admin" cannot list all componentstatuses in the cluster

and two smartstate worker processes: 29011 and 29019 both encountering errors but not while processing any smartstate message
===================================
from the logs associated with dz2lrcfp404.divbiz.net

no ems refresh error in this log set.

several smartstate scanning errors captured in worker process logs for pids 11690, 11698, 11706, and 11714
====================================

and for the logs associated with dz2lrcfp403.divbiz.net

the refresh worker processes  - 25983 , 11986 , 14085 (and others) http error

and several smartstate scanning errors capture in the work process logs for pids 11730,11714,

I have collected the OpenShift logs into the location http://file.rdu.redhat.com/~thenness/SF-01720000-CFME-OpenShift/ under the directory "OpenShift Materials" and the CFME logs with the extracted processes noted above in the same http://file.rdu.redhat.com/~thenness/SF-01720000-CFME-OpenShift/ location under the directory "CFME Materials".
Comment 2 Federico Simoncelli 2016-10-14 21:52:10 UTC 
(In reply to Thomas Hennessy from comment #0)
> Description of problem: Unexpected Exception during refresh: HTTP status
> code 403 for Openshift provider
> 
> 
> Version-Release number of selected component (if applicable): 5.6.2.1
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:
> I have processed the CFME logs and isolated the process logs for the two
> items identified in the case description:
> 
> from the logs associated with dz2lrcfp405.divbiz.net
> 
> the refresh worker process - 30183 => http error
> Unexpected Exception during refresh: HTTP status code 403, User
> "system:serviceaccount:management-infra:management-admin" cannot list all
> componentstatuses in the cluster

I saw you mentioning other error messages in the description of the bug, anyway I would keep 1 issue per bug and given the title and the initial description, this BZ is about:

  Unexpected Exception during refresh: HTTP status code 403, User "system:serviceaccount:management-infra:management-admin" cannot list all componentstatuses in the cluster

which is just a known warning, and it will be eventually fixed on the OpenShift side in the future.