Ideally this should go out at the same time as bz1245785, since this bug only occurs after that fix.
Testing bz1245785 seems to be going weill. So what's your time line to release.
*** Bug 1255827 has been marked as a duplicate of this bug. ***
I understood that there was a duplication. Could you please tell me what's going on exactly right now.
We'll have to ship a new async update for 1.2 to fix this bug.
Josh, is http://tracker.ceph.com/issues/12752 going to make v0.80.11?
(In reply to Ken Dreyer (Red Hat) from comment #8) > Josh, is http://tracker.ceph.com/issues/12752 going to make v0.80.11? Nevermind, I see Nathan already responded in the upstream ticket. It will be in v0.80.11.
Closing all RHCS 1.2 bugs, since we are not planning to do a formal RHCS 1.2.4 release. This particular issue was already fixed in RHCS 1.3, in https://bugzilla.redhat.com/show_bug.cgi?id=1255830