On 03/13/2015 07:47 PM, John Ferlan wrote:
>
>
> On 03/13/2015 12:04 PM, Eric Blake wrote:
>> Commit f182da20 (v1.2.6) caused a slight regression in virsh
>> reporting of a non-active block job; where it used to state
>> "Commit complete", it now states "Now in synchronized phase".
>> But the syn
On 03/13/2015 12:04 PM, Eric Blake wrote:
> Commit f182da20 (v1.2.6) caused a slight regression in virsh
> reporting of a non-active block job; where it used to state
> "Commit complete", it now states "Now in synchronized phase".
> But the synchronized phase is only possible for an active commit
Commit f182da20 (v1.2.6) caused a slight regression in virsh
reporting of a non-active block job; where it used to state
"Commit complete", it now states "Now in synchronized phase".
But the synchronized phase is only possible for an active commit.
For a reproducer, I created a chain 'a <- b <- c
