-
Notifications
You must be signed in to change notification settings - Fork 138
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
Py3.6 System - Scheduled tasks - snapshot & scrub #2570
Comments
We have a potentially corresponding unit test failure as follows:
Unit test failure likely unrelated and now fixed by #2581 |
Linking to related code changes having taken place since this issue was created #2579 where import fixes may have affected this issue. Re-testing now. |
We have a running schedule instantiated via Web-UI with consequent triggers from cron evident:
But:
Given the above we have a continuation her of: #2579 |
again, unrelated to this specifically, but I think there is another instance where the crontab needs to be adjusted:
|
@Hooverdan96 Thanks. Yes I'm preparing a pr for both instances now. And have broadened the commit messages accordingly. We are getting there here I think. And these took longer as there was no test coverage !! |
Fix missing import paths for Py3.6. Affected snapshot & scrub tasks post the Py3.6 transition. Copywrite date and http to https updated on changed files.
…cheduled_tasks_-_snapshot Py3.6 Scheduled tasks import paths fix, snapshot & scub rockstor#2570
Closing as: |
Post #2567 in testing branch we have a failure within our Web-UI to reflect a successfully executed snapshot task:
Reproducer - Create a snapshot of say the "home" share, limited to 2 copies with a 5 minute schedule. The resulting task is run by crontab but we fail (via our created script and call back, to update our database on the resulting execution and associated info:
The text was updated successfully, but these errors were encountered: