After a little fighting with what directories to remove and creating the
AMI I think I was able to verify on all three releases. Below are the
steps that I completed:

* Launched all three LTS AMI
* For Xenial captured `systemd-analyze` and `systemd-analyze blame`
* Installed the proposed version of pollinate
* sudo rm -Rf /var/lib/cloud/instance/* /var/cache/pollinate/* 
/var/log/cloud-init*
* Shut the instance down and create a new AMI
* Launch the new AMI
* On Xenial, verify the systemd-analyze output was improved
* Verify /var/cache/polinate/seeded existed and /var/log/cloud-init* logs 
existed
* Verified syslog has pollinate entries and were sucessful

Below is the Xenial systemd output:

Xenial ami-204e0040
Startup finished in 9.240s (kernel) + 51.217s (userspace) = 1min 457ms
29.245s pollinate.service

Xenial ami-204e0040 + New Pollinate
Startup finished in 5.051s (kernel) + 7.946s (userspace) = 12.998s
3.755s pollinate.service

** Tags removed: verification-needed
** Tags added: verification-done-precise verification-done-trusty 
verification-done-xenial

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621280

Title:
  pollinate can take a long time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1621280/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to