Bug 1168067

Summary: "Error 200 OK" when modifying a support case (CSP)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Lucas Costi <lcosti>
Component: Web ConsoleAssignee: Tomas Hofman <thofman>
Status: CLOSED WONTFIX QA Contact: Pavel Jelinek <pjelinek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bbaranow, cdewolf, hbraun, hpehl, jkudrnac, msochure, pjelinek, thofman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-29 15:54:38 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
Error 200 OK when submitting changes. none

Description Lucas Costi 2014-11-26 02:19:09 UTC
Created attachment 961443 [details]
Error 200 OK when submitting changes.

Description of problem:

When viewing and modifying the details of a support case using the Management Console, a red banner with "Error 200 OK" is presented when submitting the changes using the "Update Details" button (see the attached screenshot). 

The submitted change is made successfully. 

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

Actual results:
Red "Error 200 OK" confirmation banner. 

Expected results:
A friendlier non-error confirmation message.

Comment 3 Rostislav Svoboda 2015-06-22 14:26:35 UTC
qa_acking, we should be able to check it.

Not sure if it is really RFE, hope the return code is just incorrectly processed.

Comment 5 Tomas Hofman 2015-07-17 09:36:21 UTC
The problem seems to be that server is returning empty empty response. Angular is expecting JSON, so the parsing fails and .error() is triggered instead of .success()

Comment 6 Tomas Hofman 2015-07-20 15:47:32 UTC
Some more info:

URL that is called is https://api.access.redhat.com/rs/cases/01478517?redhat_client=EAP 6.x&account_number=1460290

Response headers:

Access-Control-Allow-Headers: Content-Type, X-PINGOTHER, X-Omit, Authorization
Cache-Control: private, no-cache
Connection: keep-alive
Content-Length: 0
Date: Mon, 20 Jul 2015 15:25:21 GMT
Expires: Wed, 31 Dec 1969 19:00:00 EST
Location: https://api.access.redhat.com/rs/cases/01478517
Server: Apache-Coyote/1.1
Strata-Code: 200
Strata-Message: OK
access-control-allow-credentials: true
access-control-allow-methods: POST, GET, OPTIONS, DELETE, PUT
access-control-allow-origin: http://localhost:9990
access-control-expose-headers: Content-Length, Location, View-Uri, view_uri, Uri
access-control-max-age: 1728000

Response content is empty.


After talking to kroberts, it looks the fix is already available (https://github.com/redhataccess/stratajs/commit/6d671a4ecce79586281a3ea44fab71cfa5794e4b).

Comment 11 JBoss JIRA Server 2016-01-25 16:56:10 UTC
Harald Pehl <hpehl> updated the status of jira JBEAP-1389 to Closed

Comment 12 Tomas Hofman 2016-11-29 15:21:51 UTC
Hello Miroslav, I think this can be closed as the support module was already removed from the product [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1379469

Comment 13 Red Hat Bugzilla 2023-09-14 02:51:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days