Bug 1255733
Summary: | Nova scheduler reports wrong available memory for a baremetal host | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | AlbertoG <agarciam> |
Component: | openstack-ironic-discoverd | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | yeylon <yeylon> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | Director | CC: | agarciam, apevec, berrange, dasmith, dhill, eglynn, jthomas, kchamart, lhh, mburns, ndipanov, pbrady, rhel-osp-director-maint, sbauza, sferdjao, sgordon, srevivo, vromanso, yeylon |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-05 12:51:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
AlbertoG
2015-08-21 12:10:52 UTC
So, I'm trying to get a few more details. Which version of Nova and Ironic are you running ? Per the bug, it says OSP8. Do you confirm ? The error above comes from the fact that it *seems* that the Ironic node already holds an instance (hence the instance=1 and the memory/disk consumed). I just wonder why a scheduler restart fixes the problem. In order to better understand, could I please have the nova-compute.log plus the nova-scheduler.log not truncated ? Ideally a sos-report would be great or if not possible, could you please also give me the nova.conf file Thanks. Hello Sylvain, I think this is a known issue and already has many BZ for this. I didn't witness this nova-scheduler issue within the case but it seems like system with more than 256GB of RAM will report their memory_mb wrongly has if there was some kind of /1024 or /1000 division for sizes bigger than X . In this case for instance, the systems are reporting 384MB of ram instead of 384000MB of RAM or so. We can easily bypass this issue by ironic node-updating the affected node with the appropriate memory size. Thank you very much, David Hill *** This bug has been marked as a duplicate of bug 1256421 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |