Comment 18 for bug 1989686

Terje, thanks for all of the helpful feedback here. Based on the command and uptime listed, as well as our internal testing, we still believe this issue to be fixed. If you see this issue after running "cloud-init clean", or if you have launched a fresh instance containing this latest version, please let us know so that we can investigate further. If we don't hear from you by end of week, we'll assume that this is fixed and can go ahead with releasing it.