Fuel client shouldn't throw traceback on Ctrl-C

Bug #1518971 reported by Mikhail Samoylov
6
This bug affects 1 person
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: 959b06c5ef8143125efd1727d350c050a922eb12
      build_id: '172'
      build_number: '172'
      feature_groups:
      - mirantis
      fuel-agent_sha: 61f741f4d89a3f1095dd8b494f82695fb69153d6
      fuel-createmirror_sha: 22a7aacd95bbdca69f9e0f08b70facabdec8fb28
      fuel-library_sha: 31aa9fb129a8b8739f8ca6ea186caa3c9f46820f
      fuel-nailgun-agent_sha: 3e9d17211d65c80bf97c8d83979979f6c7feb687
      fuel-nailgun_sha: f8ba3f9cd449363f1c08621307e7504c304c29ae
      fuel-ostf_sha: 9690a2de829d3b063ed1e64b0b10dde39f711dc0
      fuel-upgrade_sha: 1e894e26d4e1423a9b0d66abd6a79505f4175ff6
      fuelmain_sha: 266f9b374934c64629a84b5146632cc0de70ac91
      fuelmenu_sha: 06bbcebed6c8d0b0f9279e2997d2f958c800e98c
      network-checker_sha: a57e1d69acb5e765eb22cab0251c589cd76f51da
      openstack_version: 2015.1.0-8.0
      production: docker
      python-fuelclient_sha: e685d68c1c0d0fa0491a250f07d9c3a8d0f9608c
      release: '8.0'
      shotgun_sha: c377d163519f6d10b69a654019d6086ba5f14edc
shotgun_sha: c377d163519f6d10b69a654019d6086ba5f14edc

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://drive.google.com/a/mirantis.com/file/d/0B2SenDuhfXPlYWZhdnB4Vy12bzg/view

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Please attach diagnostic snapshot

Changed in fuel:
status: New → Incomplete
Revision history for this message
Mikhail Samoylov (msamoylov) wrote :

Screen with error.

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
Revision history for this message
Artem Roma (aroma-x) wrote :

One does not simply stop ostf test execution by sending SIGINT to the fuel-client. OSTF and CLI are two different components that must properly interact with each other that is through sending appropriate HTTP requests to RESTful API of ostf-adapter. What are you stopping by CTRL-C is particular function of the client that constantly polls ostf for status of current test execution and print it interactively to output stream. Hence the behavior is in some way expected. IMO the real issue here is that we don't have separate command that stops/restart particular test run. With that being said I move this bug to incomplete. Feel free to update the description or create new bug about missing functionality.

Changed in fuel:
status: New → Incomplete
Revision history for this message
Mikhail Samoylov (msamoylov) wrote :

I think we need to improve/update (hide Traceback) output for Keyboard Interrupt while OSTF check is still running.
I will open new bug for START/STOP functionality.

Changed in fuel:
status: Incomplete → Confirmed
Dmitry Pyzhov (dpyzhov)
summary: - OSTF check don't stop through CLI
+ Fuel client shouldn't throw traceback on Ctrl-C
Changed in fuel:
importance: Medium → Low
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 8.0 → 9.0
Dmitry Pyzhov (dpyzhov)
tags: added: module-client
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
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.