HA-mode for vCenter doesn't work properly

Bug #1312653 reported by Evgeniya Shumakher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Julia Aranovich

Bug Description

In 5.0 vCenter supports only non-HA mode.
For HA-mode nova-compute always run on the primary controller. If the controller goes down, network doesn't work. It's not an HA, but just a hack to ensure that HA-mode is not broken.
Does it make sense to disable it?

Tags: vcenter
Revision history for this message
Andrew Woodward (xarses) wrote :

This logic is by design. It likely should just be documented

Revision history for this message
Mike Scherbakov (mihgen) wrote :

In wizard, you first of all choose deployment mode, so if you chose HA - then we need to disable vCenter, as otherwise it won't be HA anyway. So let's disable it there for HA, and show a warning with text something like "Choose multi-node to enable vCenter."

Changed in fuel:
assignee: nobody → Fuel UI Team (fuel-ui)
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
assignee: Fuel UI Team (fuel-ui) → Julia Aranovich (jkirnosova)
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to fuel-web (master)

Fix proposed to branch: master
Review: https://review.openstack.org/90741

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/90741
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=fb676be97794d4b63b8d179e2a8518ad70448f48
Submitter: Jenkins
Branch: master

commit fb676be97794d4b63b8d179e2a8518ad70448f48
Author: Julia Aranovich <email address hidden>
Date: Mon Apr 28 17:59:57 2014 +0400

    Wizard: display warning for vCenter option (HA environment)

    Closes-Bug:#1312653

    Change-Id: I8c7eda80d265b9b7b9648645ea7ea7ac2b3c1f4e

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Meg McRoberts (dreidellhasa) wrote :

Listed as "Known Issue" in 5.0 and 5.0.1 Release Notes.

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.