Oracle ZFS Storage Appliance: Failed to upload SupportBundle after upgrade to 2013.1.1.6

Asset ID:	1-72-2048865.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2048865.1 : Oracle ZFS Storage Appliance: Failed to upload SupportBundle after upgrade to 2013.1.1.6

Applies to:

Sun ZFS Storage 7120 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Sun ZFS Storage 7420 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

After upgrading the ZFS Storage Appliance ak-2013.06.05.1.6 or higher, support bundle fails to upload.

From the jobs.txt log:

Uploading bundle ... akbundle: failed: 56

From the scrk.ak.txt log:

Fri Feb 20 16:40:30 2015
nvlist version: 0
service = supportfiles
method = upload
arguments = (embedded nvlist)
nvlist version: 0
file = ak.793aebda-ca0f-cc49-e305-80758593db3f.tar.gz
root = /upload/uuid/793aebda-ca0f-cc49-e305-80758593db3f
(end arguments)

result = (embedded nvlist)
nvlist version: 0
status = error_other
code = 0x0
akerrno = 502
akerrmsg = curl: (56) Received HTTP code 400 from proxy after CONNECT
(end result)

AK error message: Received HTTP code 400 from proxy after CONNECT

Changes

Upgraded to 2013.1.1.6

Cause

Appliance Firmware ak-2013.06.05.1.6 or higher transitions from supportfiles infrastructure to new and more secure transport.oracle.com.

With this change new support bundle sends the content length in the Connect message.

Some of the proxy - example Bluecoat - do not expect the content length in the connect message header and fails.

Information from Wikipedia about HTTP Connect tunneling: http://en.wikipedia.org/wiki/HTTP_tunnel

HTTP CONNECT tunneling

A variation of HTTP tunneling when behind an HTTP Proxy Server is to use the "CONNECT" HTTP method.[1][2]

In this mechanism, the client asks an HTTP Proxy server to forward the TCP connection to the desired destination. The server then proceeds to make the connection on behalf of the client.
Once the connection has been established by the server, the Proxy server continues to proxy the TCP stream to and from the client.
Note that only the initial connection request is HTTP - after that, the server simply proxies the established TCP connection.

This mechanism is how a client behind an HTTP proxy can access websites using SSL (i.e. HTTPS).

Not all HTTP Proxy Servers support this feature, and even those that do, may limit the behaviour (for example only allowing connections to the default HTTPS port 443, or blocking traffic which doesn't appear to be SSL).

You can see the below reply while doing akbundle manually :

curl: (56) Received HTTP code 400 from proxy after CONNECT

You can refer to below bugs for detailed explanation B
ug 20802636 - akbundle sends content length in header during connect

Solution

Upgrade to the latest Appliance firmware i.e. ak-2013.06.05.6.2 (OS8.6.2/2013.1.6.2) or higher.

Possible future solution will be available once the Curl Library is updated on ZFS Storage Appliance.

But currently there is no ETA for the same. Refer Bug 20587990 - Unable to send in bundles when proxy uses HTTP Connect tunneling

References

<NOTE:1574071.1> - Sun Storage 7000 Unified Storage System: How to troubleshoot Phone Home (i.e. scrk) connection issues
<NOTE:166650.1> - Working Effectively With Oracle Support - Best Practices
<BUG:20587990> - UNABLE TO SEND IN BUNDLES WHEN PROXY USES HTTP CONNECT TUNNELING
<BUG:20802636> - AKBUNDLE SENDS CONTENT LENGTH IN HEADER DURING CONNECT

Attachments

This solution has no attachment