© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is just clearing the pending fields, which was delayed.
The huge pages are allocated after the worker manifest is applied, and the pending fields are cleared after the conductor receives the first memory update from the agent after unlock. In this case, the first memory update was delayed due to the followings.
The sysinv agent normally starts 5 or 6 minutes after the host is unlock/rebooted which sends inventory update at startup. By this time, if the worker manifest apply has not been completed (via checking .worker_
After that, the memory update is triggered by periodical audit. The audit runs every minute, but the memory & lldp reports are sent after 5 audit interval (agent throttle update implemented for big lab performance issues in previous release). The audit throttling results in 5 minutes delay after sending the first inventory report, which adds around 11 minutes to clear the pending fields after reboot.
In this scenario, the second lock was less than 10 minutes after the first unlock. Once the host was locked, the sysinv-conductor would not clear the pending fields.
2019-05-
2019-05-
2019-05-
2019-05-
2019-05-