| 2016-02-09 21:49:09 |
Pavel Chechetin |
bug |
|
|
added bug |
| 2016-02-10 12:55:40 |
Ilya Kutukov |
fuel: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2016-02-10 12:55:43 |
Ilya Kutukov |
fuel: importance |
Undecided |
High |
|
| 2016-02-10 12:55:46 |
Ilya Kutukov |
fuel: status |
New |
Confirmed |
|
| 2016-02-10 12:55:49 |
Ilya Kutukov |
fuel: milestone |
|
9.0 |
|
| 2016-02-10 12:55:59 |
Ilya Kutukov |
tags |
|
area-python |
|
| 2016-02-11 10:37:33 |
Dmitry Pyzhov |
tags |
area-python |
area-python team-upgrades |
|
| 2016-02-11 12:08:15 |
Dmitry Pyzhov |
tags |
area-python team-upgrades |
area-python |
|
| 2016-02-20 13:37:07 |
Dmitry Pyzhov |
tags |
area-python |
area-python team-upgrades |
|
| 2016-04-19 08:51:17 |
Fuel Devops McRobotson |
fuel: milestone |
9.0 |
10.0 |
|
| 2016-04-19 08:51:20 |
Fuel Devops McRobotson |
fuel/mitaka: importance |
Undecided |
High |
|
| 2016-04-19 08:51:20 |
Fuel Devops McRobotson |
fuel/mitaka: status |
New |
Confirmed |
|
| 2016-04-19 08:51:20 |
Fuel Devops McRobotson |
fuel/mitaka: milestone |
|
9.0 |
|
| 2016-04-19 08:51:20 |
Fuel Devops McRobotson |
fuel/mitaka: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2016-04-27 13:12:43 |
Dmitry Pyzhov |
fuel: assignee |
Fuel Python Team (fuel-python) |
Fuel Octane (fuel-octane-team) |
|
| 2016-04-27 13:12:50 |
Dmitry Pyzhov |
fuel/mitaka: assignee |
Fuel Python Team (fuel-python) |
Fuel Octane (fuel-octane-team) |
|
| 2016-05-12 13:45:42 |
Pavel Chechetin |
description |
There is no traceback in the logfile.
The absence of traceback complicates troubleshooting.
It turns out that fuel2 command with --debug options writes traceback but there is no traceback in the logfile anyway.
Steps to reproduce:
1. Put "raise Exception" somewhere in nailgun/extensions/cluster_upgrade/upgrade.py
2. Restart nailgun
3. Execute: octane upgrade-env 1
Actual behavior:
1. There is no traceback in the logfile.
Expected behavior:
1. There is a traceback in the logfile. |
There is no traceback in the logfile.
The absence of traceback complicates troubleshooting.
It turns out that fuel2 command with --debug option writes a traceback to the console output but there is no traceback in the logfile anyway.
Steps to reproduce:
1. Put "raise Exception" somewhere in nailgun/extensions/cluster_upgrade/upgrade.py
2. Restart nailgun
3. Execute: octane upgrade-env 1
Actual behavior:
1. There is no traceback in the logfile.
Expected behavior:
1. There is a traceback in the logfile. |
|
| 2016-05-12 13:55:39 |
Oleg S. Gelbukh |
fuel/mitaka: importance |
High |
Medium |
|
| 2016-05-12 13:55:42 |
Oleg S. Gelbukh |
fuel/mitaka: status |
Confirmed |
Won't Fix |
|
| 2016-05-12 13:55:49 |
Oleg S. Gelbukh |
fuel: assignee |
Fuel Octane (fuel-octane-team) |
Fuel Python (Deprecated) (fuel-python) |
|
| 2016-05-12 13:56:02 |
Oleg S. Gelbukh |
fuel: assignee |
Fuel Python (Deprecated) (fuel-python) |
Fuel Mixed (fuel-mixed-team) |
|
| 2016-05-12 13:58:18 |
Pavel Chechetin |
summary |
[fuel-octane] Nailgun doesn't write a traceback in the logfile in case of 500 code |
Nailgun doesn't write a traceback in the logfile in case of 500 code |
|
| 2016-05-13 09:48:38 |
Alexander Saprykin |
fuel: assignee |
Fuel Mixed (fuel-mixed-team) |
Alexander Saprykin (cutwater) |
|
| 2016-05-13 10:21:47 |
Alexander Saprykin |
fuel: status |
Confirmed |
Incomplete |
|
| 2016-05-16 08:53:46 |
Alexander Saprykin |
fuel: assignee |
Alexander Saprykin (cutwater) |
Fuel Sustaining (fuel-sustaining-team) |
|
| 2016-06-15 16:35:49 |
Dmitry Klenov |
fuel: status |
Incomplete |
Invalid |
|
