On 07/09/2013 08:45 PM, Noah Watkins wrote:
It appears to be resolved in master now.
Yep!
-Joao
On Tue, Jul 9, 2013 at 12:43 PM, Joao Eduardo Luis
wrote:
On 07/09/2013 04:37 PM, Noah Watkins wrote:
I'm getting the following failure when running a vstart instance with
1 of each daemon.
It appears to be resolved in master now.
On Tue, Jul 9, 2013 at 12:43 PM, Joao Eduardo Luis
wrote:
> On 07/09/2013 04:37 PM, Noah Watkins wrote:
>>
>> I'm getting the following failure when running a vstart instance with
>> 1 of each daemon.
>
>
> I can confirm this happens, as it just happened t
On 07/09/2013 04:37 PM, Noah Watkins wrote:
I'm getting the following failure when running a vstart instance with
1 of each daemon.
I can confirm this happens, as it just happened to me as well.
My guess is that this is something Sage may have fixed last night, but
will have to check.
-Jo
I'm getting the following failure when running a vstart instance with
1 of each daemon.
--
0> 2013-07-09 08:30:43.213345 7fdc289e97c0 -1 mon/OSDMonitor.cc: In
function 'virtual void OSDMonitor::update_from_paxos(bool*)' thread
7fdc289e97c0 time 2013-07-09 08:30:43.207686
mon/OSDMonitor.cc: 129: F
