System_RDR_File_Manage gives "Specified function does not exist"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zVM Cloud Connector |
Confirmed
|
Medium
|
cao biao |
Bug Description
I made the next call:
curl -sk https:/
So this is een deployment of a captured image on a existing guest. As a result the function gives an error back:
{'errmsg': "Failed to purge reader of 'EMP'. SMUT error: SMUT request "
"failed. RequestData: 'changevm EMP purgerdr', Results: '{'rs': "
"12, 'errno': 0, 'strError': u'ULGSMC5900E Specified function "
"does not exist', 'overallRC': 8, 'rc': 900, 'response': "
'overall rc: 8, rc: 900, rs: 12, errno: 0, cmd: sudo '
"-k spoolids=all, out: API issued : System_
"API issued : System_
'modID': 1,
'output': '',
'overallRC': 8,
'rc': 900,
'rs': 12}
At first I thought about an authorisation error because the function was not in de name list (we choose to authorize only the functions which are necessary), but after adding the function to the namelist in zvm, it still gave the same error.
We see the call coming to zvm (an example):
00025 2019-01-09 12:52:15 REQUE DMSRSRQN REQ_ACC VSMREQIU AF_IUCV CLDCONO1
00026 2019-01-09 12:52:15 ENTRY DMSRSRQT REQ_IUCV VSMREQIU
00027 2019-01-09 12:52:15 ENTRY DMSWSWRK CALLDIRM VSMWORK1 on VSMWORK1 req(23294719) for(EMP) SYSTEM_
00028 2019-01-09 12:52:15 REQUE DMSRSRQT REQ_IUCV VSMREQIU CLDCONO1 SYSTEM_
00029 2019-01-09 12:52:15 ENTRY DMSWSSMP Work_SMP VSMWORK1 SYSTEM_
00030 2019-01-09 12:52:15 ENTRY DMSSIPTS Work_PTS VSMWORK1 SYSTEM_
The strangest is the " at the end of the command (after all). With a hex editor this is a 00 token.
So maybe a translation error between smcli and the smapi.
Environment: z/VM 6.4 build 1801
Suse 12.3 Linux guest and Cloud Connector
CLDCONO1 is the cloud connector linux working on ip 10.35.4.60
Emp is the new linux guest
description: | updated |
description: | updated |
Changed in python-zvm-sdk: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Bill, can you take a look?