120s Timeout results in None response. for long running commands

Question

120s Timeout results in None response. for long running commands

Closed this issue 8 months ago · 5 comments

2024-02-15T20:32:35.673Z : level : ERROR , message : move_rdfg_devices_from_src_rdfg failed: error:Bad or unexpected response from the storage volume backend API: Error PUT symmetrix resource. The status code received is None and the message is None.

"/opt/XXXXXX/lib/python3.8/site-packages/PyU4V/common.py", line 180, in check_status_code_success\n raise exception.VolumeBackendAPIException(\nPyU4V.utils.exception.VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Error PUT symmetrix resource. The status code received is None and the message is None."

rawstorage commented 8 months ago

Closed

Answer 1 · 2024-04-09T13:00:48.000Z

Published fix for 10.1.0.2

Answer 2 · 2024-07-04T18:10:54.000Z

I am facing the same issue with 9.x version. Is there any API in 10.1.0.2 for setting up customized timeout?

Thanks,
Sacheen Birhade

Answer 3 · 2024-07-05T10:45:51.000Z

Sacheen, this fix wasn't backported. you have the option to review the changes in this pull request and create your own fork of the code for your own install.

You can change the timeout in the new version in your connection string, conn = PyU4V.U4VConn(username='smc', password='smc', server_ip='ipaddress', verify=None, array_id='000220200226', timeout=300) . PyU4V 10.1 has this code and is capable of supporting older arrays, you can upgrade an external Unipshere to this code to avail of the fix.

Answer 4 · 2024-07-05T12:01:46.000Z

Thank you, Paul for your help as always.