| 2013-10-30 10:24:07 |
Andrey Danin |
bug |
|
|
added bug |
| 2013-10-31 09:41:57 |
Andrey Danin |
description |
Steps to reproduce:
1) Create cluster with Neutron VLAN.
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC. |
Fuel 3.2
Steps to reproduce:
1) Create cluster with Neutron VLAN.
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC. |
|
| 2013-10-31 20:35:59 |
Mike Scherbakov |
fuel: milestone |
|
4.1 |
|
| 2013-10-31 20:36:10 |
Mike Scherbakov |
fuel: importance |
Undecided |
Medium |
|
| 2013-11-01 10:16:53 |
Andrey Danin |
description |
Fuel 3.2
Steps to reproduce:
1) Create cluster with Neutron VLAN.
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC. |
Fuel 3.2
Steps to reproduce:
1) Create cluster with Neutron VLAN.
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC.
The problem is the 'allowed_networks' field is empty for new NICs. |
|
| 2013-11-01 10:20:43 |
Andrey Danin |
description |
Fuel 3.2
Steps to reproduce:
1) Create cluster with Neutron VLAN.
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC.
The problem is the 'allowed_networks' field is empty for new NICs. |
Fuel 3.2
Steps to reproduce:
1) Create cluster (tested with Neutron VLAN and Nova Network).
2) Add bootstrap node with one NIC to it. All networks whould be assigned to only NIC.
3) Shutdown the node and add a new one NIC for it.
4) Boot up the node and wait while information about the new NIC will be populated to Fuel.
5) Try to move networks to the new NIC.
Expected behavior:
You be able to move any network except for Admin to the new NIC.
Real behavior:
You can not move any network to the new NIC.
The problem is the 'allowed_networks' field is empty for new NICs. |
|
| 2013-11-01 10:36:11 |
Sergey Vasilenko |
bug |
|
|
added subscriber Sergey Vasilenko |
| 2013-11-05 08:38:43 |
Evgeniy L |
fuel: status |
New |
Confirmed |
|
| 2013-11-27 13:29:41 |
Dmitry Pyzhov |
fuel: assignee |
|
Dmitry Pyzhov (lux-place) |
|
| 2013-11-27 13:29:44 |
Dmitry Pyzhov |
fuel: importance |
Medium |
Low |
|
| 2013-12-10 11:33:42 |
Dmitry Pyzhov |
fuel: assignee |
Dmitry Pyzhov (lux-place) |
Fuel Python Team (fuel-python) |
|
| 2013-12-10 11:33:46 |
Dmitry Pyzhov |
fuel: importance |
Low |
Medium |
|
| 2013-12-17 11:51:07 |
Alexandr Notchenko |
fuel: assignee |
Fuel Python Team (fuel-python) |
Alexandr Notchenko (anotchenko) |
|
| 2013-12-17 11:51:22 |
Alexandr Notchenko |
fuel: status |
Confirmed |
In Progress |
|
| 2013-12-17 16:28:11 |
Alexandr Notchenko |
fuel: status |
In Progress |
Fix Committed |
|
| 2013-12-18 09:52:02 |
Dmitry Pyzhov |
fuel: status |
Fix Committed |
Invalid |
|
| 2013-12-18 12:42:00 |
Alexandr Notchenko |
fuel: status |
Invalid |
Confirmed |
|
| 2014-01-15 15:48:30 |
Alexandr Notchenko |
fuel: status |
Confirmed |
Won't Fix |
|
| 2014-08-07 11:58:01 |
Aleksey Kasatkin |
fuel: assignee |
Alexandr Notchenko (anotchenko) |
Fuel Python Team (fuel-python) |
|
| 2014-08-07 13:00:16 |
Aleksey Kasatkin |
fuel: status |
Won't Fix |
Invalid |
|
