`urbackupclientctl add-backupdir` is broken

Removing backup dirs works:

$ urbackupclientctl remove-backupdir -n pgsql
$ urbackupclientctl list-backupdirs
No directories are being backed up

Adding backup dirs does not:

$ urbackupclientctl add-backupdir -n root --path / -x
$ echo $?
$ urbackupclientctl list-backupdirs
No directories are being backed up

/var/log/urbackupclient.log with LOGLEVEL=debug in /etc/default/urbackupclient:

2023-11-24 19:55:37: ClientService cmd: SAVE BACKUP DIRS#pw=<stripped>&all_virtual_clients=1&enable_client_paths_use=1&dir_0=&dir_0_name=root/follow_symlinks,symlinks_optional,one_filesystem,share_hashes&dir_0_group=0
2023-11-24 19:55:37: rc=0 hasError=true state=0

As you can see, this contains hasError=true. This doesn’t seem to mean anything, because so does getting backup dirs which works fine:

2023-11-24 19:55:50: ClientService cmd: GET BACKUP DIRS#pw=<stripped>
2023-11-24 19:55:50: rc=0 hasError=true state=0

Versions used:

  • UrBackup Client Controller v2.5.25.0
  • UrBackup Client Backend v2.5.25.0

Tested on two clients.

Client auto-update is enabled on the server.

Server is on Infscape 1.11.3. I attempted to find out what UrBackup version that translates to, but the Infscape changelog (https://appupdate2.urbackup.org/amd64/production/changelog.pdf) does not mention this version…

@uroni May I provide straces in private?

Thanks. Can reproduce. Will be fixed.
Though, I also cannot delete them as well – will be fixed as well.

Temp work-around:

urbackupclientctl add-backupdir -n root --path // -x

(two slashes)

Just to mention, I’ve reported that about a year ago:

Personally I think a nice bug tracker would make live easier to follow those issues…