Comment 24 for bug 996840

I hesitate to ask, because I know everyone is busy working on something...

But, here goes: does anyone have any updates to current status for this bug? I'm using mostly Ubuntu cloud platforms, but will add a significant number of RHEL compute nodes in the near future? Everything is behind a firewall with no Internet access, so I typically import (entire) mirror repositories, etc. I have several security-related agreements across enterprises that I like to adhere to with limited exceptions, e.g., preference for LTS releases, reluctance to use backports, etc.

I have multiple Essex private clouds up and running, lots of instances per cloud, etc., so I have to decide between pushing (across all platforms) a source-code workaround versus using a backports or cloud-archive solution. I haven't (yet) done off-site testing to verify whether or not the backports or the cloud archive address this bug because I have been watching this space. I'm wondering what other folks are doing on Essex platforms? A wholesale OpenStack upgrade will be a massive number of person-hours of work...

Thanks.