| 2015-09-16 09:45:41 |
Swann Croiset |
bug |
|
|
added bug |
| 2015-09-16 09:46:52 |
Swann Croiset |
description |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appear when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she already assign more than 1 node with other roles
Warkaround:
assign the influxdb_grafana role BEFORE any assignement of other role |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appear when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Warkaround:
assign the influxdb_grafana role BEFORE any assignement of other role |
|
| 2015-09-16 09:47:55 |
Swann Croiset |
description |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appear when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Warkaround:
assign the influxdb_grafana role BEFORE any assignement of other role |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appears when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Warkaround:
assign the influxdb_grafana role BEFORE any assignement of other role |
|
| 2015-09-16 09:51:59 |
Swann Croiset |
description |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appears when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Warkaround:
assign the influxdb_grafana role BEFORE any assignement of other role |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appears when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Workaround:
assign the influxdb_grafana role BEFORE assignement of 2 other roles |
|
| 2015-09-16 10:08:47 |
Andrey Danin |
description |
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appears when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Workaround:
assign the influxdb_grafana role BEFORE assignement of 2 other roles |
Affects: Fuel 7.0 RC2
Context:
We use custom roles for LMA plugins, these roles are described for example like this for the InfluxDB-Grafana plugin :
node_roles.yaml:
influxdb_grafana:
name: 'InfluxDB Grafana'
description: 'Install InfluxDB and Grafana'
has_primary: false
public_ip_required: false
weight: 100
limits:
max: 1
conflicts:
- controller
- compute
- cinder
- ceph-osd
Steps to reproduce:
0/ install plugin LMA Influxdb grafana (master version)
1/ enable and configure the plugin (settings tab in Fuel UI)
2/ assign one node with controller node (nodes tab in Fuel UI)
3/ assign one node with compute node (nodes tab in Fuel UI)
4/ assign one node with the influxdb_grafana role
Expected results:
step #4 must be possible
Actual results:
step #4 is not possible, the role is 'locked' (cannot be selected)
a warning message indicates 'At most 1 InfluxDB Grafana nodes are allowed'
This message is inaccurate since there is not yet one inlfuxdb_grafana node.
Also, this works fine if we skip the step #2 (in other words, the bug appears when more than 1 node in conflicts list is assigned)
Impacts:
The user cannot deploy the LMA influxdb-grafana plugin if he/she has already assigned more than 1 node with other roles
Workaround:
assign the influxdb_grafana role BEFORE assignement of 2 other roles |
|
| 2015-09-16 11:01:39 |
Vitaly Kramskikh |
bug task added |
|
fuel |
|
| 2015-09-16 11:01:52 |
Vitaly Kramskikh |
fuel: status |
New |
Confirmed |
|
| 2015-09-16 11:01:54 |
Vitaly Kramskikh |
fuel: importance |
Undecided |
High |
|
| 2015-09-16 11:01:59 |
Vitaly Kramskikh |
fuel: assignee |
|
Fuel UI Team (fuel-ui) |
|
| 2015-09-16 11:02:05 |
Vitaly Kramskikh |
fuel: milestone |
|
7.0 |
|
| 2015-09-16 11:02:13 |
Vitaly Kramskikh |
nominated for series |
|
fuel/8.0.x |
|
| 2015-09-16 11:02:13 |
Vitaly Kramskikh |
bug task added |
|
fuel/8.0.x |
|
| 2015-09-16 11:02:25 |
Vitaly Kramskikh |
nominated for series |
|
fuel/7.0.x |
|
| 2015-09-16 11:02:25 |
Vitaly Kramskikh |
bug task added |
|
fuel/7.0.x |
|
| 2015-09-16 11:02:33 |
Vitaly Kramskikh |
fuel/7.0.x: status |
New |
Won't Fix |
|
| 2015-09-16 11:02:37 |
Vitaly Kramskikh |
fuel/7.0.x: importance |
Undecided |
High |
|
| 2015-09-16 11:02:43 |
Vitaly Kramskikh |
fuel/7.0.x: assignee |
|
Fuel UI Team (fuel-ui) |
|
| 2015-09-16 11:02:46 |
Vitaly Kramskikh |
fuel/7.0.x: milestone |
|
7.0 |
|
| 2015-09-16 11:02:50 |
Vitaly Kramskikh |
fuel/8.0.x: milestone |
7.0 |
8.0 |
|
| 2015-09-16 13:55:36 |
Vitaly Kramskikh |
fuel/7.0.x: importance |
High |
Medium |
|
| 2015-09-16 13:55:38 |
Vitaly Kramskikh |
fuel/8.0.x: importance |
High |
Medium |
|
| 2015-10-01 17:00:53 |
Simon Pasquier |
fuel-plugins: status |
New |
Confirmed |
|
| 2015-10-01 17:01:03 |
Simon Pasquier |
fuel-plugins: assignee |
|
LMA-Toolchain Fuel Plugins (mos-lma-toolchain) |
|
| 2015-10-12 17:21:44 |
Dmitry Pyzhov |
bug task deleted |
fuel/8.0.x |
|
|
| 2015-10-16 12:46:54 |
Vitaly Kramskikh |
fuel: importance |
Medium |
High |
|
| 2015-10-22 03:45:59 |
Dmitry Pyzhov |
tags |
lma ui |
area-ui lma ui |
|
| 2015-11-11 16:19:24 |
Vitaly Kramskikh |
tags |
area-ui lma ui |
area-ui late-discovery lma ui |
|
| 2015-12-08 10:30:11 |
OpenStack Infra |
fuel: status |
Confirmed |
In Progress |
|
| 2015-12-08 10:30:11 |
OpenStack Infra |
fuel: assignee |
Fuel UI Team (fuel-ui) |
Julia Aranovich (jkirnosova) |
|
| 2015-12-08 13:19:29 |
OpenStack Infra |
fuel: status |
In Progress |
Fix Released |
|
| 2015-12-08 13:45:57 |
Vitaly Kramskikh |
fuel: status |
Fix Released |
Fix Committed |
|
| 2016-01-29 15:26:09 |
Denis Klepikov |
fuel/7.0.x: status |
Won't Fix |
New |
|
| 2016-01-29 15:26:12 |
Denis Klepikov |
fuel/7.0.x: importance |
Medium |
High |
|
| 2016-01-29 15:26:37 |
Denis Klepikov |
tags |
area-ui late-discovery lma ui |
area-ui customer-found late-discovery lma support ui |
|
| 2016-01-29 17:18:14 |
Denis Klepikov |
fuel/7.0.x: milestone |
7.0 |
7.0-mu-3 |
|
| 2016-01-29 17:50:44 |
Ivan Ponomarev |
fuel/7.0.x: status |
New |
Confirmed |
|
| 2016-02-01 13:15:03 |
ElenaRossokhina |
tags |
area-ui customer-found late-discovery lma support ui |
area-ui customer-found late-discovery lma on-verification support ui |
|
| 2016-02-01 13:25:40 |
ElenaRossokhina |
tags |
area-ui customer-found late-discovery lma on-verification support ui |
area-ui customer-found late-discovery lma support ui |
|
| 2016-02-01 13:25:50 |
ElenaRossokhina |
fuel: status |
Fix Committed |
Fix Released |
|
| 2016-03-18 09:05:48 |
Alexey Stupnikov |
fuel/7.0.x: status |
Confirmed |
In Progress |
|
| 2016-03-18 09:05:50 |
Alexey Stupnikov |
fuel/7.0.x: assignee |
Fuel UI Team (fuel-ui) |
Alexey Stupnikov (astupnikov) |
|
| 2016-03-25 08:11:21 |
Vitaly Sedelnik |
fuel/7.0.x: status |
In Progress |
Fix Committed |
|
| 2016-03-28 13:09:14 |
TatyanaGladysheva |
tags |
area-ui customer-found late-discovery lma support ui |
area-ui customer-found late-discovery lma on-verification support ui |
|
| 2016-03-29 09:59:41 |
TatyanaGladysheva |
attachment added |
|
scr-2.png https://bugs.launchpad.net/fuel-plugins/+bug/1496328/+attachment/4615732/+files/scr-2.png |
|
| 2016-03-29 10:00:37 |
TatyanaGladysheva |
tags |
area-ui customer-found late-discovery lma on-verification support ui |
area-ui customer-found late-discovery lma support ui |
|
| 2016-03-29 10:00:51 |
TatyanaGladysheva |
fuel/7.0.x: status |
Fix Committed |
Fix Released |
|
| 2016-04-06 15:03:49 |
Alexey Stupnikov |
summary |
custom roles: "limits: max" constraint has an unpredictable behavior |
Wrong role's limits calculation |
|
