pollinate can take a long time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pollinate (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
* Due to code inefficiences, pollinate takes a significant amount of time during firstboot.
* Customers expect minimal boot-times, particularly wrt. pollinate which is described as having an impact in seconds.
[Test Case]
* Boot an Amazon instance, e.g., and examine the systemd-analyze output with and without the fix.
* Without the fix, pollinate will account for 15-60s of time. With the fix, that drops to ~6s.
[Regression Potential]
* While a large number of changes to pollinate:
changelog | 35 +++++++
pollinate | 54 +++++++
pollinate.default | 2 +-
3 files changed, 67 insertions(+), 24 deletions(-)
the releases changes have been well-tested manually in yakkety and represent the next logical release for pollinate relative to what has already been SRU'd (precise upload currently is in -proposed)..
* The highest likelihood of regression stems from possible behaviour dependencies on the old code, but that seems a) unlikely to be the case and b) fixable during the -proposed testing, if encountered.
---
backport to xenial fixes in pollinate that address slow run times (see http://
To see the issue launch an AMI, and look at systemd-analyze blame. pollinate was taking anywhere from 12-50 seconds to run during first boot.
affects: | ubuntu → pollinate (Ubuntu) |
Changed in pollinate (Ubuntu): | |
assignee: | nobody → Nish Aravamudan (nacc) |
status: | New → Fix Released |
Changed in pollinate (Ubuntu Xenial): | |
assignee: | nobody → Nish Aravamudan (nacc) |
Changed in pollinate (Ubuntu): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in pollinate (Ubuntu Xenial): | |
status: | New → In Progress |
description: | updated |
Changed in pollinate (Ubuntu Trusty): | |
status: | New → In Progress |
Changed in pollinate (Ubuntu Precise): | |
status: | New → In Progress |
description: | updated |
Changed in pollinate (Ubuntu Trusty): | |
assignee: | nobody → Nish Aravamudan (nacc) |
Changed in pollinate (Ubuntu Precise): | |
assignee: | nobody → Nish Aravamudan (nacc) |
Changed in pollinate (Ubuntu): | |
importance: | Undecided → Medium |
Changed in pollinate (Ubuntu Precise): | |
importance: | Undecided → Medium |
Changed in pollinate (Ubuntu Trusty): | |
importance: | Undecided → Medium |
Changed in pollinate (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in pollinate (Ubuntu Precise): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in pollinate (Ubuntu Xenial): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Changed in pollinate (Ubuntu Trusty): | |
assignee: | Nish Aravamudan (nacc) → nobody |
Hello Patricia, or anyone else affected,
Accepted pollinate into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ pollinate/ 4.23-0ubuntu1~ 16.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!