Closed markcocker closed 5 years ago
It sounds like something went wrong in Zowe's underlying Create.uss() call. The key line of output seems to be this one:
[ZosmfRestClient.js:70] Encountered an error trying to parse causeErrors as JSON - causeErrors is likely not JSON format
I suspect that something that's expecting to receive an ImperativeError instead received garbage, rethrew it, and that caused a similar problem higher up the stack.
I suspect our code isn't being as tolerant of weird responses from Zowe APIs as it could be. I've noted that when an Error is caught the cause is usually set to an Object, but it's sometimes a stringified version of that Object, and sometimes to a plain old string. I'll add some code to try and cope with each variation out of Create.uss() rather than assuming consistency.
Thanks. As our z/OSMF server was restarted, I had to recreate the error by creating a new z/OSMF profile with an invalid port. The symptoms look the same and the error message is much better now Problem is: z/OSMF REST API Error: http(s) request error event called Error: connect ECONNREFUSED 9.20.5.0:65000
.
zowe cics-deploy push bundle --name INVOKE --targetdir /u/cicprov/mnt/CICPY000/bundles --overwrite --zosmf-p invalid
Command Error:
A failure occurred during CICS bundle pushing.
Reason = A problem occurred attempting to create directory '/u/cicprov/mnt/CICPY000/bundles/cics-nodejs-invoke_1.0.0'. Problem is: z/OSMF REST API Error:
http(s) request error event called
Error: connect ECONNREFUSED 9.20.5.0:65000
~/.zowe/zowe/logs/zowe.log shows: