yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #38105
[Bug 1301279] Re: Changing node's properties in Ironic after node is deployed will count as available resources in Nova
I don't believe there's anything to do here in Ironic, correct me if I'm
wrong.
** Changed in: ironic
Status: Confirmed => Invalid
--
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/1301279
Title:
Changing node's properties in Ironic after node is deployed will count
as available resources in Nova
Status in Ironic:
Invalid
Status in OpenStack Compute (nova):
Fix Released
Bug description:
If you increase the properties of a node which was already deployed
the different will go to nova as available resources. For e.g, a node
with properties/memory_mb=512 was deployed, and n-cpu is showing:
2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 0
2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 0
2014-04-02 10:37:26.514 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0
Now if we update that that to properties/memory_mb=1024, the
difference will be shown in nova as available resources:
2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 512
2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 0
2014-04-02 10:40:48.266 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0
LOGs: http://paste.openstack.org/show/74806/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1301279/+subscriptions