Exchange applying order compute with cinder configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ksenia Svechnikova | ||
Mitaka |
Fix Released
|
High
|
Ksenia Svechnikova | ||
Newton |
Confirmed
|
High
|
MOS QA Team |
Bug Description
Detailed bug description:
Test Apply config for node with multiple role fail with AssertionError: https:/
Steps to reproduce: Run test 'apply_
Expected results: Test pass
Actual result: AssertionError: Expected that the option "default_
Description of the environment: 9.0 mos iso #416
Additional information: The root cause is in new order of config execution. Previously it was 'compute, cinder' and openstack-config tasks were executed in this order. But now we can see that they are executed in ID-priority way:
[root@nailgun ~]# fuel2 openstack-config list --env 1
+----+-
| id | is_active | config_type | cluster_id | node_id | node_role |
+----+-
| 4 | True | role | 1 | None | controller |
| 7 | True | role | 1 | None | cinder |
| 8 | True | role | 1 | None | compute |
+----+-
====> compute conf was executed
[root@nailgun ~]# fuel2 openstack-config list --env 1
+----+-
| id | is_active | config_type | cluster_id | node_id | node_role |
+----+-
| 4 | True | role | 1 | None | controller |
| 8 | True | role | 1 | None | compute |
| 9 | True | role | 1 | None | cinder |
+----+-
[root@nailgun ~]#
==> cinder conf
tags: | added: swarm-fail |
Fix proposed to branch: master /review. openstack. org/323375
Review: https:/