oVirt infra daily report - unstable production jobs - 760

2019-03-10 Thread jenkins
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/760//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 10/03/2019
 
00 Unstable Critical
 
   
   ovirt-engine-api-model_master_build-artifacts-fc28-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng-image_master_build-artifacts-fc28-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng_4.2_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_hc-basic-suite-4.2
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-ansible-suite-4.3
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-ipv6-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   ___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/LLMXAAH2KQP75IRLGY7E4TES4RX26DMG/


[CQ]: 98407, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
98407,3 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/98407/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13352/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/QXOUA3EX647DOSM3DFFSF3K55CH6E2XJ/


[JIRA] (OVIRT-2697) error before starting tests

2019-03-10 Thread Dafna Ron (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39158#comment-39158
 ] 

Dafna Ron commented on OVIRT-2697:
--

we did




> error before starting tests
> ---
>
> Key: OVIRT-2697
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Ahmad Khiet
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/KP22XJR3UDQMH54FT53IZNUML6MMZGX7/


Re: [JIRA] (OFT-653) error before starting tests

2019-03-10 Thread Dafna Ron
we did

On Sun, Mar 10, 2019 at 3:03 PM Eyal Edri  wrote:

> i think we agreed to drop this project IIRC and report issues on the ovirt
> project, Dafna?
>
> On Sun, Mar 10, 2019, 16:47 Liora Milbaum (oVirt JIRA) <
> j...@ovirt-jira.atlassian.net> wrote:
>
>>
>>  [
>> https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Liora Milbaum reassigned OFT-653:
>> -
>>
>> Assignee: infra  (was: Liora Milbaum)
>>
>> > error before starting tests
>> > ---
>> >
>> > Key: OFT-653
>> > URL: https://ovirt-jira.atlassian.net/browse/OFT-653
>> > Project: OST Failures Tracking
>> >  Issue Type: Bug
>> >Reporter: Ahmad Khiet
>> >Assignee: infra
>> >Priority: High
>> >  Labels: ost_failures
>> >
>>
>>
>>
>>
>> --
>> This message was sent by Atlassian Jira
>> (v1001.0.0-SNAPSHOT#100099)
>> ___
>> Infra mailing list -- infra@ovirt.org
>> To unsubscribe send an email to infra-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/infra@ovirt.org/message/NLIEAQ73VNG2XOGP7JTOKHM6GK3OSGUY/
>>
>
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/WTGGPQDGE7ZMABHJYWWBAF23UVO7HOFM/


[CQ]: 91993, 39 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
91993,39 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/91993/39

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13346/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/OF5PQAQSQPA46JUFZTIVBM6EMFYJZXLW/


[JIRA] (OVIRT-2698) Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to

2019-03-10 Thread Liora Milbaum (oVirt JIRA)
Liora Milbaum created OVIRT-2698:


 Summary: Upgrade Suite: Copy from 
lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to
 Key: OVIRT-2698
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2698
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Liora Milbaum
Assignee: infra


[CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
https://gerrit.ovirt.org/#/c/94713/1
http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/

  # 001_upgrade_engine.test_initialize_engine: 
* Copy 
/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf
 to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: 

* Copy 
/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf
 to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: 
Success (in 0:00:00)
* Collect artifacts: 
~ [Thread-8] Copy from 
lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to 
/dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/default/test_logs/001_upgrade_engine.test_initialize_engine-20190307160642/lago-upgrade-from-prevrelease-suite-4-3-engine/_tmp_otopi*:
 ERROR (in 0:00:00)
  - [Thread-8] lago-upgrade-from-prevrelease-suite-4-3-engine: 
ERROR (in 0:00:00)
* Collect artifacts: ERROR (in 0:00:01)
  # 001_upgrade_engine.test_initialize_engine: ERROR (in 
0:00:49)
  # Results located at 
/dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/001_upgrade_engine.py.junit.xml
@ Run test: 001_upgrade_engine.py: ERROR (in 0:00:49)
Error occured, aborting
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run
self.cli_plugins[args.ovirtverb].do_run(args)
  File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in 
do_run
self._do_run(**vars(args))
  File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper
return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper
return func(*args, prefix=prefix, **kwargs)
  File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in 
do_ovirt_runtest
raise RuntimeError('Some tests failed')
RuntimeError: Some tests failed



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/VYKJWKM3G46XRED4HEPN5LGONUQOPIIR/


[JIRA] (OVIRT-2698) Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum updated OVIRT-2698:
-
Labels: ost_failures  (was: )

> Upgrade Suite: Copy from 
> lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to
> --
>
> Key: OVIRT-2698
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2698
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Liora Milbaum
>Assignee: infra
>  Labels: ost_failures
>
> [CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
> https://gerrit.ovirt.org/#/c/94713/1
> http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/
>   # 001_upgrade_engine.test_initialize_engine: 
> * Copy 
> /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf
>  to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: 
> 
> * Copy 
> /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf
>  to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: 
> Success (in 0:00:00)
> * Collect artifacts: 
> ~ [Thread-8] Copy from 
> lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to 
> /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/default/test_logs/001_upgrade_engine.test_initialize_engine-20190307160642/lago-upgrade-from-prevrelease-suite-4-3-engine/_tmp_otopi*:
>  ERROR (in 0:00:00)
>   - [Thread-8] lago-upgrade-from-prevrelease-suite-4-3-engine: 
> ERROR (in 0:00:00)
> * Collect artifacts: ERROR (in 0:00:01)
>   # 001_upgrade_engine.test_initialize_engine: ERROR (in 
> 0:00:49)
>   # Results located at 
> /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/001_upgrade_engine.py.junit.xml
> @ Run test: 001_upgrade_engine.py: ERROR (in 0:00:49)
> Error occured, aborting
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in 
> do_run
> self.cli_plugins[args.ovirtverb].do_run(args)
>   File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in 
> do_run
> self._do_run(**vars(args))
>   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper
> return func(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper
> return func(*args, prefix=prefix, **kwargs)
>   File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in 
> do_ovirt_runtest
> raise RuntimeError('Some tests failed')
> RuntimeError: Some tests failed



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/I4DH3SC4CJIAJ2OESPON5H3P3HO2XVXA/


[JIRA] (OVIRT-2697) error before starting tests

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum moved OFT-653 to OVIRT-2697:
--

 Project: oVirt - virtualization made easy  (was: OST Failures Tracking)
Workflow: Task Management Workflow  (was: Software Simplified Workflow for 
Project OFT)
 Key: OVIRT-2697  (was: OFT-653)

> error before starting tests
> ---
>
> Key: OVIRT-2697
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Ahmad Khiet
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/NWNRBREMSTD43CURTMUQ45GNUJXZUVFC/


Re: [JIRA] (OFT-653) error before starting tests

2019-03-10 Thread Eyal Edri
i think we agreed to drop this project IIRC and report issues on the ovirt
project, Dafna?

On Sun, Mar 10, 2019, 16:47 Liora Milbaum (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

>
>  [
> https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Liora Milbaum reassigned OFT-653:
> -
>
> Assignee: infra  (was: Liora Milbaum)
>
> > error before starting tests
> > ---
> >
> > Key: OFT-653
> > URL: https://ovirt-jira.atlassian.net/browse/OFT-653
> > Project: OST Failures Tracking
> >  Issue Type: Bug
> >Reporter: Ahmad Khiet
> >Assignee: infra
> >Priority: High
> >  Labels: ost_failures
> >
>
>
>
>
> --
> This message was sent by Atlassian Jira
> (v1001.0.0-SNAPSHOT#100099)
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-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/infra@ovirt.org/message/NLIEAQ73VNG2XOGP7JTOKHM6GK3OSGUY/
>
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/RATRWY5EXDJLCQTSHMRIKY3ZAYRGS3AM/


[JIRA] (OFT-653) error before starting tests

2019-03-10 Thread Eyal Edri (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39157#comment-39157
 ] 

Eyal Edri commented on OFT-653:
---

i think we agreed to drop this project IIRC and report issues on the ovirt
project, Dafna?

On Sun, Mar 10, 2019, 16:47 Liora Milbaum (oVirt JIRA) <



> error before starting tests
> ---
>
> Key: OFT-653
> URL: https://ovirt-jira.atlassian.net/browse/OFT-653
> Project: OST Failures Tracking
>  Issue Type: Bug
>Reporter: Ahmad Khiet
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/ZRLFEOIVX3EVNSXNK26N3UIKAPCTX4VJ/


[JIRA] (OFT-653) error before starting tests

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum reassigned OFT-653:
-

Assignee: infra  (was: Liora Milbaum)

> error before starting tests
> ---
>
> Key: OFT-653
> URL: https://ovirt-jira.atlassian.net/browse/OFT-653
> Project: OST Failures Tracking
>  Issue Type: Bug
>Reporter: Ahmad Khiet
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/NLIEAQ73VNG2XOGP7JTOKHM6GK3OSGUY/


[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum updated OVIRT-2696:
-
Summary: verify_glance_import - AttributeError: 'NoneType' object has no 
attribute 'status'  (was: AttributeError: 'NoneType' object has no attribute 
'status')

> verify_glance_import - AttributeError: 'NoneType' object has no attribute 
> 'status'
> --
>
> Key: OVIRT-2696
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Liora Milbaum
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>
> [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't 
> the failure root cause
> Project name - ovirt-engine
> Branch - ovirt-master
> Failed Suite - basic suite
> Failed test/failed phase
> Link to first reported failed build - 
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/
> Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/6EH7FH6NOT7LVTATSWBWAVQXBPC7N7LY/


[JIRA] (OVIRT-2696) AttributeError: 'NoneType' object has no attribute 'status'

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum updated OVIRT-2696:
-
Labels: ost_failures  (was: )

> AttributeError: 'NoneType' object has no attribute 'status'
> ---
>
> Key: OVIRT-2696
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Liora Milbaum
>Assignee: infra
>Priority: High
>  Labels: ost_failures
>
> [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't 
> the failure root cause
> Project name - ovirt-engine
> Branch - ovirt-master
> Failed Suite - basic suite
> Failed test/failed phase
> Link to first reported failed build - 
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/
> Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/UWZR5B64CWLW6PZLVYLEPEJW3VOHTT6P/


[JIRA] (OVIRT-2696) AttributeError: 'NoneType' object has no attribute 'status'

2019-03-10 Thread Liora Milbaum (oVirt JIRA)
Liora Milbaum created OVIRT-2696:


 Summary: AttributeError: 'NoneType' object has no attribute 
'status'
 Key: OVIRT-2696
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Liora Milbaum
Assignee: infra
Priority: High


[CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the 
failure root cause

Project name - ovirt-engine
Branch - ovirt-master
Failed Suite - basic suite
Failed test/failed phase
Link to first reported failed build - 
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/
Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/T2ON32WDMUF7O5G47A3AR4OHPZ5IMLJ4/


Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]

2019-03-10 Thread Liora Milbaum
Is the following log snippet, taken from [1], relevant to this thread:

 [36m  # resize_and_refresh_storage_domain:  [32mSuccess [0m (in 0:00:04) [0m
 [36m  # add_vm2_lease:  [0m [0m [0m
 [36m* Collect artifacts:  [0m [0m [0m
 [36m~ [Thread-620] Copy from
lago-basic-suite-4-3-engine:/tmp/otopi* to
/dev/shm/ost/deployment-basic-suite-4.3/default/test_logs/002_bootstrap.add_vm2_lease-20190308151804/lago-basic-suite-4-3-engine/_tmp_otopi*:
 [31mERROR [0m (in 0:00:00) [0m
 [36m  - [Thread-620] lago-basic-suite-4-3-engine:  [31mERROR [0m
(in 0:00:00) [0m
 [36m* Collect artifacts:  [31mERROR [0m (in 0:00:01) [0m
 [36m  # add_vm2_lease:  [31mERROR [0m (in 0:00:03) [0m
 [36m  # Results located at
/dev/shm/ost/deployment-basic-suite-4.3/002_bootstrap.py.junit.xml [0m
 [36m@ Run test: 002_bootstrap.py:  [31mERROR [0m (in 0:05:17) [0m
 [31mError occured, aborting
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run
self.cli_plugins[args.ovirtverb].do_run(args)
  File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line
184, in do_run
self._do_run(**vars(args))
  File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper
return func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper
return func(*args, prefix=prefix, **kwargs)
  File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107,
in do_ovirt_runtest
raise RuntimeError('Some tests failed')
RuntimeError: Some tests failed [0m


[1] 
https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.3_change-queue-tester/detail/ovirt-4.3_change-queue-tester/165/pipeline


On Fri, Mar 8, 2019 at 12:21 AM Nir Soffer  wrote:

> On Thu, Mar 7, 2019 at 8:50 PM Dafna Ron  wrote:
>
>> I report this issue to the list and the test owner is more then welcome
>> to respond.
>> Galit, can you please review the skiptest
>> https://gerrit.ovirt.org/#/c/98191/
>>
>
> I looked at engine and vdsm logs, and I don't think the add_vm2_lease test
> is related
> so there is no point to disable it.
>
> It seems that just after finishing resize_and_refresh_storage_domain test:
>
> 2019-02-27 13:37:21,036-0500 INFO (jsonrpc/5) [vdsm.api] START
> resizePV(sdUUID=u'34311cc1-c4d2-4cfe-88b5-dd5ad72261d3',
> spUUID=u'717575a9-7818-460d-ba3a-d5bdd8ef9ed3',
> guid=u'360014054e5952dc174c4a12b971ea45c', options=None)
> from=:::192.168.201.4,43920,
> flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
> task_id=5908a867-5e11-474f-8119-49cfe219d4c8 (api:48)
> 2019-02-27 13:37:21,499-0500 INFO (jsonrpc/5) [vdsm.api] FINISH resizePV
> return={'size': '24293408768'} from=:::192.168.201.4,43920,
> flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
> task_id=5908a867-5e11-474f-8119-49cfe219d4c8 (api:54)
>
> Engine try to lookup the vm lease. The lookup fails (expected since there
> is no such lease):
>
> 2019-02-27 13:37:21,968-0500 INFO  (jsonrpc/1) [vdsm.api] START
> lease_info(lease={u'sd_id': u'b370b91d-00b5-4f62-9270-ac0acd47d075',
> u'lease_id': u'3500eb82-e5e2-4e24-b41c-ea02d9f6adee'})
> from=:::192.168.201.4,43920,
> flow_id=117dec74-ad59-4b12-8148-b2c130337c10,
> task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:48)
>
> 2019-02-27 13:37:21,987-0500 INFO  (jsonrpc/1) [vdsm.api] FINISH
> lease_info error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
> from=:::192.168.201.4,43920,
> flow_id=117dec74-ad59-4b12-8148-b2c130337c10,
> task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:52)
>
> On engine side, we see immediately after that:
>
> 2019-02-27 13:37:22,078-05 DEBUG
> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
> (default task-1) [117dec74-ad59-4b12-8148-b2c130337c10] method:
> getListForSpmSelection, params: [717575a9-7818-460d-ba3a-d5bdd8ef9ed3],
> timeElapsed: 12ms
>
> Which means nothing to me, but it seems that engine treat the expected
> error to lookup the lease
> as fatal error in the spm.
>
> Soon engine try to stop the spm on host-0, which make no sense:
>
> 2019-02-27 13:37:22,125-05 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default
> task-1) [117dec74-ad59-4b12-8148-b2c130337c10] SpmStopVDSCommand::Stopping
> SPM on vds 'lago-basic-suite-master-host-0', pool id
> '717575a9-7818-460d-ba3a-d5bdd8ef9ed3'
>
> At the same time, host1 has trouble to see the LUNs, and fail to connect
> to the pool:
>
> 2019-02-27 13:37:20,014-0500 INFO  (jsonrpc/4) [vdsm.api] START
> getDeviceList(storageType=3, guids=[u'360014055ad799e3a968444abdaefa323',
> u'360014054e5952dc174c4a12b971ea45c'], checkStatus=False, options={})
> from=:::192.168.201.4,33922,
> flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
> task_id=78fb7d20-8bec-4561-9867-da4174d181a6 (api:48)
>
> 2019-02-27 13:37:20,340-0500 INFO  (jsonrpc/4) [vdsm.api] FINISH
> getDeviceList return={'devList': []} from=:::192.168.201.4,33922,
> flow_id=f204cfe2-ef48-429d-ab33-e1175d
> 0530a0, 

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)

2019-03-10 Thread Liora Milbaum (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liora Milbaum reassigned OVIRT-2694:


Assignee: Liora Milbaum  (was: infra)

> some users list emails are still not being threaded properly (probably yahoo 
> / html related)
> 
>
> Key: OVIRT-2694
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Greg Sheremeta
>Assignee: Liora Milbaum
> Attachments: Selection_042.png, image.png, strahil original.pdf
>
>
> some users list emails are still not being threaded properly (probably yahoo 
> / html related)
> All of Strahil's messages do this. See screenshots and original message dump 
> attached.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/A5GWXIVCYGFYPPX2MUAXZAAA6WTT3FI3/


[CQ]: 98364, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
98364,5 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/98364/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13345/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/X7WM4FH6C7SOX56RIJMHX2TGNIPH5XOQ/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39155#comment-39155
 ] 

Barak Korren commented on OVIRT-2695:
-

Here:

https://docs.google.com/document/d/1UYwjJdZLvlLdbfV2izx4Qs8fjagG1FB-meqjOnChOuk/edit?usp=sharing

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/S3EDMUBQOV46UC744OFXZHQT3SOAEOKI/


[CQ]: 97030, 14 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
97030,14 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/97030/14

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13342/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/QNMGQP3IKTB5EHL2LXBR3T7SL3AK23R2/


Jenkins build is back to normal : system-sync_mirrors-fedora-base-fc29-x86_64 #371

2019-03-10 Thread jenkins
See 

___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/QPZ4MRU27422KJZQYJCZDJTPFLATXREG/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Eyal Edri (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39154#comment-39154
 ] 

Eyal Edri commented on OVIRT-2695:
--

Can you share the link?

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/7PGCHNQQKPDU2QKMOCH3SXKMZ6EYGW7N/


Jenkins build is back to normal : system-sync_mirrors-centos-kvm-common-el7-x86_64 #2270

2019-03-10 Thread jenkins
See 

___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/6TBGBFDCLI46MB2YLZPBAGTWYVD5ZZEV/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39153#comment-39153
 ] 

Barak Korren commented on OVIRT-2695:
-

[~eedri] already added it to [~lmilb...@redhat.com]'s KB doc

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/YZ3QUC2WSVUXWH46ZENCLTRTU3JAZRXV/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Eyal Edri (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39152#comment-39152
 ] 

Eyal Edri commented on OVIRT-2695:
--

Barak,
can you please add info how and where you cleared the cache for future
reference so we can look up this ticket if needed in the future?

thanks

On Sun, Mar 10, 2019, 13:12 Barak Korren (oVirt JIRA) <



> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/OOBFJ5HY2UBTJGUGDPOIHOWRK4TXN6NX/


Re: [JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Eyal Edri
Barak,
can you please add info how and where you cleared the cache for future
reference so we can look up this ticket if needed in the future?

thanks

On Sun, Mar 10, 2019, 13:12 Barak Korren (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

>
>  [
> https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Barak Korren updated OVIRT-2695:
> 
> Blocked By: user response
> Status: Blocked  (was: To Do)
>
> blocking ticket on user response
>
> > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> > --
> >
> > Key: OVIRT-2695
> > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> > Project: oVirt - virtualization made easy
> >  Issue Type: Outage
> >  Components: CI client projects, Jenkins Slaves
> >Reporter: Nir Soffer
> >Assignee: Barak Korren
> >
> > build-artifacts on s390x fail now with:
> > [Errno 2] No such file or directory:
> >
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> > Here are few example failures:
> >
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> >
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> > This is going to block the change queue when we merge these patches,
> > and we have 4.3 build soon.
> > We had this issue few week ago, and Barak fixed this by deleting caches
> on
> > the slaves. I hope this can be fixed quickly
> > this time.
> > Nir
>
>
>
> --
> This message was sent by Atlassian Jira
> (v1001.0.0-SNAPSHOT#100099)
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-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/infra@ovirt.org/message/J67TBKAAFH3G4GNBJCMNX7LAKTLGMJW6/
>
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/XXOG63IOUVPVCOJYWVNHQLTRDFPAHXX6/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2695:

Blocked By: user response
Status: Blocked  (was: To Do)

blocking ticket on user response

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/J67TBKAAFH3G4GNBJCMNX7LAKTLGMJW6/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39150#comment-39150
 ] 

Barak Korren commented on OVIRT-2695:
-

[~nsof...@redhat.com] I cleared the caches, please check that your jobs pass now

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/H26EBJOZWI5AHIXP7NVCMFVZJB5H5WZ4/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2695:

Component/s: CI client projects
 Jenkins Slaves

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/MISPDVYNZ2FCFICKTNSEW3MMAW2SKPLS/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2695:

Issue Type: Outage  (was: By-EMAIL)

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects, Jenkins Slaves
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/IZ4JXL3MZTBQT6KPIPOI74TDIOEMEYX6/


[CQ]: 97030, 14 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
97030,14 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/97030/14

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13338/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/ZBKYIKVDAYTIK6M2WR3IWDZHNFABDTRE/


[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)

2019-03-10 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren reassigned OVIRT-2695:
---

Assignee: Barak Korren  (was: infra)

> [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
> --
>
> Key: OVIRT-2695
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> build-artifacts on s390x fail now with:
> [Errno 2] No such file or directory:
> '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm'
> Here are few example failures:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3727/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3732/pipeline
> This is going to block the change queue when we merge these patches,
> and we have 4.3 build soon.
> We had this issue few week ago, and Barak fixed this by deleting caches on
> the slaves. I hope this can be fixed quickly
> this time.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/VF77JT6QDF4Q6BCD4R7236VVAK5LKCMU/


[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems

2019-03-10 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39149#comment-39149
 ] 

Barak Korren commented on OVIRT-2252:
-

we cannot, because of the way stdciv2 works, if we drop the slave, the jobs for 
the 'jenkins' repo will never finish.

I wouldn't want to just drop the 'jenkins' repo jobs, because that is the only 
way we have ATM to pre-test some things.

I think at this point the solution we should aim for is to containerize the 
s390x host, that would resolve this issue and would enable us to drop support 
for not-containerized hosts in the future. I actually had a chat with the 
host's maintainer a while ago, and he was willing to install docker there. The 
intiative died out because I did not have time to push it further.

> The s390x slave is used in parallel by both the staging and the production CI 
> systems
> -
>
> Key: OVIRT-2252
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins Slaves
>Reporter: Barak Korren
>Assignee: infra
>
> Since we only have one s390x slave, it is currently attached to both the 
> staging and the production CI systems, and while they use separate user 
> accounts, it turns out this is not enough to isolate them from one another.
> The are several issues that are caused by this configuration:
> # Tests that allocate a fixed network port can fail if they are run by both 
> systems at the same time - this happens in practice when sending Python 
> patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start 
> a web server on port 8675.
> # The {{mock_cleanup.sh}} script that is being run by one system can time out 
> trying to umount things from a mock environment that was created and is being 
> used by the other system.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/44Q6QHOXI4J4A4I7GZZQGN4TAWQ6AK7V/


[CQ]: 98364, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

2019-03-10 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
98364,5 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97381,22 (vdsm) that this change depends on or is based
on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 97381,22 (vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://gerrit.ovirt.org/#/c/98364/5

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/97381/22

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13336/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-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/infra@ovirt.org/message/Y37XJYDT6EHT4EP6OY7IWQ6ZLFDHL4UW/