On 9 Apr 2017, at 09:42, Barak Korren <bkorren(a)redhat.com>
wrote:
On 9 April 2017 at 10:39, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> 1. The error:
> 2017-04-08 14:12:11,376-04 ERROR
> [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able
> to update response for "fc0cef3f-d8fa-4074-b315-e36cc2f63fa1"
>
> Is still seen, not sure why.
>
> 2. MOM is not available (unrelated, but still a bug)
>
> 3. New error I have not seen in the past on host1
>
(
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6257/art...
> ) :
>
> 2017-04-08 14:12:22,208-0400 WARN (jsonrpc/6) [storage.LVM] lvm pvs failed:
> 5 [] [' Failed to find physical volume
> "/dev/mapper/360014050eacbb3c8b21428fb6683f074".'] (lvm:325)
>
> 4. New warning:
> 2017-04-08 14:13:17,327-0400 WARN (check/loop) [storage.asyncutils] Call
> <bound method DirectioChecker._check of <DirectioChecker
> /dev/0eb0f05c-0507-4f02-ba13-b8d865538d7a/metadata running
> next_check=4295183.36 at 0x2fb9190>> delayed by 1.43 seconds
> (asyncutils:138)
>
>
> Do we know when it began?
Yes. I linked to the patch that seems to have started this.
This should be easy to revert
Working on it
Then we’ll see what exactly is the culprit
--
Barak Korren
bkorren(a)redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel