FuelUI unpredictable behavior adding Operating system + multi role

Bug #1415395 reported by okosse
This bug report is a duplicate of:  Bug #1411679: Incorrect role editing. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
okosse

Bug Description

In FuelUI adding the role of the Operating system and the creation on its basis multirole leads to unpredictable results: roles are not added or added otherwise.
Steps to reproduce: create an environment. The type of hypervisor, network, etc. is not the value. Determine for one node the role of the Operating system and assign other nodes any role. Now, if you combine multirole, will fail.

---------------------fuel-version---------------------------------
api: '1.0'
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413
auth_required: true
build_id: 2015-01-27_22-55-01
build_number: '82'
feature_groups:
- mirantis
fuellib_sha: abcccb60c1e6bde225ede10992fa123d3e092015
fuelmain_sha: ''
nailgun_sha: 7a3d06074c18f90b46000468d49fe8624cd2c519
ostf_sha: c9100263140008abfcc2704732e98fbdfd644068
production: docker
python-fuelclient_sha: 1f3ba542dd93cf79fa5ec92880fc1fbde4c97e00
release: '6.1'
release_versions:
  2014.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413
      build_id: 2015-01-27_22-55-01
      build_number: '82'
      feature_groups:
      - mirantis
      fuellib_sha: abcccb60c1e6bde225ede10992fa123d3e092015
      fuelmain_sha: ''
      nailgun_sha: 7a3d06074c18f90b46000468d49fe8624cd2c519
      ostf_sha: c9100263140008abfcc2704732e98fbdfd644068
      production: docker
      python-fuelclient_sha: 1f3ba542dd93cf79fa5ec92880fc1fbde4c97e00
      release: '6.1'

Tags: ui
Revision history for this message
Julia Aranovich (jkirnosova) wrote :

Please provide any screenshot or additional specific steps to reproduce. Can't reproduce the issue on master (fake-ui).

Changed in fuel:
status: New → Incomplete
Changed in fuel:
assignee: nobody → Fuel UI Team (fuel-ui)
Changed in fuel:
milestone: none → 6.1
importance: Undecided → Medium
assignee: Fuel UI Team (fuel-ui) → okosse (okosse)
Revision history for this message
Tatyana Dubyk (tdubyk) wrote :

I've reproduced this bug again.

[root@nailgun ~]# fuel --fuel-version
api: '1.0'
astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413
auth_required: true
build_id: 2015-02-01_22-55-01
build_number: '92'
feature_groups:
- mirantis
fuellib_sha: c5e4a0410ba66f9e9911f62b3b71c0b9c29aed6e
fuelmain_sha: ''
nailgun_sha: c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b
ostf_sha: c9100263140008abfcc2704732e98fbdfd644068
production: docker
python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358
release: '6.1'
release_versions:
  2014.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: ed5270bf9c6c1234797e00bd7d4dd3213253a413
      build_id: 2015-02-01_22-55-01
      build_number: '92'
      feature_groups:
      - mirantis
      fuellib_sha: c5e4a0410ba66f9e9911f62b3b71c0b9c29aed6e
      fuelmain_sha: ''
      nailgun_sha: c0932eb5c2aa7fd1e13a999cb1b4bf5aff101c3b
      ostf_sha: c9100263140008abfcc2704732e98fbdfd644068
      production: docker
      python-fuelclient_sha: 2ea7b3e91c1d2ff85110bf5abb161a6f4e537358
      release: '6.1'

Steps to reproduce:
1. deploy lab using iso : 6.1 build 92
2. create env with parameters:
-OS: any (as example I uses Ubuntu)
-hypervisor: vcenter
-settings for vcenter : any
-networking setup: default
-storage backends: default
-additional services: default

3. click on create nodes button and add:
 - 1 node with role : cinder
 - 1 node with role: operating system
4. then select node with role 'Cinder' and add to this node role : 'OS'
    and click 'Apply changes button'
 expected result:
                 1 node with role 'Cinder-Based OS' and 1 node with role Based OS
 actual result:
                 nothing is changed
                 instead role 'Cinder-Based OS' we still have :
                 - 1 node with role : cinder
                 - 1 node with role: operating system
5. let's try another scenario:
   so we still have:
 - 1 node with role : cinder
 - 1 node with role: operating system
   let's try to apply one more role to node with 'operating system' role
6. so select node with role 'operating system' and add to this node role : 'contoller'
    and click 'Apply changes button'.

 expected result: 1 node with role 'Controller-Based OS' and 1 node with role Cinder
 actual result: we got 1 node with role 'Cinder-Based OS' and 'Based OS'

--------------------
Conclusion: mechanism of assigning new roles to the existing nodes which already have roles, works incorrectly.

Changed in fuel:
status: Incomplete → Confirmed
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.