oVirt infra daily report - unstable production jobs - 754

[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/754//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 04/03/2019
 
00 Unstable Critical
 
   
   ovirt-appliance_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-appliance_ovirt-4.3_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-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_4.3_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-node-ng-image_4.3_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-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-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-provider-ovn_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_hc-basic-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.

   
   
   
   ovirt-system-tests_he-basic-iscsi-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_master_standard-poll-upstream-sources
   
   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_openshift-on-ovirt-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.

 

[CQ]: b2ac05e (v2v-conversion-host) failed "ovirt-master" system tests

[oVirt Jenkins]

Change b2ac05e (v2v-conversion-host) is probably the reason behind recent
system test failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://github.com/oVirt/v2v-conversion-host/commit/b2ac05e131384e50835f8705032b289fdea7b10c

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13234/
___
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/JWSPFV53X24DY24BF4L6FVFP5G4ZST3D/

[JIRA] (OVIRT-2566) make network suite blocking

[Nir Soffer (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39119#comment-39119
 ] 

Nir Soffer commented on OVIRT-2566:
---

On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) <


I'm ok with this only if it will gate *only* vdsm-network package, and it
will run in parallel, so
it does not slow down OST run.

For basic suite, we have too many random failures, so I don't think it is
useful, and we should
make it optional.

Nir




> make network suite blocking
> ---
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: OST
>Reporter: danken
>Assignee: infra
>Priority: High
>
> The network suite is executing nightly for almost a year. It has a caring 
> team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due to 
> a production code bug.
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/
> I would like to see this suite escalated to the importance of the basic 
> suite, making it a gating condition for marking a collection of packages as 
> "tested".
> [~gbenh...@redhat.com], what should be done to make this happen?



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
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/RDPMPJJQ4FRUURJ3YRLFJHBP5KNBV5AJ/

Re: [JIRA] (OVIRT-2566) make network suite blocking

[Nir Soffer]

On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

> danken created OVIRT-2566:
> -
>
>  Summary: make network suite blocking
>  Key: OVIRT-2566
>  URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
>  Project: oVirt - virtualization made easy
>   Issue Type: Improvement
>   Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
>
> The network suite is executing nightly for almost a year. It has a caring
> team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due
> to a production code bug.
>
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/
>
> I would like to see this suite escalated to the importance of the basic
> suite, making it a gating condition for marking a collection of packages as
> "tested".
>

I'm ok with this only if it will gate *only* vdsm-network package, and it
will run in parallel, so
it does not slow down OST run.

For basic suite, we have too many random failures, so I don't think it is
useful, and we should
make it optional.

Nir


>
> [~gbenh...@redhat.com], what should be done to make this happen?
>
>
>
>
> --
> This message was sent by Atlassian Jira
> (v1001.0.0-SNAPSHOT#100095)
> ___
> 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/VFQ776FLS2QBATFSUFFETZUTJIYUK3LL/
>
___
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/E5FK7BB7NLV3AVAOUQRW3KH7N3L652ZA/

[CQ]: ad74db5 (v2v-conversion-host) failed "ovirt-master" system tests

[oVirt Jenkins]

Change ad74db5 (v2v-conversion-host) is probably the reason behind recent
system test failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://github.com/oVirt/v2v-conversion-host/commit/ad74db5a93b7cff1f5309fc0f18bd8d34096a54a

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13229/
___
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/6MMEOSJ2ZS2HZGYJEQCHG66GGTCNOYAD/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1478 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-gg1mn.___
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/S3NZV7RFF3Y7PRMKUJ4HTUNCOVRV2N7K/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1478 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-9t3rf.___
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/H5YFO6X3VZTE6MTII7E2T6OVB6INO3SA/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1477 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-423j5.___
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/SU6YJBCPFVFLOVNYKSHBJ2FHJXRP4C7C/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1477 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-qv1hn.___
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/DODQZXUTV55ZGPXRLQ4CYZQIIGHPLN7R/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1476 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-7bdfh.___
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/GYYTLM3OEIU326TOMPOXTGVG7EWNZSF5/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3686 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-hvhdq.___
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/GD33M4HYQYDNNI7ARKZ7FTWVDRV6ZP2O/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3686 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-807wk.___
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/5NJYBTUW3DTNBSHIMZOEDTJQ63S45D6X/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3686 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-wn4gp.___
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/R2QJR5PBMQX4SBUEKCM65XU3V6WGOO5O/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3686 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-91gr2.___
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/5CNCZ2PG7NHWRZ6QGQPTBJPK3TPYOQAH/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3685 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-l6h9v.___
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/M6TND67HR4PARHNESEBDJION3NFXGB6L/

[JIRA] (OVIRT-2693) [request] jenkins dev permission

[Anton Marchukov (oVirt JIRA)]

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

Anton Marchukov reassigned OVIRT-2693:
--

Assignee: Anton Marchukov  (was: infra)

> [request] jenkins dev permission
> 
>
> Key: OVIRT-2693
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2693
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Ahmad Khiet
>Assignee: Anton Marchukov
>
> Hi,
> can I get a developer permission on jenkins for ovirt?
> Thanks,
> Ahmad Khiet



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
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/24TGV5ZZYCNHEGWJANY7HSJTD666WT2Z/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3685 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-r68hd.___
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/2H57GZH43I2ZBGTQLGLHONPE36NJKTT7/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3685 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-zl71v.___
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/JB2YQNDSWAQOBPZUPCU3K2NLQKGTFRKQ/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3685 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-lg8w6.___
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/BJ2VEI2DXT7O5PGLXRP75JM7FRGWTNJ2/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1475 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-cm1pz.___
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/OJ3WGMRSCRDA3OY4TK6PV4U7H4KAOAO4/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1474 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-hfp3l.___
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/67KXGBON5I7EAMLF4QQR5MT3PZ632I4B/

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#1473 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-b31jr.___
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/ORNOLXQBVPPRN3UBGK3PHS27INVYO5F3/

Re: [JIRA] (OVIRT-2566) make network suite blocking

[Eyal Edri]

We still need to allocate bare metal to run it on each CQ run, and I'm not
sure we have available resources for it, pretty sure we don't have since
KubeVirt took half of the hosts.


On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

>
> [
> https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39113#comment-39113
> ]
>
> danken commented on OVIRT-2566:
> ---
>
> Is there news here? Would you try adding it?
>
> A benefit for sequential execution, is that you don't need to waste
> resources on the network suite if the basic suite has finished successfully.
>
> > make network suite blocking
> > ---
> >
> > Key: OVIRT-2566
> > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> > Project: oVirt - virtualization made easy
> >  Issue Type: Improvement
> >  Components: OST
> >Reporter: danken
> >Assignee: infra
> >Priority: High
> >
> > The network suite is executing nightly for almost a year. It has a
> caring team that tends to it, and it does not have false positives.
> > Currently, it currently fails for a week on the 4.2 branch, but it is
> due to a production code bug.
> >
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/
> > I would like to see this suite escalated to the importance of the basic
> suite, making it a gating condition for marking a collection of packages as
> "tested".
> > [~gbenh...@redhat.com], what should be done to make this happen?
>
>
>
> --
> This message was sent by Atlassian Jira
> (v1001.0.0-SNAPSHOT#100098)
> ___
> 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/3WAKBKFISFUPWW22URYET3CDSE7X36Y5/
>


-- 

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
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/JYY66IV7TBMLH47YUZP7XDLK56L34MPQ/

[JIRA] (OVIRT-2566) make network suite blocking

[Eyal Edri (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39115#comment-39115
 ] 

Eyal Edri commented on OVIRT-2566:
--

We still need to allocate bare metal to run it on each CQ run, and I'm not
sure we have available resources for it, pretty sure we don't have since
KubeVirt took half of the hosts.


On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) <



-- 

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)


> make network suite blocking
> ---
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: OST
>Reporter: danken
>Assignee: infra
>Priority: High
>
> The network suite is executing nightly for almost a year. It has a caring 
> team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due to 
> a production code bug.
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/
> I would like to see this suite escalated to the importance of the basic 
> suite, making it a gating condition for marking a collection of packages as 
> "tested".
> [~gbenh...@redhat.com], what should be done to make this happen?



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
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/QR4KQGH67J2E4CYSA7EKFTOJIQHRQYHO/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-c2m45.___
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/V2ZWCTJZY5BLBLYYINVFZECPCRD3KBKK/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-7zxnk.___
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/U4EJ35OBFGYEF6XQLU45NCUGS652RUND/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-0cq3b.___
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/K2DC4KFGFTSRDFKNEWDE2J4RD7IL53CW/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-90n54.___
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/ZFZW3HBX3EW2MB6OW4KF4RRWQSZRSEZU/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-62gsk.___
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/URHLVEUSFQX5ZRVRY6QLV7M5UEAAN7AY/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-9fvmp.___
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/ADPXUYI7JLEL7ZUFXFHSQDPBE436GMTZ/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-4rfdb.___
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/5FL3GLDHDANG63CGULUS2ERYHZYSD34A/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-0llb9.___
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/VWO265XMNVHBZO5MSITVJNN2UI3LYI34/

Jenkins build is back to stable : ovirt_master_publish-rpms_nightly #1278

[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/2UU4FCSAMAH6MKCTI4PP2CM7BDUVBUOV/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-2jp6g.___
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/HYT7P4UGT2QH4NJ5X5OVRXQGY4G5SUPE/

[JIRA] (OVIRT-2566) make network suite blocking

[danken (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39113#comment-39113
 ] 

danken commented on OVIRT-2566:
---

Is there news here? Would you try adding it?

A benefit for sequential execution, is that you don't need to waste resources 
on the network suite if the basic suite has finished successfully.

> make network suite blocking
> ---
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: OST
>Reporter: danken
>Assignee: infra
>Priority: High
>
> The network suite is executing nightly for almost a year. It has a caring 
> team that tends to it, and it does not have false positives.
> Currently, it currently fails for a week on the 4.2 branch, but it is due to 
> a production code bug.
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/
> I would like to see this suite escalated to the importance of the basic 
> suite, making it a gating condition for marking a collection of packages as 
> "tested".
> [~gbenh...@redhat.com], what should be done to make this happen?



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
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/3WAKBKFISFUPWW22URYET3CDSE7X36Y5/

Jenkins build is back to stable : ovirt_4.2_publish-rpms_nightly #525

[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/QKIESJS47OEHF4AAJR6ILX4XCJFJST4Q/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-7mgq8.___
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/CJ3DST5NAIQQKGCMGIZ7NSCJZHM2FI5G/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3682 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-lbq2g.___
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/JVNXZGLTVSVLWUXS4KKKVF3CTFSF76X5/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3682 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-v095q.___
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/XHCQNKUKCFSPPOGM6MDI4HW273BLXQ6X/

[CQ]: f7c5585 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests

[oVirt Jenkins]

Change f7c5585 (ovirt-ansible-engine-setup) is probably the reason behind
recent system test failures in the "ovirt-4.2" change queue and needs to be
fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://github.com/oVirt/ovirt-ansible-engine-setup/commit/f7c5585dd76b3f882dc2348821ae99ec904b7f75

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3978/
___
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/ZGIAXJCQN445JSHW3F3EEFBJKI7FR75U/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3682 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-0mg3q.___
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/L6EC5UAAUY6VJP3OIA7CG3MI2PAB3QMD/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3682 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-9rxps.___
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/ZESBZKEFXV3HXULDIBSSRSPUQ7IOKBBL/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3682 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-g25mt.___
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/C37E7AHCMNFM3O7ETCZOHLBNKUZZKANC/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3681 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-pfldz.___
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/RIZOTJGXXQCY3A4RYMQ7U52TAZ7VYLR6/

Re: [CQ]: 98203, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests

[Dafna Ron]

This was reported to the list and a bugzilla opened to fix it
until the issue is resolved I will add a skiptest

On Mon, Mar 4, 2019 at 9:42 AM oVirt Jenkins  wrote:

> Change 98203,1 (ovirt-engine-extension-aaa-jdbc) is probably the reason
> behind
> recent system test failures in the "ovirt-master" change queue and needs
> to be
> fixed.
>
> This change had been removed from the testing queue. Artifacts build from
> this
> change will not be released until it is fixed.
>
> For further details about the change see:
> https://gerrit.ovirt.org/#/c/98203/1
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13223/
> ___
> 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/FOJ4YWYCIRRP7GR6IKZAALVI2WOOAYMR/
>
___
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/MT4WLVKRW7DT53TK5DPWA24PVLFK52WT/

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

[Dafna Ron]

As I had another failure of this today I will be disabling this test until
issue is resolved (https://bugzilla.redhat.com/1684267)

Thanks,
Dafna


On Thu, Feb 28, 2019 at 8:48 PM Nir Soffer  wrote:

> On Thu, Feb 28, 2019 at 11:52 AM Dafna Ron  wrote:
>
>> Hi,
>>
>> We have a failure on the project in basic suite, master branch. The
>> recent failure was in patch:
>> https://gerrit.ovirt.org/#/c/98087/1 - Add pre-seed for ovirt-web-ui
>>
>> CQ is pointing at the below as the root cause (which was merged a while
>> back):
>> https://gerrit.ovirt.org/#/c/97491/ - Add pre-seed for ovirt-web-ui
>>
>> Can you please check the issue as it seems both patches are changing the
>> same thing and the project seem to be broken since
>> https://gerrit.ovirt.org/#/c/97491/3
>>
>> Latest failure:
>> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/
>>
>> Logs:
>>
>> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/
>>
>> errors from logs:
>> Engine:
>>
>> 2019-02-27 13:37:28,479-05 ERROR
>> [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25]
>> Transaction rolled-back for command
>> 'org.ovirt.engine.core.bll.UpdateVmCommand'.
>> 2019-02-27 13:37:28,483-05 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-1) [74283e25] EVENT_ID: USER_FAILED_UPDATE_VM(58), Failed to
>> update VM vm2 (User: admin@inter
>> nal-authz).
>> 2019-02-27 13:37:28,485-05 INFO
>> [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25]
>> Lock freed to object 'EngineLock:{exclusiveLocks='[vm2=VM_NAME]',
>> sharedLocks='[3500eb82-e5e2-4e24-b41c-ea
>> 02d9f6adee=VM]'}'
>> 2019-02-27 13:37:28,485-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-1) [74283e25] method: runAction, params: [UpdateVm,
>> VmManagementParametersBase:{commandId='340
>> 59769-05b9-429e-8356-f6b9b9953f55', user='admin', commandType='UpdateVm',
>> vmId='3500eb82-e5e2-4e24-b41c-ea02d9f6adee'}], timeElapsed: 6618ms
>> 2019-02-27 13:37:28,486-05 ERROR
>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>> task-1) [] Operation Failed: []
>> 2019-02-27 13:37:28,579-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] method: get, params:
>> [e29c0ba1-464c-4eb4-a8f2-c6933d9
>> 9969a], timeElapsed: 3ms
>>
>>
>> vdsm:
>>
>> 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)
>> 2019-02-27 13:37:21,988-0500 ERROR (jsonrpc/1) [storage.TaskManager.Task]
>> (Task='9c297d41-0aa7-4c74-b268-b710e666bc6c') Unexpected error (task:875)
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882,
>> in _run
>> return fn(*args, **kargs)
>>   File "", line 2, in lease_info
>>   File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
>> method
>> ret = func(*args, **kwargs)
>>   File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3702,
>> in lease_info
>> info = dom.lease_info(lease.lease_id)
>>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 674,
>> in lease_info
>> return vol.lookup(lease_id)
>>   File "/usr/lib/python2.7/site-packages/vdsm/storage/xlease.py", line
>> 553, in lookup
>> raise NoSuchLease(lease_id)
>> NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
>>
>
> This is not an error of vdsm. Someone asked for information about a
> non-existing lease,
> and vdsm fail the request with the expected error:
>
> NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
>
> But since the error is not a public error, vdsm logger handle it as
> unexpected error and
> create lot of noise in vdsm log.
>
> On engine side, this creates even worse noise, as we can see here:
>
> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
> (look for 2019-02-27 13:37:21,996-05)
>
> All these noise could be avoided if vdsm was using a proper public error.
> I filed https://bugzilla.redhat.com/1684267
>
> But, this error is not related to the actual failing test, this is just
> noise hiding the real problem.
>
> Thanks for reporting this.
>
> Nir
>
___
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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3681 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-k2wn9.___
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/TCTMGOXS3RJY55K7Y2TUDZ5UF7RCU7MT/

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[Barak Korren (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39112#comment-39112
 ] 

Barak Korren edited comment on OVIRT-2691 at 3/4/19 10:25 AM:
--

This is not a real clone failure - the issue is this:

{code}
at java.lang.Thread.run(Thread.java:748)

Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned 
status code 1:

stdout: 

stderr: warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove 
tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission denied
{code}

Jenkins is failing to run {{git clean -fdx}} because root-owned files were left 
in the workspace - this ususally happens when someone manually aborts  
{{mock_runner.sh}}.

[~grose...@redhat.com] I think you're the infra owner - please clean up the 
workspaces on the node and restore it to working condition.

[~amarchuk] please make an effort to avoid offlining slaves without following 
up with a solution


was (Author: bkor...@redhat.com):
This is not a real clone failure - the issue is this:

{code}
at java.lang.Thread.run(Thread.java:748)

Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned 
status code 1:

stdout: 

stderr: warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove 
tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission denied
{code}

Jenkins is failing to run {{git clean -fdx}} because root-owned files were left 
in the workspace - this ususally happens when someone manually aborts  
{{mock_runner.sh}}.

[~grose...@redhat.com] I think you're the infra owner - please clean up the 
workspaces on the node and restore it to working condition.

[~amarchuk] please make and effort to avoid offlining slaves without following 
up with a solution

> All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error 
> fetching remote repo 'origin'
> ---
>
> Key: OVIRT-2691
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Looks like all builds on Fedora 28 fail with this error now:
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3457/pipeline
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-c

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3681 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-3tcrm.___
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/KF2TLPPX6Q2ML3SSBOGQ35ROQ4ZUUDX6/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3681 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-6fzkn.___
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/VMEOPQ4TBDDEYUQIULSU3D3CH5OT3Q72/

[CQ]: 98203, 1 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests

[oVirt Jenkins]

Change 98203,1 (ovirt-engine-extension-aaa-jdbc) is probably the reason behind
recent system test failures in the "ovirt-master" change queue and needs to be
fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

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

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13223/
___
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/FOJ4YWYCIRRP7GR6IKZAALVI2WOOAYMR/

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[Barak Korren (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39112#comment-39112
 ] 

Barak Korren commented on OVIRT-2691:
-

This is not a real clone failure - the issue is this:

{code}
at java.lang.Thread.run(Thread.java:748)

Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned 
status code 1:

stdout: 

stderr: warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove 
.tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc:
 Permission denied

warning: failed to remove tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: 
Permission denied

warning: failed to remove 
tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission denied

warning: failed to remove 
tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission denied
{code}

Jenkins is failing to run {{git clean -fdx}} because root-owned files were left 
in the workspace - this ususally happens when someone manually aborts  
{{mock_runner.sh}}.

[~grose...@redhat.com] I think you're the infra owner - please clean up the 
workspaces on the node and restore it to working condition.

[~amarchuk] please make and effort to avoid offlining slaves without following 
up with a solution

> All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error 
> fetching remote repo 'origin'
> ---
>
> Key: OVIRT-2691
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Looks like all builds on Fedora 28 fail with this error now:
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3457/pipeline
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3455/pipeline/101
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3461/pipeline
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend
> For some reason we always get the same slave for the py27 build.
> 
> No credentials specified
> Fetching changes from the remote Git repository
> Cleaning workspace
> ERROR: Error fetching remote repo 'origin'
> hudson.plugins.git.GitException: Failed to fetch from
> https://gerrit.ovirt.org/vdsm
> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904)
> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
> at
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: hudson.plugins.git.GitException: Command "git clean -fdx"
> returned status code 1:
> stdout:
> stderr: warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc:
> Per

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3680 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-gpbvm.___
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/4K743KLCZLYHY4V6QCMSM24B4RCYVMVB/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3680 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-3237m.___
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/UIMZXMC2QJFA463TAWRJMSDTWHPBEUFF/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3680 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-7px3m.___
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/UVMD6SA23BGZILRYK3OHFORDBJF5KCL6/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3680 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-3mdnh.___
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/7UAPH4PQVIJBCYZ7RLC53PQXYM5GN5RD/

[JIRA] (OVIRT-2693) [request] jenkins dev permission

[Ahmad Khiet (oVirt JIRA)]

Ahmad Khiet created OVIRT-2693:
--

 Summary: [request] jenkins dev permission
 Key: OVIRT-2693
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2693
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Ahmad Khiet
Assignee: infra


Hi,

can I get a developer permission on jenkins for ovirt?

Thanks,
Ahmad Khiet



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
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/3RRBNOQK46PADM6OBEOUPZRMOEC4NZ4N/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-sgk4l.___
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/RX6K5IFJDQL3WEH6ZAKGCUOXPVJ7WDER/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-2r94w.___
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/YZ5VTPRROV3J3FWCCB4R764JH3H6BLUK/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-sdsgl.___
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/XXFL7642B4I2SMJ55MPRJ3MTXCT5U7PR/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-4qxkr.___
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/SB6KYEJTRPSS6KEVBZJ7APSJB4APJRRI/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-3zzh0.___
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/MR6T2C2KCF54C27KB3LEJD6OL5DIJ7DX/

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

[jenkins]

Failed to run project_setup.sh for:
#3679 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-rkjs9.___
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/RTGE2BAR2LYR2DWRCRAMIARDETDJ3WFW/

[JIRA] (OVIRT-2691) All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error fetching remote repo 'origin'

[Anton Marchukov (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39111#comment-39111
 ] 

Anton Marchukov commented on OVIRT-2691:


I have disabled this node for now till this is being investigated.

> All builds on vm0145.workers-phx.ovirt.org (fc28 phx nested) fail with: Error 
> fetching remote repo 'origin'
> ---
>
> Key: OVIRT-2691
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2691
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Looks like all builds on Fedora 28 fail with this error now:
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3457/pipeline
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3455/pipeline/101
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> -
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/3461/pipeline
>   vm0145.workers-phx.ovirt.org (fc28 phx nested)
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/buildTimeTrend
> For some reason we always get the same slave for the py27 build.
> 
> No credentials specified
> Fetching changes from the remote Git repository
> Cleaning workspace
> ERROR: Error fetching remote repo 'origin'
> hudson.plugins.git.GitException: Failed to fetch from
> https://gerrit.ovirt.org/vdsm
> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904)
> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1144)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
> at
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
> at
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: hudson.plugins.git.GitException: Command "git clean -fdx"
> returned status code 1:
> stdout:
> stderr: warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/plugin.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/compat.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/engine.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> .tox/lib-py27/lib/python2.7/site-packages/pytest_cov/__pycache__/embed.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> tests/__pycache__/pywatch_test.cpython-27-PYTEST.pyc: Permission denied
> warning: failed to remove
> tests/__pycache__/prlimit_test.cpython-27-PYTEST.pyc: Permission denied
> warning: failed to remove tests/__pycache__/ssl_test.cpython-27-PYTEST.pyc:
> Permission denied
> warning: failed to remove
> tests/__pycache__/hooking_test.cpython-27-PYTEST.pyc: Permission denied
> warning: failed to remove
> tests/common/__pycache__/systemd_test.cpython-27-PYTEST.pyc: Permission
> denied
> warning: failed to remove
> tests/common/__pycache__/systemctl_test.cpython-27-PYTEST.pyc: Permission
> denied
> warning: failed to remove
> tests/common/__pycache__/commands_test.cpython-27-PYTEST.pyc: Permission
> denied
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:901)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:912)
> at hudson.plugins.git.GitAPI.clean(GitAPI.java:311)
> at sun.reflect.GeneratedMethodAccessor225.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Deleg