Fuel does not allow to deploy environments without controllers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Roman Prykhodchenko | ||
8.0.x |
Fix Released
|
High
|
Roman Prykhodchenko | ||
Mitaka |
Fix Released
|
High
|
Roman Prykhodchenko |
Bug Description
Fuel does not allow to deploy environment without controllers and gives error like this:
Error: Not enough controllers, ha_compact mode requires at least 1 controller(s)
This blocks any possibility to deploy deeply customized configurations using Fuel Plugins. For instance: I may want to introduce brand new role that will replace our standard controller role and use this role in my deployment. But Nailgun will not allow this.
Steps to reproduce:
1) Create env without controllers (for example with 1 compute)
2) Deploy changes
Expected result:
Some kind of warning about possible problems and started deployment process
Actual result:
Deployment is not started, "Not enough controllers, ha_compact mode requires at least 1 controller(s)" is shown
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "461"
build_id: "461"
fuel-nailgun_sha: "be3b6aa15ead51
python-
fuel-agent_sha: "9d550d821ef2d2
fuel-
astute_sha: "b81577a5b7857c
fuel-library_sha: "60edcca1b81fe5
fuel-ostf_sha: "f66b1208bb9214
fuel-mirror_sha: "b62f3cce5321fd
fuelmenu_sha: "6c1888a48e2c32
shotgun_sha: "63645dea384a37
network-
fuel-upgrade_sha: "616a7490ec7199
fuelmain_sha: "1777390e250c68
description: | updated |
tags: | added: feature |
Changed in fuel: | |
assignee: | Krzysztof Szukiełojć (kszukielojc) → nobody |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Roman Prykhodchenko (romcheg) |
tags: | added: on-verification |
I would propose feature to enable fuel-plugin declare controller role that would make our checks happy.
That's means it is a feature that requires blueprint.
Controller node is *crucial* role and removing checks for it seems like a drastic solution.