On Sun, Mar 4, 2018 at 5:48 PM, Nir Soffer <[email protected]> wrote:
> On Sun, Mar 4, 2018 at 5:31 PM Yaniv Kaul <[email protected]> wrote: > >> On Sun, Mar 4, 2018 at 5:18 PM, Daniel Belenky <[email protected]> >> 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 >>> >>> <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-004_basic_sanity.py/lago-basic-suite-4-2-engine> >>> - host 0 >>> >>> <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-004_basic_sanity.py/lago-basic-suite-4-2-host-0/_var_log> >>> - host 1 >>> >>> <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-004_basic_sanity.py/lago-basic-suite-4-2-host-1/_var_log> >>> >>> 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+0000: 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 [email protected] http://lists.ovirt.org/mailman/listinfo/devel
