Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Nir Soffer 
On Sun, Mar 4, 2018 at 6:43 PM Yaniv Kaul  wrote:

> On Sun, Mar 4, 2018 at 5:48 PM, Nir Soffer  wrote:
>
>> On Sun, Mar 4, 2018 at 5:31 PM Yaniv Kaul  wrote:
>>
>>> On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky 
>>> wrote:
>>>
 Hi,

 The following test failed OST: 004_basic_sanity.disk_operations.

 Link to suspected patch: https://gerrit.ovirt.org/c/88404/
 Link to the failed job:
 http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/
 Link to all test logs:

- engine

 
- host 0

 
- host 1

 

 Error snippet from engine:

 2018-03-04 09:50:14,823-05 ERROR 
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
 (ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is down 
 with error. Exit message: Lost connection with qemu process.


 Error snippet from host:

 Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04 
 14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest 
 agent is not responding: QEMU guest agent is not connected


>>> That's not surprising - there's no guest agent there.
>>>
>>
>> There are 2 issues here:
>> - we are testing without guest agent when this is the recommended
>> configuration
>>   (snapshots may not be consistent without guest agent)
>>
>
> We are still using Cirros. I need to get a CentOS with cloud-init uploaded
> (WIP...)
>
>
>> - vdsm should not report errors about guest agent since it does not know
>> if
>> guest agent is installed or not. This message should be an INFO message
>> like
>> "could not stop the vm using guest agent, falling back to ..."
>>
>> Generally we should not see ERROR or WARN message in OST. Any repeating
>> error or warning should be reported as a bug.
>>
>
> There are several on storage... Should we file BZs on them?
>

I think we have only warnings now, but they should be fixed, so please file
a bug.


> Y.
>
>
>>
>> Nir
>>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Yaniv Kaul 
On Sun, Mar 4, 2018 at 5:48 PM, Nir Soffer  wrote:

> On Sun, Mar 4, 2018 at 5:31 PM Yaniv Kaul  wrote:
>
>> On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky 
>> wrote:
>>
>>> Hi,
>>>
>>> The following test failed OST: 004_basic_sanity.disk_operations.
>>>
>>> Link to suspected patch: https://gerrit.ovirt.org/c/88404/
>>> Link to the failed job: http://jenkins.ovirt.org/
>>> job/ovirt-4.2_change-queue-tester/1019/
>>> Link to all test logs:
>>>
>>>- engine
>>>
>>> 
>>>- host 0
>>>
>>> 
>>>- host 1
>>>
>>> 
>>>
>>> Error snippet from engine:
>>>
>>> 2018-03-04 09:50:14,823-05 ERROR 
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>>> (ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is down 
>>> with error. Exit message: Lost connection with qemu process.
>>>
>>>
>>> Error snippet from host:
>>>
>>> Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04 
>>> 14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest 
>>> agent is not responding: QEMU guest agent is not connected
>>>
>>>
>> That's not surprising - there's no guest agent there.
>>
>
> There are 2 issues here:
> - we are testing without guest agent when this is the recommended
> configuration
>   (snapshots may not be consistent without guest agent)
>

We are still using Cirros. I need to get a CentOS with cloud-init uploaded
(WIP...)


> - vdsm should not report errors about guest agent since it does not know if
> guest agent is installed or not. This message should be an INFO message
> like
> "could not stop the vm using guest agent, falling back to ..."
>
> Generally we should not see ERROR or WARN message in OST. Any repeating
> error or warning should be reported as a bug.
>

There are several on storage... Should we file BZs on them?
Y.


>
> Nir
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Eyal Edri 
I've prepared a revert patch [1] in the meantime, but its strange that it
passed check-patch, can you verify which SDK version was used and which one
you need?

[1] https://gerrit.ovirt.org/#/c/88441/

On Sun, Mar 4, 2018 at 6:01 PM, Benny Zlotnik  wrote:

> https://gerrit.ovirt.org/#/c/84338/ this patch was merged today and it
> seems to be causing the problem since it uses an SDK feature which is
> currently only available in the 4.3 SDK versions
> It looks like it should be available in the SDK when it's built against
> the 4.2.29 ovirt-engine-api-model
>
> On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky 
> wrote:
>
>> Hi,
>>
>> The following test failed OST: 004_basic_sanity.disk_operations.
>>
>> Link to suspected patch: https://gerrit.ovirt.org/c/88404/
>> Link to the failed job: http://jenkins.ovirt.org/
>> job/ovirt-4.2_change-queue-tester/1019/
>> Link to all test logs:
>>
>>- engine
>>
>> 
>>- host 0
>>
>> 
>>- host 1
>>
>> 
>>
>> Error snippet from engine:
>>
>> 2018-03-04 09:50:14,823-05 ERROR 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>> (ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is down 
>> with error. Exit message: Lost connection with qemu process.
>>
>>
>> Error snippet from host:
>>
>> Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04 
>> 14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest agent 
>> is not responding: QEMU guest agent is not connected
>>
>>
>> Thanks,
>>
>> --
>>
>> DANIEL BELENKY
>>
>> RHV DEVOPS
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Benny Zlotnik 
https://gerrit.ovirt.org/#/c/84338/ this patch was merged today and it
seems to be causing the problem since it uses an SDK feature which is
currently only available in the 4.3 SDK versions
It looks like it should be available in the SDK when it's built against the
4.2.29 ovirt-engine-api-model

On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky  wrote:

> Hi,
>
> The following test failed OST: 004_basic_sanity.disk_operations.
>
> Link to suspected patch: https://gerrit.ovirt.org/c/88404/
> Link to the failed job: http://jenkins.ovirt.org/
> job/ovirt-4.2_change-queue-tester/1019/
> Link to all test logs:
>
>- engine
>
> 
>- host 0
>
> 
>- host 1
>
> 
>
> Error snippet from engine:
>
> 2018-03-04 09:50:14,823-05 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is down 
> with error. Exit message: Lost connection with qemu process.
>
>
> Error snippet from host:
>
> Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04 
> 14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest agent 
> is not responding: QEMU guest agent is not connected
>
>
> Thanks,
>
> --
>
> DANIEL BELENKY
>
> RHV DEVOPS
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Nir Soffer 
On Sun, Mar 4, 2018 at 5:31 PM Yaniv Kaul  wrote:

> On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky 
> wrote:
>
>> Hi,
>>
>> The following test failed OST: 004_basic_sanity.disk_operations.
>>
>> Link to suspected patch: https://gerrit.ovirt.org/c/88404/
>> Link to the failed job:
>> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/
>> Link to all test logs:
>>
>>- engine
>>
>> 
>>- host 0
>>
>> 
>>- host 1
>>
>> 
>>
>> Error snippet from engine:
>>
>> 2018-03-04 09:50:14,823-05 ERROR 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>> (ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is down 
>> with error. Exit message: Lost connection with qemu process.
>>
>>
>> Error snippet from host:
>>
>> Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04 
>> 14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest agent 
>> is not responding: QEMU guest agent is not connected
>>
>>
> That's not surprising - there's no guest agent there.
>

There are 2 issues here:
- we are testing without guest agent when this is the recommended
configuration
  (snapshots may not be consistent without guest agent)
- vdsm should not report errors about guest agent since it does not know if
guest agent is installed or not. This message should be an INFO message
like
"could not stop the vm using guest agent, falling back to ..."

Generally we should not see ERROR or WARN message in OST. Any repeating
error or warning should be reported as a bug.

Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 04-03-2018 ] [ 004_basic_sanity.disk_operations ]

2018-03-04 Thread Daniel Belenky 
Hi,

The following test failed OST: 004_basic_sanity.disk_operations.

Link to suspected patch: https://gerrit.ovirt.org/c/88404/
Link to the failed job:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/
Link to all test logs:

   - engine
   

   - host 0
   

   - host 1
   


Error snippet from engine:

2018-03-04 09:50:14,823-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJoinPool-1-worker-12) [] EVENT_ID: VM_DOWN_ERROR(119), VM vm2 is
down with error. Exit message: Lost connection with qemu process.


Error snippet from host:

Mar  4 09:56:27 lago-basic-suite-4-2-host-1 libvirtd: 2018-03-04
14:56:27.831+: 1189: error : qemuDomainAgentAvailable:6010 : Guest
agent is not responding: QEMU guest agent is not connected


Thanks,

-- 

DANIEL BELENKY

RHV DEVOPS
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel