[libvirt] Syslog "nested job is dangerous" message

Ján Tomko jtomko at redhat.com
Thu Jul 17 07:54:40 UTC 2014


On 07/17/2014 08:51 AM, Jiri Denemark wrote:
> On Thu, Jul 17, 2014 at 13:29:52 +1000, Sam Bobroff wrote:
>> On 17/07/14 12:50, Eric Blake wrote:
>>> On 07/16/2014 07:52 PM, Sam Bobroff wrote:
>>>> Hello everyone,
>>>
>>> [Can you configure your mailer to wrap long lines?]
>>
>> [No problem, done.]
>>
>>>> After performing a migration, the syslog often contains several
>>>> messages like this:
>>>>
>>>> "This thread seems to be the async job owner; entering monitor
>>>> without asking for a nested job is dangerous"
>>>
>>> The sign of a bug that we need to fix.  What version of libvirt are
>>> you using?  We may have already fixed it.
>>
>> I've been testing on 1.2.6, but I will re-test on the latest code from git.
> 
> Hmm, it what were you doing when the message appeared in the log? I
> fixed wrong usage of our job tracking APIs long time ago
> (e4e28220b572cf4c71d07740c24150411f0704a6 in 1.0.3) so I guess there
> must be another place we don't do it correctly.
> 

That commit was essentially reverted by my commit 9846402 when fixing
migration crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1018267

I think the message was harmless during migration as we don't allow other jobs
(except destroy).

Jan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20140717/b46c2fbb/attachment-0001.sig>


More information about the libvir-list mailing list