snapshot failed time to time because IUCV failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zVM Cloud Connector |
Confirmed
|
Medium
|
nafeiyang |
Bug Description
https:/
https:/
[2018-05-10 19:44:24] [ERROR] Failed to check iucv status on capture source vm QYR00011 with error (Error) ULTVMU0315E IUCV socket error sending command to QYR00011. cmd: pwd, rc: 4, rs: 111, out: ERROR: ERROR connecting socket:
[2018-05-10 19:44:24] [ERROR] Failed to capture guest 'QYR00011' to generate image 'd1b4ce01-
[2018-05-10 19:44:24] [ERROR] (127.0.0.1:46488) Traceback (most recent call last):
File "/usr/lib/
return_data = api_func(*api_args, **api_kwargs)
File "/usr/lib/
compress_
File "/usr/lib/
compress_
File "/usr/lib/
msg=msg)
SDKGuestOperati
[2018-05-10 19:44:24] [INFO] The msg <{u'rs': 5, u'overallRC': 300, u'modID': 10, u'rc': 300, u'output': u'', u'errmsg': u'Failed to capture userid QYR00011 to generate image, error: Failed to check iucv status on capture source vm QYR00011 with error (Error) ULTVMU0315E IUCV socket error sending command to QYR00011. cmd: pwd, rc: 4, rs: 111, out: ERROR: ERROR connecting socket:'}> lead to return internal error
[2018-05-10 19:44:24] [INFO] 10.32.202.49 "POST /guests/
summary: |
- snapshot failed time to time + snapshot failed time to time because IUCV failure |
it might be another issue that
[2018-05-10 19:44:19] [INFO] 9.114.224.65 "PUT /guests/ QYR00011/ nic/1000" status: 200 length: 77 headers: [('Content-Length', '77'), ('Content-Type', 'application/ json'), ('cache-control', 'no-cache')] exc_info: None QYR00011/ action" status: 200 length: 77 headers: [('Content-Length', '77'), ('Content-Type', 'application/ json'), ('cache-control', 'no-cache')] exc_info: None QYR00011/ power_state" status: 200 length: 79 headers: [('Content-Length', '79'), ('Content-Type', 'application/ json'), ('cache-control', 'no-cache')] exc_info: None
[2018-05-10 19:44:20] [INFO] 10.32.202.49 "POST /guests/
...
[2018-05-10 19:44:23] [INFO] 10.32.202.49 "GET /guests/
I doubt whether it's because instance startup and IUCV not able to talk now
so I'd suggest we reconsider IUCV connection to have some retry mechanism.....