Py3.6 Scheduled tasks import paths fix, snapshot & scub #2570 #2585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix missing import paths for Py3.6. Follow-up/counter-part to the test-lead pull request #2579 - indicating we have a lack of test coverage here as these failing imports were not uncovered by our tests as the shutdown one was in the referenced pull request.
Affected snapshot & scrub tasks post the Py3.6 transition. Copywrite date and http to https updated on changed files.
Fixes #2570
Testing:
Scheduled Snapshot task
A Web-UI scheduled snapshot (every 5 mins with 2 limit) was created and observed to be instantiated within CRON:
The resulting Web-UI schedule was updated and expected snapshots were created:
Scheduled Scrub task
A Web-UI scheduled scrub (every 5 mins) and a very small pool was created and seen to be instantiated by CRON:
And a subsequent scheduled scrub was also observed within the logs:
The resulting Web-UI schedule was updated:
and the Pool scrub tab also indicated the scheduled scrubs as expected: