Cron <root@rockstor> /opt/rockstor/bin/st-snapshot 1 \*-*-*-*-*-* / what does this mean?

Hi All,

since the lastest test release 3.9.1-13 I get on a daily base the follwing message via email - anything I should do about it?
or is it just an information and all is good?

thx

Traceback (most recent call last):
File "/opt/rockstor/bin/st-snapshot", line 45, in <module>
sys.exit(scripts.scheduled_tasks.snapshot.main())
File "/opt/rockstor/src/rockstor/scripts/scheduled_tasks/snapshot.py", line 94, in main
validate_snap_meta(meta)
File "/opt/rockstor/src/rockstor/scripts/scheduled_tasks/snapshot.py", line 38, in validate_snap_meta
raise Exception('share_name missing from meta. {}'.format(meta))
Exception: share_name missing from meta. {u'writable': True, u'visible': False, u'prefix': u'rm_share', u'share': u'rm_share', u'max_count': u'14'}

@glenngould Are yes:

I should have posted an indication on this side effect in the testing channel releases thread. Essentially, as is expected from time to time, the testing channel had a breaking update that was later fixed by the following release:

The issue details what happened:
https://github.com/rockstor/rockstor-core/issues/1809

and the fix introduced in 3.9.1-11:

https://github.com/rockstor/rockstor-core/pull/1812

details the following requirement:

N.B. as with the pool api scheduled scrub task fix, it will be necessary for users to delete and re-create all their existing scheduled snapshot tasks (post this pr) in order that their prior function (pre share api change) be restored.

Hope that covers it. Upon the next stable release there is the intention to detail this requirement but I neglected to surface it for testing in the referenced thread.

Hope that helps.

2 Likes

OK, thank you-will try to create new tasks and see if there is any difference!