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

Bug 1173074

Summary: Red Hat Access: Support stucked after upload failure
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: redhat-support-plugin-rhevAssignee: Josh Kinlaw <jkinlaw>
Status: CLOSED DUPLICATE QA Contact: Jiri Belka <jbelka>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.4.4CC: awels, ecohen, gklein, jbelka, jkinlaw, kroberts, lsurette, rbalakri, yeylon, ylavi
Target Milestone: ovirt-3.6.0-rc   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: subeng
Fixed In Version: redhat-support-plugin-rhev-3.6.0-8.el6.noarch.rpm Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-06 14:33:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Sub-Eng RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log
none
screenshot 1
none
screenshot 2 none

Description Jiri Belka 2014-12-11 12:08:03 UTC
Created attachment 967206 [details]
log

Description of problem:
i tried to "get" support while using Power8 host in my RHEVM setup. In new case it displays:

Successfully created case number 01314536

Failed to upload attachment RHEV Manager SOS Report to case 01314536 : Internal server error

Successfully uploaded attachment RHEV Manager Database Dump to case 01314536

Failed to upload attachment Host SOS Report/ibm-p8-rhevm-hv-01.klab.eng.bos.redhat.com to case 01314536

The in-progress wheel is running, seems to be stucked...

...but, I tried to search for my case and it displays:

Attachments

Filename	Description	Size	Attached	Attached By	Delete
sos_pgdump.tar	RHEV Manager Database Dump	2.6 MB	Dec 11, 2014 12:43:44 PM	Jiri Belka	Delete
ClockSkew-ibm-p8-rhevm-hv-01.klab.eng.bos.redhat.com4482032414311223972.txt	Clock Skew file for ibm-p8-rhevm-hv-01.klab.eng.bos.redhat.com	308.0 bytes	Dec 11, 2014 12:46:22 PM	Jiri Belka	Delete
sosreport-ibm-p8-rhevm-hv-01.klab.eng.bos.redhat.com-20141211114337.tar.xz	Host SOS Report/ibm-p8-rhevm-hv-01.klab.eng.bos.redhat.com	51.9 MB	Dec 11, 2014 12:46:13 PM	Jiri Belka	Delete

So some sos report was uploaded for power8 server.

FYI I don't see any ERROR in redhat-support-plugin-rhev.log file.


Version-Release number of selected component (if applicable):
redhat-support-plugin-rhev-3.4.0-4.el6ev.noarch
sos-2.2-68.el6.noarch
sos-3.1-1.1.pkvm2_1_1.6.noarch

How reproducible:
100%

Steps to Reproduce:
1. hosts -> power8 host -> right-click for Support
2. fill title and description
3. select manager sos and host sos for upload

Actual results:
failure and dialog is stucked

Expected results:
should work or at least dialog should not show in-progress wheel anymore

Additional info:

Comment 1 Jiri Belka 2014-12-11 12:08:30 UTC
Created attachment 967207 [details]
screenshot 1

Comment 2 Jiri Belka 2014-12-11 12:09:04 UTC
Created attachment 967208 [details]
screenshot 2

Comment 3 Yaniv Lavi 2015-08-25 13:45:29 UTC
Can you please ack this?

Comment 4 Yaniv Lavi 2015-08-25 13:46:31 UTC
Can you please provide the patches that resolve this issue?

Comment 5 Yaniv Lavi 2015-09-08 14:13:44 UTC
Do you know is this was included in the latest build to QE?

Comment 6 Josh Kinlaw 2015-09-08 18:45:37 UTC
This is a result of the client's request timing out before the file upload is complete. This will only occur on slower setups. The attachment is actually uploaded but the user receives an error because the 1 minute timeout is reached before the file finishes. I have tried to extend the session-timeout value in web.xml but it appears that JBoss is ignoring this setting. I removed some of the less important things that the SOS report was sending in an attempt to speed up the request. Hopefully this will resolve the issue. Other than that, the best we can do is wait for the next upgrade of JBoss and see if that setting is being accepted.

Comment 7 Yaniv Lavi 2015-10-06 14:33:28 UTC

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