yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68128
[Bug 1697820] Re: Failure to create ResourceProvider resets status and numatopology in table compute_nodes
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => 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/1697820
Title:
Failure to create ResourceProvider resets status and numatopology in
table compute_nodes
Status in OpenStack Compute (nova):
Expired
Bug description:
RT call update_available_resource to update resource to db periodic.
each time,update_available_resource first call _init_compute_node to init resource and update them(stats and numalogy is empty and init value) to db, at end of update_available_resource, the stats and numalogy is filled with right value,then _update() function called, the resource finally update to db.
But, in _update(), the resource update to db when the local resource
is changed(by self._resource_change(compute_node)), this cause the
stats and numalogy in compute_nodes is always the init or empty value.
You can see the empty or init value of stats and numalogy in
compute_nodes table when resource of nova-compute not change for a
while.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1697820/+subscriptions
References