-
Notifications
You must be signed in to change notification settings - Fork 139
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
Scheduled shutdown task fails due to type issue #2805
Comments
Based on the referenced issue #2807 this use case could be addressed possibly with changing the
|
I'm working on the referenced/linked issue in #2805 (comment), so will add this change according there. And if all is well we can close this issue as a duplicate. |
Add type hints to the shutdown/reboot run_command() wrapper parameters in osi.py, and to command.py's use of these wrappers. Includes fix for legacy inadvertent integer in delay during scheduled task calls.
I've now split this out into it's own pull request: there were a few comment updates etc and shutdown/reboot specific changes that make it cleaner that way. PR currently under test. |
…fails-due-to-type-issue Scheduled shutdown task fails due to type issue #2805
Closing as: |
Thanks to user aymenSo, it appears that a scheduled shutdown task fails ultimately due to a type error, which results in a low-level exception during the attempt to execute the
shutdown
program.this can likely be traced back to this part of the code:
rockstor-core/src/rockstor/storageadmin/views/command.py
Lines 304 to 310 in 6c86e38
[phillxnet EDIT]
As documented in the forum thread, thedelay
variable should be populated with+3
instead of just3
following theshutdown
man page:https://man7.org/linux/man-pages/man8/shutdown.8.html
Should be an easy fix, however, not sure how one would design a test to this (or whether that is necessary) without shutting down the system every time :) (maybe trigger the shutdown and then cancel it within the delay time?).
Forum reference: https://forum.rockstor.com/t/error-on-shutdown-task/9313
The text was updated successfully, but these errors were encountered: