yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1498865@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1498865

Title:
  VMware: nova-network creates a port group only on one ESXi in cluster
  in case with VlanManager

Status in OpenStack Compute (nova):
  Expired

Bug description:
  In case with VlanManager nova-compute creates a appropriate port group
  (vSwitch) only on one ESXi in cluster. Thus all instances are created
  only on one ESXi host in cluster.

  Openstack Release: Kilo on Ubuntu 14.04

  root@node-2:~# dpkg -l | grep nova
  ii  nova-api                            1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - compute API frontend
  ii  nova-cert                           1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - certificate manager
  ii  nova-common                         1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - common files
  ii  nova-compute                        1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - compute node
  ii  nova-compute-kvm                    1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - compute node (KVM)
  ii  nova-conductor                      1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - conductor service
  ii  nova-consoleauth                    1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - Console Authenticator
  ii  nova-consoleproxy                   1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - NoVNC proxy
  ii  nova-network                        1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - network manager
  ii  nova-objectstore                    1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - object store
  ii  nova-scheduler                      1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - virtual machine scheduler
  ii  python-nova                         1:2015.1.1-1~u14.04+mos19662           all          OpenStack Compute - libraries
  ii  python-novaclient                   1:2.23.0-1~u14.04+mos1245              all          client library for OpenStack Compute API

  Steps to reproduce:

  1. Deploy Fuel 7.0
  2. Create env with vcenter support
  3. Set Nova VlanManager
  4. Add a controller node
  5. Configure VMware settings (At least two ESXi hosts should be in cluster)
  6. Deploy enviroment
  7. Login to Horizon and create a bunch of instances using vcenter availability zone
  8. Verify ESXi network settings using vCenter

  Observed behavior:

  Appropriate port group (br103 in my case) was added only on one ESXi
  in cluster. All VMs were created only on one ESXi.

  Workaround:
  We can manually add appropriate port groups on other ESXi in cluster. In such case all new created VMs will be distributed across all ESXi in cluster.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1498865/+subscriptions