Fuel snapshot cli command always download snapshot to current directory, even if --dir specified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Vitalii Kulanov | ||
7.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Mitaka |
Won't Fix
|
Medium
|
Vitalii Kulanov | ||
Newton |
Fix Committed
|
Medium
|
Vitalii Kulanov |
Bug Description
In fuel cli we have two options:
To download diagnostic snapshot to current directory:
fuel snapshot
To download diagnostic snapshot to specific directory:
fuel snapshot --dir path/to/directory
And there is no option to not download it, just trigger creation via cli.
It can be pain for multigigabytes snapshot(simply not enough space on the disk to store two copies). User may want to get copy from /var/www/
I propose to change this code:
https:/
To download only when --dir parameter is specified, and not download to current dir when executing via:
fuel snapshot
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 6.1 |
Changed in fuel: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: module-client |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Alexander Bozhenko (alexbozhenko) |
Changed in fuel: | |
assignee: | Alexander Bozhenko (alexbozhenko) → Fuel QA Team (fuel-qa) |
summary: |
- Fuel snapshot cli command doesn't allow not to download snapshot to - current directory + Fuel snapshot cli command doesn't allow to download snapshot to current + directory |
summary: |
- Fuel snapshot cli command doesn't allow to download snapshot to current - directory + Fuel snapshot cli command always download snapshot to current directory, + even if --dir specified |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Triaged |
no longer affects: | fuel/8.0.x |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Sorry, we have soft code freeze in action in 6.1. Moving this request to 7.0. Maybe we will have time to fix it in 6.1 timeframe.