[ovirt-devel] [Ovirt] [CQ weekly status] [16-11-2018]
Hi All, I want to just give a quick and simple status on CQ so that everyone is informed on the general state of our tests when they come in on beginning of the week. *Ovirt-Master*- *GREEN* *Ovirt-4.2* - *GREEN* Happy Week! Dafna ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BDIFZPEADVRXL5O5JE7CSNGS7BIBC5ZW/
[ovirt-devel] Re: Getting info about qemu guest agent into the engine
> On 16 Nov 2018, at 13:21, Tomasz Baranski wrote: > > On 18/11/16 11:39, Michal Skrivanek wrote: >> >> >>> On 16 Nov 2018, at 11:22, Tomasz Barański wrote: >>> >>> Hello, wise people! >>> >>> As a part of BZ1615830[1] I want to add information about qemu guest agent >>> to engine's DB. I have some trouble figuring out some details. >>> >>> 1. VDSM seems to be using QGA, but it does not report any information about >>> it. Am I right? >> >> what do you mean to report any information? There are guest agent reported >> fields which are either there or not >> One such field is appsList which returns the agent itself (well, it’s fake >> for qemu-ga, but the agent string is always put there) > > Oh, appsList, I didn't look into stats. > Thanks, I guess that's what I was looking for. > >> >>> I only found a mention about it in `xml` field in JSON returned by >>> `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as >>> documented in libvirt. >> >> virtio channels are always there for both agents >> >>> >>> 2. How does the engine puts data into `vm_dynamic` table? I can't find any >>> usage for `InsertVmDynamic` procedure. >> >> app_list > > ?? > How is app_list used to fill in fields like `vnc_port` or `cpu_name`? oh sorry, I though you still talk about the guest agent info only VmDynamic::updateRuntimeData() > >> >>> >>> 3. Also, it's not clear to me how (whether?) the engine consumes output of >>> VM.getInfo/Host.getVMFullList. >> >> it does not in 4.2+ clusters, see FullListAdapter::getVmFullList() >> >> HTH, >> michal >> >>> Any pointers to relevant code appreciated. >>> >>> >>> Tomo >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830 >>> ___ >>> Devel mailing list -- devel@ovirt.org >>> To unsubscribe send an email to devel-le...@ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DASVREOUEKMRWGQ4IBGHFSBTF2XMBF3C/ >> ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/LSX5JCRZ6FR7EXABX32XWWSYOY25XWX3/
[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 15-11-2018 ] [ check_snapshot_with_memory ]
Other projects are passing so it cannot be ost
we have ovirt-engine 4.2 that passed though:
https://gerrit.ovirt.org/#/c/95447/
logging a ticket to look into these failures.
On Fri, Nov 16, 2018 at 1:30 PM Dafna Ron wrote:
> I am seeing a second project to fail on this:
>
> https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue-tester/3495/
>
> I am not seeing any changes in OST merged in the last 2 days that could
> have caused this and I am also not seeing any infrastructure commonality
> (not running on same hosts).
>
> However, something has changed to cause the iscsi domain to be filled and
> fail on run vm.
>
> Milan, can you please double check that this change is not causing any
> leftovers in the iscsi domain?
> https://gerrit.ovirt.org/#/c/95333/
>
> Thanks,
> Dafna
>
>
>
> On Fri, Nov 16, 2018 at 11:32 AM Greg Sheremeta
> wrote:
>
>> It's definitely not that patch - the patch is UI / GWT only and isn't
>> tested outside of the selenium tests in 008. Also, this is a backport and
>> we didn't see any issues on master.
>>
>> Greg
>>
>> On Fri, Nov 16, 2018, 6:24 AM Dafna Ron >
>>> Hi,
>>> we have a failure on basic suite for test check_snapshot_with. _memory.
>>>
>>> I am actually not seeing any reason the patch would cause that specific
>>> issue but its consistently failing on this change.
>>> I am seeing a vm memory saved to the iscsi domain but aside from that
>>> nothing is failing before tto cause a cleanup issue or create low space on
>>> the storage).
>>> can some one please take a look to see if anything in the patch is
>>> causing this?
>>>
>>>
>>> Link and headline of suspected patches:
>>>
>>> https://gerrit.ovirt.org/#/c/95436/1 -
>>> webadmin: network operation in progress - sync host interfaces
>>>
>>> Link to Job:
>>> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/
>>>
>>> Link to all logs:
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-4.2/post-004_basic_sanity.py/
>>>
>>> (Relevant) error snippet from the log:
>>>
>>>
>>>
>>> 2018-11-15 08:19:33,409-05 DEBUG
>>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method:
>>> runVdsCommand, params: [IsVmDuringInitiating
>>> ,
>>> IsVmDuringInitiatingVDSCommandParameters:{vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
>>> timeElapsed: 1ms
>>> 2018-11-15 08:19:33,430-05 ERROR
>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] EVENT_ID:
>>> USER_FAILED_RUN_VM(54), Failed to run VM
>>> vm0 due to a failed validation: [Cannot run VM. Low disk space on
>>> Storage Domain iscsi.] (User: admin@internal-authz).
>>> 2018-11-15 08:19:33,430-05 WARN
>>> [org.ovirt.engine.core.bll.RunVmCommand] (default task-5)
>>> [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Validation of action 'RunVm' failed
>>> for user admin@internal-authz. Reasons: VAR__
>>> ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN,$storageName
>>> iscsi
>>> 2018-11-15 08:19:33,431-05 INFO
>>> [org.ovirt.engine.core.bll.RunVmCommand] (default task-5)
>>> [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Lock freed to object
>>> 'EngineLock:{exclusiveLocks='[9144eb88-8f0a-4e77-9d70-3b761e
>>> 48ecb4=VM]', sharedLocks=''}'
>>> 2018-11-15 08:19:33,438-05 DEBUG
>>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runAction,
>>> params: [RunVm, RunVmParams:{comm
>>> andId='69628467-56d3-4d93-aed1-a2807b7dbc45', user='null',
>>> commandType='Unknown', vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
>>> timeElapsed: 115ms
>>> 2018-11-15 08:19:33,441-05 ERROR
>>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>>> task-5) [] Operation Failed: [Cannot run VM. Low disk space on Storage
>>> Domain iscsi.]
>>> 2018-11-15 08:19:34,044-05 DEBUG
>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] START,
>>> GetAllVmStatsVDSCommand(HostName = lago-basic-su
>>> ite-4-2-host-0,
>>> VdsIdVDSCommandParametersBase:{hostId='063dfef9-bc9d-44c3-8ba3-8142e3eb129c'}),
>>> log id: 65651e2b
>>> 2018-11-15 08:19:34,045-05 DEBUG
>>> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] SEND
>>> destination:jms.topic.vdsm_requests
>>> reply-to:jms.topic.vdsm_responses
>>> content-length:103
>>>
>>>
>>>
>>>
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/ar
[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 15-11-2018 ] [ check_snapshot_with_memory ]
I am seeing a second project to fail on this:
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-queue-tester/3495/
I am not seeing any changes in OST merged in the last 2 days that could
have caused this and I am also not seeing any infrastructure commonality
(not running on same hosts).
However, something has changed to cause the iscsi domain to be filled and
fail on run vm.
Milan, can you please double check that this change is not causing any
leftovers in the iscsi domain?
https://gerrit.ovirt.org/#/c/95333/
Thanks,
Dafna
On Fri, Nov 16, 2018 at 11:32 AM Greg Sheremeta wrote:
> It's definitely not that patch - the patch is UI / GWT only and isn't
> tested outside of the selenium tests in 008. Also, this is a backport and
> we didn't see any issues on master.
>
> Greg
>
> On Fri, Nov 16, 2018, 6:24 AM Dafna Ron
>> Hi,
>> we have a failure on basic suite for test check_snapshot_with. _memory.
>>
>> I am actually not seeing any reason the patch would cause that specific
>> issue but its consistently failing on this change.
>> I am seeing a vm memory saved to the iscsi domain but aside from that
>> nothing is failing before tto cause a cleanup issue or create low space on
>> the storage).
>> can some one please take a look to see if anything in the patch is
>> causing this?
>>
>>
>> Link and headline of suspected patches:
>>
>> https://gerrit.ovirt.org/#/c/95436/1 -
>> webadmin: network operation in progress - sync host interfaces
>>
>> Link to Job:
>> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/
>>
>> Link to all logs:
>>
>>
>> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-4.2/post-004_basic_sanity.py/
>>
>> (Relevant) error snippet from the log:
>>
>>
>>
>> 2018-11-15 08:19:33,409-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method:
>> runVdsCommand, params: [IsVmDuringInitiating
>> ,
>> IsVmDuringInitiatingVDSCommandParameters:{vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
>> timeElapsed: 1ms
>> 2018-11-15 08:19:33,430-05 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] EVENT_ID:
>> USER_FAILED_RUN_VM(54), Failed to run VM
>> vm0 due to a failed validation: [Cannot run VM. Low disk space on Storage
>> Domain iscsi.] (User: admin@internal-authz).
>> 2018-11-15 08:19:33,430-05 WARN [org.ovirt.engine.core.bll.RunVmCommand]
>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Validation of
>> action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__
>> ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN,$storageName
>> iscsi
>> 2018-11-15 08:19:33,431-05 INFO [org.ovirt.engine.core.bll.RunVmCommand]
>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Lock freed to
>> object 'EngineLock:{exclusiveLocks='[9144eb88-8f0a-4e77-9d70-3b761e
>> 48ecb4=VM]', sharedLocks=''}'
>> 2018-11-15 08:19:33,438-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runAction,
>> params: [RunVm, RunVmParams:{comm
>> andId='69628467-56d3-4d93-aed1-a2807b7dbc45', user='null',
>> commandType='Unknown', vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
>> timeElapsed: 115ms
>> 2018-11-15 08:19:33,441-05 ERROR
>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>> task-5) [] Operation Failed: [Cannot run VM. Low disk space on Storage
>> Domain iscsi.]
>> 2018-11-15 08:19:34,044-05 DEBUG
>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] START,
>> GetAllVmStatsVDSCommand(HostName = lago-basic-su
>> ite-4-2-host-0,
>> VdsIdVDSCommandParametersBase:{hostId='063dfef9-bc9d-44c3-8ba3-8142e3eb129c'}),
>> log id: 65651e2b
>> 2018-11-15 08:19:34,045-05 DEBUG
>> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] SEND
>> destination:jms.topic.vdsm_requests
>> reply-to:jms.topic.vdsm_responses
>> content-length:103
>>
>>
>>
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZIG4VQKIFFARDTDJ6B2JROENN2Z44B4I/
>>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List
[ovirt-devel] Re: Getting info about qemu guest agent into the engine
On 18/11/16 11:39, Michal Skrivanek wrote: > > > > On 16 Nov 2018, at 11:22, Tomasz Barański wrote: > > > > Hello, wise people! > > > > As a part of BZ1615830[1] I want to add information about qemu guest agent > > to engine's DB. I have some trouble figuring out some details. > > > > 1. VDSM seems to be using QGA, but it does not report any information about > > it. Am I right? > > what do you mean to report any information? There are guest agent reported > fields which are either there or not > One such field is appsList which returns the agent itself (well, it’s fake > for qemu-ga, but the agent string is always put there) Oh, appsList, I didn't look into stats. Thanks, I guess that's what I was looking for. > > > I only found a mention about it in `xml` field in JSON returned by > > `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as > > documented in libvirt. > > virtio channels are always there for both agents > > > > > 2. How does the engine puts data into `vm_dynamic` table? I can't find any > > usage for `InsertVmDynamic` procedure. > > app_list ?? How is app_list used to fill in fields like `vnc_port` or `cpu_name`? > > > > > 3. Also, it's not clear to me how (whether?) the engine consumes output of > > VM.getInfo/Host.getVMFullList. > > it does not in 4.2+ clusters, see FullListAdapter::getVmFullList() > > HTH, > michal > > > Any pointers to relevant code appreciated. > > > > > > Tomo > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830 > > ___ > > Devel mailing list -- devel@ovirt.org > > To unsubscribe send an email to devel-le...@ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DASVREOUEKMRWGQ4IBGHFSBTF2XMBF3C/ > ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HTOIJHAO2STLVKVJSZU35XXWF3GAUOAB/
[ovirt-devel] Re: [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 15-11-2018 ] [ check_snapshot_with_memory ]
It's definitely not that patch - the patch is UI / GWT only and isn't
tested outside of the selenium tests in 008. Also, this is a backport and
we didn't see any issues on master.
Greg
On Fri, Nov 16, 2018, 6:24 AM Dafna Ron Hi,
> we have a failure on basic suite for test check_snapshot_with. _memory.
>
> I am actually not seeing any reason the patch would cause that specific
> issue but its consistently failing on this change.
> I am seeing a vm memory saved to the iscsi domain but aside from that
> nothing is failing before tto cause a cleanup issue or create low space on
> the storage).
> can some one please take a look to see if anything in the patch is causing
> this?
>
>
> Link and headline of suspected patches:
>
> https://gerrit.ovirt.org/#/c/95436/1 -
> webadmin: network operation in progress - sync host interfaces
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/
>
> Link to all logs:
>
>
> https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-4.2/post-004_basic_sanity.py/
>
> (Relevant) error snippet from the log:
>
>
>
> 2018-11-15 08:19:33,409-05 DEBUG
> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method:
> runVdsCommand, params: [IsVmDuringInitiating
> ,
> IsVmDuringInitiatingVDSCommandParameters:{vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
> timeElapsed: 1ms
> 2018-11-15 08:19:33,430-05 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] EVENT_ID:
> USER_FAILED_RUN_VM(54), Failed to run VM
> vm0 due to a failed validation: [Cannot run VM. Low disk space on Storage
> Domain iscsi.] (User: admin@internal-authz).
> 2018-11-15 08:19:33,430-05 WARN [org.ovirt.engine.core.bll.RunVmCommand]
> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Validation of
> action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__
> ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN,$storageName
> iscsi
> 2018-11-15 08:19:33,431-05 INFO [org.ovirt.engine.core.bll.RunVmCommand]
> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Lock freed to
> object 'EngineLock:{exclusiveLocks='[9144eb88-8f0a-4e77-9d70-3b761e
> 48ecb4=VM]', sharedLocks=''}'
> 2018-11-15 08:19:33,438-05 DEBUG
> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
> (default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runAction,
> params: [RunVm, RunVmParams:{comm
> andId='69628467-56d3-4d93-aed1-a2807b7dbc45', user='null',
> commandType='Unknown', vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
> timeElapsed: 115ms
> 2018-11-15 08:19:33,441-05 ERROR
> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
> task-5) [] Operation Failed: [Cannot run VM. Low disk space on Storage
> Domain iscsi.]
> 2018-11-15 08:19:34,044-05 DEBUG
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] START,
> GetAllVmStatsVDSCommand(HostName = lago-basic-su
> ite-4-2-host-0,
> VdsIdVDSCommandParametersBase:{hostId='063dfef9-bc9d-44c3-8ba3-8142e3eb129c'}),
> log id: 65651e2b
> 2018-11-15 08:19:34,045-05 DEBUG
> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message]
> (EE-ManagedThreadFactory-engineScheduled-Thread-25) [] SEND
> destination:jms.topic.vdsm_requests
> reply-to:jms.topic.vdsm_responses
> content-length:103
>
>
>
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZIG4VQKIFFARDTDJ6B2JROENN2Z44B4I/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/A62A2KACAGE5I7Y5MN5JPTKKI644YEJM/
[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 15-11-2018 ] [ check_snapshot_with_memory ]
Hi,
we have a failure on basic suite for test check_snapshot_with. _memory.
I am actually not seeing any reason the patch would cause that specific
issue but its consistently failing on this change.
I am seeing a vm memory saved to the iscsi domain but aside from that
nothing is failing before tto cause a cleanup issue or create low space on
the storage).
can some one please take a look to see if anything in the patch is causing
this?
Link and headline of suspected patches:
https://gerrit.ovirt.org/#/c/95436/1 -
webadmin: network operation in progress - sync host interfaces
Link to Job:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/
Link to all logs:
https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3487/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-4.2/post-004_basic_sanity.py/
(Relevant) error snippet from the log:
2018-11-15 08:19:33,409-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method:
runVdsCommand, params: [IsVmDuringInitiating
,
IsVmDuringInitiatingVDSCommandParameters:{vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
timeElapsed: 1ms
2018-11-15 08:19:33,430-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] EVENT_ID:
USER_FAILED_RUN_VM(54), Failed to run VM
vm0 due to a failed validation: [Cannot run VM. Low disk space on Storage
Domain iscsi.] (User: admin@internal-authz).
2018-11-15 08:19:33,430-05 WARN [org.ovirt.engine.core.bll.RunVmCommand]
(default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Validation of
action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__
ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_SPACE_LOW_ON_STORAGE_DOMAIN,$storageName
iscsi
2018-11-15 08:19:33,431-05 INFO [org.ovirt.engine.core.bll.RunVmCommand]
(default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] Lock freed to
object 'EngineLock:{exclusiveLocks='[9144eb88-8f0a-4e77-9d70-3b761e
48ecb4=VM]', sharedLocks=''}'
2018-11-15 08:19:33,438-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-5) [dce28fd0-bebc-4aba-80d5-ffc081b1f591] method: runAction,
params: [RunVm, RunVmParams:{comm
andId='69628467-56d3-4d93-aed1-a2807b7dbc45', user='null',
commandType='Unknown', vmId='9144eb88-8f0a-4e77-9d70-3b761e48ecb4'}],
timeElapsed: 115ms
2018-11-15 08:19:33,441-05 ERROR
[org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
task-5) [] Operation Failed: [Cannot run VM. Low disk space on Storage
Domain iscsi.]
2018-11-15 08:19:34,044-05 DEBUG
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [] START,
GetAllVmStatsVDSCommand(HostName = lago-basic-su
ite-4-2-host-0,
VdsIdVDSCommandParametersBase:{hostId='063dfef9-bc9d-44c3-8ba3-8142e3eb129c'}),
log id: 65651e2b
2018-11-15 08:19:34,045-05 DEBUG
[org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message]
(EE-ManagedThreadFactory-engineScheduled-Thread-25) [] SEND
destination:jms.topic.vdsm_requests
reply-to:jms.topic.vdsm_responses
content-length:103
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZIG4VQKIFFARDTDJ6B2JROENN2Z44B4I/
[ovirt-devel] Re: Getting info about qemu guest agent into the engine
> On 16 Nov 2018, at 11:22, Tomasz Barański wrote: > > Hello, wise people! > > As a part of BZ1615830[1] I want to add information about qemu guest agent > to engine's DB. I have some trouble figuring out some details. > > 1. VDSM seems to be using QGA, but it does not report any information about > it. Am I right? what do you mean to report any information? There are guest agent reported fields which are either there or not One such field is appsList which returns the agent itself (well, it’s fake for qemu-ga, but the agent string is always put there) > I only found a mention about it in `xml` field in JSON returned by > `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as > documented in libvirt. virtio channels are always there for both agents > > 2. How does the engine puts data into `vm_dynamic` table? I can't find any > usage for `InsertVmDynamic` procedure. app_list > > 3. Also, it's not clear to me how (whether?) the engine consumes output of > VM.getInfo/Host.getVMFullList. it does not in 4.2+ clusters, see FullListAdapter::getVmFullList() HTH, michal > Any pointers to relevant code appreciated. > > > Tomo > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830 > ___ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DASVREOUEKMRWGQ4IBGHFSBTF2XMBF3C/ ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JQCUX6W5PUZCA4K3SV5H2XZOIXRZK3SW/
[ovirt-devel] Getting info about qemu guest agent into the engine
Hello, wise people! As a part of BZ1615830[1] I want to add information about qemu guest agent to engine's DB. I have some trouble figuring out some details. 1. VDSM seems to be using QGA, but it does not report any information about it. Am I right? I only found a mention about it in `xml` field in JSON returned by `VM.getInfo` (and `Host.getVMFullList`): a `virtio` channel as documented in libvirt. 2. How does the engine puts data into `vm_dynamic` table? I can't find any usage for `InsertVmDynamic` procedure. 3. Also, it's not clear to me how (whether?) the engine consumes output of VM.getInfo/Host.getVMFullList. Any pointers to relevant code appreciated. Tomo [1] https://bugzilla.redhat.com/show_bug.cgi?id=1615830 ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DASVREOUEKMRWGQ4IBGHFSBTF2XMBF3C/
