Bug 1469798 - SUI : Fetching service data for some services shows error
Summary: SUI : Fetching service data for some services shows error
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Shveta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-11 20:58 UTC by Shveta
Modified: 2018-08-02 22:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 22:18:35 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
error (229.59 KB, image/png)
2017-07-27 21:39 UTC, Shveta
no flags Details
evm log (8.70 MB, application/zip)
2017-07-28 22:16 UTC, Shveta
no flags Details

Description Shveta 2017-07-11 20:58:47 UTC
Description of problem:


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

How reproducible:


Steps to Reproduce:
1. Created few services.
2. Some of them show data without error but few services when clicked on it shows error . Not sure what is special about these services. Screenshot with console attached.
3. 

Actual results:


Expected results:


Additional info:
Appliance - https://10.8.197.236/ui/service/services/5

Comment 2 Shveta 2017-07-11 20:59:46 UTC
Service name -> error_service

Comment 3 Chris Kacerguis 2017-07-12 01:32:28 UTC

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

Comment 4 Shveta 2017-07-27 21:39:21 UTC
Re-opening this as the BZ bug 1467569 is fixed in 5.8.1.5 but 
still seeing this issue .
CLicking on some services shows error as in attached screenshot.
Appliance: https://10.8.197.227/ui/service

Comment 5 Shveta 2017-07-27 21:39:41 UTC
Created attachment 1305659 [details]
error

Comment 7 Chris Hale 2017-07-28 19:57:39 UTC
I took a look and I see exactly what you see.  We don't really change the request per service to have different parameters so what works for one service should work for another.  Since I can't retrieve the service, I can't really tell you what Shveta might have done differently for these services that is causing these services to error out.

Comment 8 Chris Hale 2017-07-28 19:59:00 UTC
Can you provide the evm logs of this appliance so the API team can see what might be behind this 500 error?

Comment 9 Shveta 2017-07-28 22:16:45 UTC
Created attachment 1306044 [details]
evm log

Appliance : https://10.8.197.114/ui/service

Comment 11 Shveta 2018-08-02 22:18:35 UTC
Not seeing this issue anymore .Closing .


Note You need to log in before you can comment on or make changes to this bug.