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: Low => Undecided

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

** Changed in: nova
     Assignee: Ankit Agrawal (ankitagrawal) => (unassigned)

-- 
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/1334974

Title:
  create vm fail by  volume when use diskfilter

Status in OpenStack Compute (nova):
  Expired

Bug description:
  I configed the  diskfilter in nova.conf,i created vm by a bootable volume and use the back-end storage , the vm flavor is following:
  cpu 1
  mem 2G
  root_gb 2T

  In fact , the local disk in computer node  is 80G, so i create vm that remind no available host;
  I think , i create vm  by volume and use  back-end storage,  the diskfilter should not be  chose the host by local disk size.
  In addition,the compute node report the resource info that shoud check the instance status, if it createdby a  volume ,the local_gb_used shoud not add the flavor's root_db size.

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