vSphere cluster can't be added when new compute-vmware node was added to environment
Bug #1490305 reported by
Ilya Bumarskov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Partner Core |
Bug Description
Fuel ISO #253
Description:
Can't add a new vSphere cluster if new compute-vmware role was added to env.
Steps to reproduce:
1. Deploy env with controller and vCenter support
2. Add a compute-vmware node
3. Navigate to VMWare tab and try to add a new nova compute instance
Observed behaviour:
Nova Computes section can't be changed.
affects: | mos → fuel |
tags: | added: vcenter |
Changed in fuel: | |
assignee: | nobody → Fuel Partner Integration Team (fuel-partner) |
milestone: | none → 7.0 |
importance: | Undecided → Critical |
description: | updated |
Changed in fuel: | |
assignee: | Fuel Partner Integration Team (fuel-partner) → Igor Zinovik (izinovik) |
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-partners |
To post a comment you must log in.
Described functionality: add 'compute-vmware' node to deployed OpenStack environment, add vSphere cluster on the VMware
tab and assign control over this cluster to nova-compute service that will be running on newly added 'compute-vmware' node
was not implemented due to resource shortage.
This limitation must be reflected in documentation.
Marking as 'Wont Fix' for Fuel 7.0 and lower priority to High.
Marking as 'Confirmed' for Fuel 8.0 with High priority.