I'm confused. As I understand it, a simple solution exists upstream, it's been understood for over a month, and it's easy to apply. I also understand that this bug affects everybody who uses Ubuntu 14.04 on AWS, and it prevents anybody from using Ubuntu 14.04 in a production environment on AWS. A sketchy workaround -- replacing the kernel -- might suffice for test or development environments. (I'm rehashing what I've learned from https://groups.google.com/forum/#!topic/logstash-users/sFNrqRbI6EM and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308796 and the LKML....)
So why hasn't Ubuntu updated its AWS cloud images? Why didn't Ubuntu fix its kernel before re-releasing its AWS cloud images on 2014-06-07, at http://cloud-images.ubuntu.com/releases/14.04/release/? Was anybody aware, when releasing those images, that they are unreliable? If so, was there a release note that I missed? I don't understand the logistical issues that are keeping this bug unresolved. What would it take to escalate this bug to Critical? Either I'm affected by this kernel bug far more than everybody else is, I have unrealistic expectations about Ubuntu 14.04 LTS, or Ubuntu is being too opaque. What's happening? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
