Freezer client reports misleading error when backup path is non-existant

Bug #1425591 reported by Zahari Zahariev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
In Progress
Undecided
sbartel

Bug Description

Freezer displays a misguiding error when you try to backup path or file that does not exist. The other starnge thing is although it returns a "Critical error" it still creates the backup containers for that execution.

Found in:
=========
zahari@zahari-z420:~$ freezerc --version
freezer version 1.1.2

Example:
========
zahari@zahari-z420:~$ swift list

zahari@zahari-z420:~$ freezerc --action backup --path-to-backup /tmp/kiss_me --container TEST199 --backup-name backup1
log file at /var/log/freezer.log
[*] Critical Error: Error: Please ALL the following options: --path-to-backup, --backup-name

zahari@zahari-z420:~$ swift list
freezer_TEST199
freezer_TEST199_segments
========

Correct behavior should be to report helpful error message that path is non-existant and to fail all further actions so no Swift containser should be created.

Tags: freezer
description: updated
sbartel (samuel-bartel)
Changed in freezer:
assignee: nobody → sbartel (samuel-bartel)
Changed in freezer:
status: New → In Progress
Revision history for this message
Deklan Dieterly (deklan) wrote :

sbartel, can you please update the status of this bug? Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.