[VMware-dvs][DVS-2.1] Some VMs have incorrect mapping at vSphere.

Bug #1557980 reported by SlOPS
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel Plugins
Fix Committed
Critical
Fuel Partner Integration Team

Bug Description

Some of VMs may be mapped to incorrect DVS ports after deploy. It causes abnormal firewall operation and multiple bugs.

It seems that nova-compute restart can fix problem. The problem never observed after it.

SlOPS (vtabolin)
Changed in fuel-plugins:
importance: Undecided → Critical
milestone: none → 8.0
assignee: nobody → Fuel Partner Integration Team (fuel-partner)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-plugin-vmware-dvs (master)

Reviewed: https://review.openstack.org/291095
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-vmware-dvs/commit/?id=00a7601d53daae06f0a89e26cda2b536dfbd6aa2
Submitter: Jenkins
Branch: master

commit 00a7601d53daae06f0a89e26cda2b536dfbd6aa2
Author: Igor Gajsin <email address hidden>
Date: Thu Mar 10 13:45:02 2016 +0300

    add explicit restart nova-compute in post_deployment stage

    Closes-bug: #1557980

    Change-Id: Iec77d268b2157de6951d52c09fb5bcc2628bc827

Changed in fuel-plugins:
status: New → Fix Committed
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.