-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] zos_operator throws TypeError when wait_time_s is specified #391
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine from here.
Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Updated changes return a result (below), what is new in the response is the
|
Signed-off-by: ddimatos <[email protected]>
Signed-off-by: ddimatos <[email protected]>
Regression with updated responses: 100% regression success, internal link/log For the long running command which is commented out, we need a MVS command that can take a while to run, they all average 1/2 - 1 second , not long enough to evaluate. I do have a long running command I used that can not to be publicly shared that I tested with and it all ran fine. I will look for a valid command we can share by discussing it with some of the system admins. In the case of the long running command it worked as designed. Command sanitized for reasons noted. Once it reached 50 seconds it returned. Even though the wait_time_s did work I do think there is room for improvement and opened this issue #398
|
Also addresses #377 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, this refactor removes unnecessary steps and simplifies the verbose and wait logic.
SUMMARY
After ZOAU implemented timeout option in opercmd support was missing from zos_operator. Changed the opercmd.execute_command call to use the latest interface and explicitly provide the timeout value, had to be done this way since zoau python utils does a validation in this value over kwargs.
Added the case when wait_time_s is 0 to default to 1 and be true to the docs "When set to 0, the system default is used".
Also changed the test to now validate for timeouts and enabled the quick delay test.
Update, in addition to the original issue these updates are have included in this PR:
fixes #389
fixes #377
ISSUE TYPE
COMPONENT NAME
zos_operator
ADDITIONAL INFORMATION