Avoid losing the snapshot list on configuration reload
Goal
The list of snapshots is lost after sending a reload signal
2022/03/23 02:39:17 snapshots.go:57: [DEBUG] snapshot: {oldest5@snapshot_20220323023741 2022-03-23 02:38:51 +0000 UTC 2022-03-23 02:37:41 +0000 UTC 0 45099008 oldest5 0}
...
2022/03/23 02:40:27 main.go:277: [INFO] Reloading configuration
2022/03/23 02:40:27 config.go:58: [DEBUG] Config loaded
2022/03/23 02:40:27 manager.go:92: [DEBUG] Using "zfs" thin-clone manager.
2022/03/23 02:40:27 pool_manager.go:269: [INFO] Discovering: /var/lib/dblab/oldest5
2022/03/23 02:40:27 pool_manager.go:299: [DEBUG] Data &{oldest5 zfs 0001-01-01 00:00:00 +0000 UTC oldest5 /var/lib/dblab clones data sockets observer {{0 0} 0 0 0 0} empty}
2022/03/23 02:40:27 pool_manager.go:309: [INFO] 2022-03-23 02:37:41 +0000 UTC
2022/03/23 02:40:27 pool_manager.go:250: [INFO] Available storage pools: [oldest5]
2022/03/23 02:40:27 pool_manager.go:251: [INFO] Active pool: oldest5
2022/03/23 02:40:27 main.go:283: [INFO] Configuration has been reloaded
2022/03/23 02:40:34 logging.go:16: [INFO] -> POST /clone
2022/03/23 02:40:34 mode_local.go:315: [INFO] no snapshots for pool oldest5
2022/03/23 02:40:34 errors.go:21: [ERROR] [ERROR] - POST /clone - failed to create clone: failed to find the latest snapshot: no snapshot found
2022/03/23 02:40:34 util.go:31: [DEBUG] Response: no snapshot found