yahoo-eng-team team mailing list archive

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

Cleanup
=======

This bug report has the status "Incomplete" since more than 30 days
and it looks like that there are no open reviews for it. To keep
the bug list sane, I close this bug with "won't fix". This does not
mean that it is not a valid bug report, it's more to acknowledge that
no progress can be expected here anymore. You are still free to push a
new patch for this bug. If you could reproduce it on the current master
code or on a maintained stable branch, please switch it to "Confirmed".

Juno has reached its EOL, so it's "invalid" for that release.

** Changed in: juno
       Status: New => Invalid

** Changed in: nova
       Status: Incomplete => Won't Fix

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

Title:
  CPU/MEM usage not accurate. Hits quotas while resources are available

Status in Juno:
  Invalid
Status in OpenStack Compute (nova):
  Won't Fix
Status in Ubuntu:
  New

Bug description:
  I tried to set my quotas to exactly the hardware specs of my compute
  node for accurate reporting. My compute node runs on bare metal. After
  I did this I got quotas exceeded, unable to launch instance. I checked
  the hypervisor from the web interface and cli. 5 of 12 VCPUs used and
  6GB of 16GB used. When you try and change the quotas to match the
  hardware it errors. From the CLI it reports that quota cant be set to
  12 VCPUs because 17 are in use. Same with mem says 17GB are in use.
  But they arent in use clearly. So the bandaid is to set the quotas
  really high and then it ignores them and allows you to create
  instances against the actual nova usage stats. This also causes some
  failure to launch instance errors, no host is available meaning there
  arent enough resources even though there are. Im running this as a
  production environment for my domain so I have spent hundreds of hours
  chasing my tail. Hope this is helpful for debugging the issue.

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