Fuel client shouldn't throw traceback on Ctrl-C
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Low
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
Newton |
Confirmed
|
Low
|
Fuel Sustaining |
Bug Description
release_versions:
2015.1.0-8.0:
VERSION:
api: '1.0'
astute_sha: 959b06c5ef81431
build_id: '172'
build_number: '172'
feature_
- mirantis
fuel-
fuel-
fuel-
fuel-
fuel-
fuel-
fuel-
fuelmain_sha: 266f9b374934c64
fuelmenu_sha: 06bbcebed6c8d0b
network-
openstack
production: docker
python-
release: '8.0'
shotgun_sha: c377d163519f6d1
shotgun_sha: c377d163519f6d1
Steps to reproduce.
1. Run OSTF check for any env (fuel health --env 1 --force --check smoke,sanity)
2. Abort (Ctrl+C) with the keyboard OSTF test before test end
3. Run OSTF check again
Current results: Through WebUI we can see that OSTF check don't stopped. We canno't run test again because previously launched the test is not completed
Expected Result: we need to send command Stop Test through WebAPI after hitting Ctrl+C in CLI
Also:
1. No traceback for Keybord OSTF test interruption
2. Test stop after sending Ctrl+C
Dump:
https:/
description: | updated |
Changed in fuel: | |
status: | Incomplete → New |
assignee: | Fuel QA Team (fuel-qa) → Fuel Python Team (fuel-python) |
tags: |
added: area-python removed: ostf |
summary: |
- OSTF check don't stop through CLI + Fuel client shouldn't throw traceback on Ctrl-C |
Changed in fuel: | |
importance: | Medium → Low |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: module-client |
Please attach diagnostic snapshot