[upgrade][8.0] Unpredictable behaviour of the script in case of disconnected terminal

Bug #1547819 reported by Vladimir Khlyunev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
Unassigned
7.0.x
Won't Fix
Medium
Registry Administrators
8.0.x
Won't Fix
Medium
Registry Administrators
Mitaka
Won't Fix
Medium
Registry Administrators
Newton
Won't Fix
Medium
Registry Administrators

Bug Description

If user will close the terminal by any reason (networking issues, kernel panic, missclick, etc) the octane can receive SIGHUP in any state (e.g. when one of containers was shut down) which leads to unpredictable state of fuel node. We should handle it.

Dmitry Klenov (dklenov)
tags: added: area-python
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

version

expected result

steps to reproduce

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
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

We passed SCF for 9.0. Moving the medium priority bug to 10.0 release.

Changed in fuel:
milestone: 9.0 → 10.0
Revision history for this message
Anton Matveev (amatveev) wrote :

octane specific, moving to won't fix due to shifted priorities

Changed in fuel:
status: Triaged → Won't Fix
Curtis Hovey (sinzui)
Changed in fuel:
assignee: Registry Administrators (registry) → nobody
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.