Can't add vmware cluster on controller after first deployment

Bug #1598834 reported by Ilya Bumarskov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Alexander Arzhanov
Mitaka
Confirmed
High
Alexander Arzhanov

Bug Description

Fuel 9.0/9.1

Detailed bug description:
New nova-compute instance (vCenter az) is not started on controller after redeploy env.

Steps to reproduce:
   - Create new env with vCenter and DVS plugin
   - Add following nodes:
         * Controller
         * Controller
         * Controller
   - Configure VMware vCenter Settings. Add vSphere cluster and configure Nova Compute instances on controller.
   - Deploy env
   - Add new nova-compute instance and assign new vSphere cluster on controller.
   - Redeploy env
   - Check that for each cluster runs nova-compute.

Observed behavior:
New nova-compute instance was not deployed on controllers.

Related-bugs:
https://bugs.launchpad.net/fuel/+bug/1593277

Changed in fuel:
importance: Undecided → Medium
assignee: nobody → Ilya Bumarskov (ibumarskov)
assignee: Ilya Bumarskov (ibumarskov) → Alexander Arzhanov (aarzhanov)
milestone: none → 9.0-updates
tags: added: area-pce-vcenter
Changed in fuel:
status: New → Confirmed
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Bug prevents scale actions for vCenter clusters in deployments with controller nodes only and should be raised up to high priority.

tags: added: release-notes
Revision history for this message
Olena Logvinova (ologvinova) wrote :
tags: added: release-notes-done
removed: release-notes
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

vCenter was removed from MOS 10

no longer affects: fuel/newton
Changed in fuel:
milestone: 10.0 → 9.x-updates
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.