[vcenter][ui] vmware target compute node was not correctly set
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Medium
|
Andriy Popovych | ||
Bug Description
Trying to deploy MOS+vCenter with compute node on controllers. But phantom(removed) 'node-5' was set as target compute node instead of "controllers".
Release: MOS 7.0
Steps to reproduce:
1) Create env with vCenter as hypervisor
2) Add any discovered node with role "compute-vmware"
3) On "vmware" tab set this compute node as "target node" and press "save"
4) On "vmware" tab change target node back to "controllers"
Actual result:
fuel vmware-settings --download --env ENV_ID
-------
current:
id: node-5
label: node-5
-------
Expected result:
target node should be "controllers"
Workaround:
1) fuel vmware-settings --download --env ENV_ID
2) Edit "target node" in resulting yaml
3) fuel vmware-settings --upload --env ENV_ID
For reference: https:/
| tags: | added: area-ui |
| summary: |
- [vcenter][ui] Target compute node is not correctly set + [vcenter][ui] vmware target compute node was not correctly set |
| Krzysztof Szukiełojć (kszukielojc) wrote | #1 |
| Changed in fuel: | |
| milestone: | none → 7.0-updates |
| assignee: | nobody → Fuel UI Team (fuel-ui) |
| assignee: | Fuel UI Team (fuel-ui) → Fuel Python Team (fuel-python) |
| tags: |
added: area-python removed: area-pce-vcenter area-ui |
| Changed in fuel: | |
| importance: | Undecided → Medium |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Fuel Partner Integration Team (fuel-partner) |
| tags: |
added: area-partners removed: area-python |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| assignee: | Fuel Partner Integration Team (fuel-partner) → Andriy Popovych (popovych-andrey) |
| tags: | added: non-release |
| Alexey Stupnikov (astupnikov) wrote | #2 |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
Seems that problem is in backend not in UI.