yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => 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/1335744

Title:
  VMware: port group and vm are created in different exsi when using
  vlanDHCPmanage

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When using vlanDHCPmanage it is supposed to create a portgroup if the
  portgroups doesn't exist in the vCenter. I found that it is possible
  that the created portgroup and deployed vm are located in different
  exsis if there are more than 1 exsi under cluster. The deployment is
  shown as successful. Of course the IPs are not correct.

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