Complete
Details
Assignee
Vladimir VinogradenkoVladimir VinogradenkoReporter
Scott WScott WDue date
Jul 01, 2020Components
Fix versions
Affects versions
Priority
Low
Details
Details
Assignee
Vladimir Vinogradenko
Vladimir VinogradenkoReporter
Scott W
Scott WDue date
Jul 01, 2020
Components
Fix versions
Affects versions
Priority
More fields
More fields
More fields
Katalon Platform
Katalon Platform
Katalon Platform
Created May 21, 2020 at 1:41 PM
Updated July 1, 2022 at 4:53 PM
Resolved June 9, 2020 at 3:49 PM
It appears FreeNAS has included a version of rclone in 11.3-U3 that is affected by this bug:
https://github.com/rclone/rclone/issues/4051
The result of including this version of rclone, failing to test it and then shipping it in update 11.3-U3 means that Google Team Drives used for Cloud Sync tasks no longer work. When the Cloud Sync tasks run, they upload to my personal Google Drive rather than the shared Team Drive.
Here's the rclone config used by FreeNAS for one of these now-broken Cloud Sync tasks. I've removed my token and fudged the team_drive ID, but you can see how the config includes both team_drive and root_folder_id, which is the root of the bug.
[remote]
token = {"access_token":"","token_type":"Bearer","refresh_token":"","expiry":"2020-05-21T08:59:59.458838805-05:00"}
team_drive = 0AI_3p73b543uXXXXXX
client_id =
client_secret =
type = drive
root_folder_id = root
folder = tank/iocage
fast_list = True
What is the best way to downgrade rclone so I can resume my Cloud Sync tasks? Is that even possible? Is there a way to pass --drive-root-folder-id "" to rclone?