[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1099 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1099/,
Build Number: 1099,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt_master_image-ng-system-tests - Build # 58 - Still Failing!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/ 
Build: http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/58/
Build Number: 58
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #37
[Yaniv Kaul] Slim down the amount of packages we sync


Changes for Build #38
[Yaniv Kaul] Slim down the amount of packages we sync

[Eyal Edri] remove emails from repo closure jobs


Changes for Build #39
[Ondřej Svoboda] Add a VM with a custom MAC to the second SD.

[Sandro Bonazzola] repos-check-closure: move master from f24 to f25

[Sandro Bonazzola] pthreading: move from fc24 to fc25 on master

[Sandro Bonazzola] aaa-misc: drop fc24 on master

[Sandro Bonazzola] logger-log4j: drop fc24 on master

[Sandro Bonazzola] python-windows: drop fc24 on master

[Sandro Bonazzola] py2exe-py2.7: drop fc24 on master


Changes for Build #40
[Ondřej Svoboda] Add a VM with a custom MAC to the second SD.


Changes for Build #41
[Ondřej Svoboda] Add a VM with a custom MAC to the second SD.


Changes for Build #42
[ngoldin] Add the engine VM IP as a valid FQDN on setup

[Daniel Belenky] mock_stup and mock_cleanup:Add Docker engine installation and 
cleanup


Changes for Build #43
[Eyal Edri] exclude openvswitch-devel & test pkg from ovirt repo

[Daniel Belenky] mock_cleanup: skip docker cleanup if docker is not installed


Changes for Build #44
[Lev Veyde] Configure NFSv3 to use static ports

[Sandro Bonazzola] qemu: don't publish on master

[Sandro Bonazzola] ovirt-release: add check-patch for ppc64le


Changes for Build #45
[Lev Veyde] Configure NFSv3 to use static ports

[Eyal Edri] dropping jobs from master publisher - first patch

[Ryan Barry] Remove vintage node jobs


Changes for Build #46
[Lev Veyde] Configure NFSv3 to use static ports

[Sandro Bonazzola] ovirt-engine-cli: drop fc24 on master

[Sandro Bonazzola] ovirt-engine-yarn: drop fc24 on master

[Sandro Bonazzola] ovirt-imageio: drop fc24 on master

[Sandro Bonazzola] ovirt-vmconsole: drop fc24 on master


Changes for Build #47
[Lev Veyde] Configure NFSv3 to use static ports


Changes for Build #48
[Ondra Machacek] Fix Ansible modules tests

[Daniel Belenky] ost publisher: replaced 'email' with 'email-ext'

[Gil Shinar] New builder that includes a few more std steps


Changes for Build #49
[Yaniv Kaul] Fix cockpit dependencies

[Sandro Bonazzola] ovirt-optimizer: drop fc24 on master

[Sandro Bonazzola] ovirt-scheduler-proxy: drop fc24 on master

[Yaniv Bronhaim] remove check-merged job in python-pthreading

[Daniel Belenky] jenkins (system_tests_template): added email-to macro to match 
the

[Pavel Zhukov] Add ovirt-web-ui project.

[ngoldin] Add lago-demo check-patch job

[Gil Shinar] Changing mock_runner mocks map to be in a file


Changes for Build #50
[Simone Tiraboschi] hc: rebase on last gdeploy

[Pavel Zhukov] Fix typo in github.yaml


Changes for Build #51
[Simone Tiraboschi] he: fetch the domain name on the first HE host

[Eyal Edri] remove ovirt 4.0 jobs

[Pavel Zhukov] Use webhooks instead of polling

[idodoroz] Remove opstools-ansible from oVirt repos


Changes for Build #52
[Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo

[Eyal Edri] removing projects from master publisher - stage II


Changes for Build #53
[Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo

[Sandro Bonazzola] ovirt-release: test ppc64le on master only

[Sandro Bonazzola] ebay-cors-filter: drop jobs


Changes for Build #54
[Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo


Changes for Build #55
[Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo


Changes for Build #56
[Sahina Bose] ovirt-system-tests: Tests for HC setup in 4.1

[Daniel Belenky] jenkins: Split ovirt-engine-_coverity-analysis job

[Daniel Belenky] jenkins: moved system jobs to /projects/system/

[Daniel Belenky] jenkins: Removed dcaro & vishnu from email alerts

[Daniel Belenky] jenkins: split scan_security_and_license job


Changes for Build #57
[Yaniv Bronhaim] Vdsm introduced abrt integration which requires additional 
rpms in

[Sandro Bonazzola] ovirt-engine-sdk: drop fc24 on master

[Sandro Bonazzola] ovirt-guest-agent: drop fc24 on master

[Pavel Zhukov] Revert "Use webhooks instead of polling"

[Eyal Edri] adding hyper converged storage system tests jobs


Changes for Build #58
[Pavel Zhukov] Revert "ost: added repo closure test"




-
Failed Tests:
-
1 tests failed.
FAILED:  002_bootstrap.add_cluster

Error Message:

status: 409
reason: Conflict
detail: KSM or balooning must be enabled to allow memory optimization.

Stack Trace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/unittest/case.py", line 367, in run
testMethod()
  File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6075 - SUCCESS!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6075/,
Build Number: 6075,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 274

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

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 28/03/2017
 
00 Unstable Critical
 
   
   ovirt-system-tests_master_check-patch-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_master-ansible-system-tests
   
   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_master_image-ng-system-tests
   
   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.

   
   
   
   test-repo_ovirt_experimental_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
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6074 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6074/,
Build Number: 6074,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6073 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6073/,
Build Number: 6073,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6072 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6072/,
Build Number: 6072,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6071 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6071/,
Build Number: 6071,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #196

[jenkins]

See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: jenkins dev role for mlipchuk user

[Barak Korren]

Forwarded to infra-support to open ticket:

https://ovirt-jira.atlassian.net/browse/OVIRT-1284

Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/

בתאריך 28 במרץ 2017 18:00,‏ "Maor Lipchuk"  כתב:

> Hi,
>
> Can you please add dev role to mlipchuk user so I can run the ci manual
> tests
>
> Thanks,
> Maor
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1284) Fwd: jenkins dev role for mlipchuk user

[Barak Korren (oVirt JIRA)]

Barak Korren created OVIRT-1284:
---

 Summary: Fwd: jenkins dev role for mlipchuk user
 Key: OVIRT-1284
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1284
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Barak Korren
Assignee: infra


Forwarding to infra-support to open ticket

Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
‏-- הודעה שהועברה --
מאת: "Maor Lipchuk" 
תאריך: 28 במרץ 2017 18:00
נושא: jenkins dev role for mlipchuk user
אל: "infra" 
‏עותק:

Hi,
>
> Can you please add dev role to mlipchuk user so I can run the ci manual
> tests
>
> Thanks,
> Maor
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change in barak-test[master]: Just a dummy change for testing

[review]

>From Barak Korren :

Barak Korren has posted comments on this change.

Change subject: Just a dummy change for testing
..


Patch Set 2: -Code-Review

-- 
To view, visit https://gerrit-staging.phx.ovirt.org/4
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5
Gerrit-PatchSet: 2
Gerrit-Project: barak-test
Gerrit-Branch: master
Gerrit-Owner: Barak Korren 
Gerrit-Reviewer: Barak Korren 
Gerrit-Reviewer: Jenkins CI 
Gerrit-HasComments: No
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change in barak-test[master]: Just a dummy change for testing

[review]

>From Barak Korren :

Barak Korren has posted comments on this change.

Change subject: Just a dummy change for testing
..


Patch Set 2: Code-Review-1 -Verified

testing again

-- 
To view, visit https://gerrit-staging.phx.ovirt.org/4
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5
Gerrit-PatchSet: 2
Gerrit-Project: barak-test
Gerrit-Branch: master
Gerrit-Owner: Barak Korren 
Gerrit-Reviewer: Barak Korren 
Gerrit-Reviewer: Jenkins CI 
Gerrit-HasComments: No
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change in barak-test[master]: Just a dummy change for testing

[review]

>From Barak Korren :

Barak Korren has posted comments on this change.

Change subject: Just a dummy change for testing
..


Patch Set 2:

testing mc'testing

-- 
To view, visit https://gerrit-staging.phx.ovirt.org/4
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5
Gerrit-PatchSet: 2
Gerrit-Project: barak-test
Gerrit-Branch: master
Gerrit-Owner: Barak Korren 
Gerrit-Reviewer: Barak Korren 
Gerrit-Reviewer: Jenkins CI 
Gerrit-HasComments: No
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1283) Repoclosure test output should be more verbose

[Pavel Zhukov (oVirt JIRA)]

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

Pavel Zhukov reassigned OVIRT-1283:
---

Assignee: Daniel Belenky  (was: infra)

> Repoclosure test output should be more verbose
> --
>
> Key: OVIRT-1283
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1283
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Pavel Zhukov
>Assignee: Daniel Belenky
>Priority: High
>
> In current implementation it's not telling too much about the failure itself:
> Error Message
> Error: repoclosure failed. exit code is: 256
> Stacktrace
> Traceback (most recent call last):
>   File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
> testMethod()
>   File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in 
> wrapped_test
> test()
>   File 
> "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/000_check_repo_closure.py",
>  line 95, in check_repo_closure
> res, 0, 'Error: repoclosure failed. exit code is: {}'.format(res)
>   File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in 
> eq_
> raise AssertionError(msg or "%r != %r" % (a, b))
> AssertionError: Error: repoclosure failed. exit code is: 256



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1282) repoclosure is failed on gdeploy

[Pavel Zhukov (oVirt JIRA)]

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

Pavel Zhukov reassigned OVIRT-1282:
---

Assignee: Daniel Belenky  (was: infra)

> repoclosure is failed on gdeploy
> 
>
> Key: OVIRT-1282
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1282
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Pavel Zhukov
>Assignee: Daniel Belenky
>Priority: Highest
>
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066
> 14:18:36 [basic_suit_el7] Repos looked at: 10
> 14:18:36 [basic_suit_el7]centos-base-el7
> 14:18:36 [basic_suit_el7]centos-extras-el7
> 14:18:36 [basic_suit_el7]centos-opstools-testing-el7
> 14:18:36 [basic_suit_el7]centos-ovirt-4.0-el7
> 14:18:36 [basic_suit_el7]centos-updates-el7
> 14:18:36 [basic_suit_el7]epel-el7
> 14:18:36 [basic_suit_el7]glusterfs-3.10-el7
> 14:18:36 [basic_suit_el7]internal_repo
> 14:18:36 [basic_suit_el7]ovirt-master-snapshot-static-el7
> 14:18:36 [basic_suit_el7]ovirt-master-tested-el7
> 14:18:36 [basic_suit_el7] Num Packages in Repos: 38045
> 14:18:36 [basic_suit_el7] package: 
> ovirt-release-host-node-4.2.0-0.3.master.2017032835.git67870d2.el7.centos.noarch
>  from internal_repo
> 14:18:36 [basic_suit_el7]   unresolved deps: 
> 14:18:36 [basic_suit_el7]  gdeploy



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6070 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6070/,
Build Number: 6070,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6069 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6069/,
Build Number: 6069,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-03-2017 ] [ repoclosure ]

[Pavel Zhukov]

Hi,

Newly introduced repoclosure test is failed [1] on gdeploy package
(GlusterFS) [2]

As we hadn't run this test before the only suspected patch is the patch
to add the test itself:
959e735c1c02a74c209fffc03d76f67ccf86606e ost: added repo closure test

[1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066/

[2]

14:18:36 [basic_suit_el7] Repos looked at: 10
14:18:36 [basic_suit_el7]centos-base-el7
14:18:36 [basic_suit_el7]centos-extras-el7
14:18:36 [basic_suit_el7]centos-opstools-testing-el7
14:18:36 [basic_suit_el7]centos-ovirt-4.0-el7
14:18:36 [basic_suit_el7]centos-updates-el7
14:18:36 [basic_suit_el7]epel-el7
14:18:36 [basic_suit_el7]glusterfs-3.10-el7
14:18:36 [basic_suit_el7]internal_repo
14:18:36 [basic_suit_el7]ovirt-master-snapshot-static-el7
14:18:36 [basic_suit_el7]ovirt-master-tested-el7
14:18:36 [basic_suit_el7] Num Packages in Repos: 38045
14:18:36 [basic_suit_el7] package: 
ovirt-release-host-node-4.2.0-0.3.master.2017032835.git67870d2.el7.centos.noarch
 from internal_repo
14:18:36 [basic_suit_el7]   unresolved deps: 
14:18:36 [basic_suit_el7]  gdeploy

-- 
Pavel Zhukov

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1283) Repoclosure test output should be more verbose

[Pavel Zhukov (oVirt JIRA)]

Pavel Zhukov created OVIRT-1283:
---

 Summary: Repoclosure test output should be more verbose
 Key: OVIRT-1283
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1283
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Pavel Zhukov
Assignee: infra
Priority: High


In current implementation it's not telling too much about the failure itself:

Error Message

Error: repoclosure failed. exit code is: 256
Stacktrace

Traceback (most recent call last):
  File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
  File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in 
wrapped_test
test()
  File 
"/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/000_check_repo_closure.py",
 line 95, in check_repo_closure
res, 0, 'Error: repoclosure failed. exit code is: {}'.format(res)
  File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in eq_
raise AssertionError(msg or "%r != %r" % (a, b))
AssertionError: Error: repoclosure failed. exit code is: 256



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1282) repoclosure is failed on gdeploy

[Pavel Zhukov (oVirt JIRA)]

Pavel Zhukov created OVIRT-1282:
---

 Summary: repoclosure is failed on gdeploy
 Key: OVIRT-1282
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1282
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Pavel Zhukov
Assignee: infra
Priority: Highest


http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066


14:18:36 [basic_suit_el7] Repos looked at: 10
14:18:36 [basic_suit_el7]centos-base-el7
14:18:36 [basic_suit_el7]centos-extras-el7
14:18:36 [basic_suit_el7]centos-opstools-testing-el7
14:18:36 [basic_suit_el7]centos-ovirt-4.0-el7
14:18:36 [basic_suit_el7]centos-updates-el7
14:18:36 [basic_suit_el7]epel-el7
14:18:36 [basic_suit_el7]glusterfs-3.10-el7
14:18:36 [basic_suit_el7]internal_repo
14:18:36 [basic_suit_el7]ovirt-master-snapshot-static-el7
14:18:36 [basic_suit_el7]ovirt-master-tested-el7
14:18:36 [basic_suit_el7] Num Packages in Repos: 38045
14:18:36 [basic_suit_el7] package: 
ovirt-release-host-node-4.2.0-0.3.master.2017032835.git67870d2.el7.centos.noarch
 from internal_repo
14:18:36 [basic_suit_el7]   unresolved deps: 
14:18:36 [basic_suit_el7]  gdeploy



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

jenkins dev role for mlipchuk user

[Maor Lipchuk]

Hi,

Can you please add dev role to mlipchuk user so I can run the ci manual
tests

Thanks,
Maor
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6068 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6068/,
Build Number: 6068,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-1281:
-
Epic Link: OVIRT-403

> Add 'patch owner' feature to Gerrit 
> 
>
> Key: OVIRT-1281
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> Details still TBD, but we want to check if there is a way for the patch 
> author who is the patch 'owner' or 'maintainer' and has the responsibility to 
> make sure the patch is reviewed in time and pushed and not left behind. 
> It might be Gerrit doesn't support such feature, but we'll check.
> [~oourf...@redhat.com][~ykaul][~danken] please add more info as needed.



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit

[eyal edri [Administrator] (oVirt JIRA)]

eyal edri [Administrator] created OVIRT-1281:


 Summary: Add 'patch owner' feature to Gerrit 
 Key: OVIRT-1281
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: eyal edri [Administrator]
Assignee: infra


Details still TBD, but we want to check if there is a way for the patch author 
who is the patch 'owner' or 'maintainer' and has the responsibility to make 
sure the patch is reviewed in time and pushed and not left behind. 

It might be Gerrit doesn't support such feature, but we'll check.


[~oourf...@redhat.com][~ykaul][~danken] please add more info as needed.



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6067 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6067/,
Build Number: 6067,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : deploy-to-ovirt_experimental_master #14335

[jenkins]

See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6066 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066/,
Build Number: 6066,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: deploy-to-ovirt_experimental_master #14334

[jenkins]

See 


--
[...truncated 32.62 KB...]
2017-03-28 
14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 
14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking 
if changes#detail is an iso
2017-03-28 
14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:170::  It is not
2017-03-28 

[oVirt Jenkins] ovirt_3.6_he-system-tests - Build # 891 - Fixed!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ 
Build: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/891/
Build Number: 891
Build Status:  Fixed
Triggered By: Started by user Lev Veyde

-
Changes Since Last Success:
-
Changes for Build #890
[Yaniv Bronhaim] Vdsm introduced abrt integration which requires additional 
rpms in

[Sandro Bonazzola] ovirt-engine-sdk: drop fc24 on master

[Sandro Bonazzola] ovirt-guest-agent: drop fc24 on master

[Pavel Zhukov] Revert "Use webhooks instead of polling"

[Eyal Edri] adding hyper converged storage system tests jobs


Changes for Build #891
[Yaniv Bronhaim] Vdsm introduced abrt integration which requires additional 
rpms in




-
Failed Tests:
-
All tests passed 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change in barak-test[master]: Just a dummy change for testing

[review]

>From Barak Korren :

Barak Korren has posted comments on this change.

Change subject: Just a dummy change for testing
..


Patch Set 2:

testing mc'testing!!!

-- 
To view, visit https://gerrit-staging.phx.ovirt.org/4
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5
Gerrit-PatchSet: 2
Gerrit-Project: barak-test
Gerrit-Branch: master
Gerrit-Owner: Barak Korren 
Gerrit-Reviewer: Barak Korren 
Gerrit-Reviewer: Jenkins CI 
Gerrit-HasComments: No
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: resources.ovirt.org directory layout is a mess

[Barak Korren]

On 28 March 2017 at 14:21, Sandro Bonazzola  wrote:

>
>
> On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri  wrote:
>
>> Hi,
>>
>> On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak  wrote:
>>
>>> Hi,
>>>
>>> I just noticed we have couple of different places for the same kind of
>>> content (packages):
>>>
>>> /pub/ - includes new releases and snapshots repos
>>>
>>
>> This is the official place for oVirt releases and what any user should
>> use.
>> The official repositories
>>
>>
>>> /repos/ovirt/{experimental,tested}/ - experimental seems pretty close
>>> to snapshots
>>>
>>
>> Experimental - internal repo for CI, no one should use it.
>> Tested - official verified repos with packages that passed OST, we
>> recommend anyone to use that repo if he wants latest and greatest packages
>> and can't wait to an official release
>>
>
> If it's now official, please move it to /pub. /repos is not meant to be
> used for official public content. /repos was meant to host internal,
> development, temporary, backup repos.
>

I guess the description Eyal gave was misleading. The "official" cutting
edge releases were and remain in the nightly "snapshot" repos under "/pub".
"tested" is for use by processes that cannot wait for the nightly
publishing job and needs the latest stuff that passed OST (This means most
CI processes, but probably not user processes).

-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: resources.ovirt.org directory layout is a mess

[Sandro Bonazzola]

On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri  wrote:

> Hi,
>
> On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak  wrote:
>
>> Hi,
>>
>> I just noticed we have couple of different places for the same kind of
>> content (packages):
>>
>> /pub/ - includes new releases and snapshots repos
>>
>
> This is the official place for oVirt releases and what any user should use.
> The official repositories
>
>
>> /repos/ovirt/{experimental,tested}/ - experimental seems pretty close
>> to snapshots
>>
>
> Experimental - internal repo for CI, no one should use it.
> Tested - official verified repos with packages that passed OST, we
> recommend anyone to use that repo if he wants latest and greatest packages
> and can't wait to an official release
>

If it's now official, please move it to /pub. /repos is not meant to be
used for official public content. /repos was meant to host internal,
development, temporary, backup repos.



> Snapshots - from next week, ovirt-snapshot-master will be a nightly
> snapshot of tested repo, this is ideal for QE or anyone who wants to test
> oVirt, but can't have the repo refreshed all the time.
>
>
>> /releases - old releases
>>
>
> We don't maintain this, probably kept for history purposes
>
>
>>
>> The /repos prefix by itself is incredibly messy, there are bunch of
>> private directories and ovirt among them.
>>
>
> Please open a ticket on jira.ovirt.org with details and we'll look into
> it, but I don't think that each directory on a release server should matter.
> There is official documentation for oVirt users and release rpms which
> provides you with exactly which repos you should use.
>
> We do need to add documentation on what each repo means and its usage, can
> you please open a ticket on it so we won't forget?
>
>
>>
>> Can you please unify the structure so it is easier to navigate? We
>> should at least have one top level dir for all official public
>>
>
>
>
>> content.
>>
>> Something like
>>
>> /ovirt/{releases,experimental,tested}//
>>
>> and
>>
>> /ovirt/yum-repos/release.rpm
>>
>>  would work well enough I think.
>>
>> Thanks
>>
>> Martin
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
>
> Eyal edri
>
>
> ASSOCIATE MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>



-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

TRIED. TESTED. TRUSTED. 
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: resources.ovirt.org directory layout is a mess

[Barak Korren]

On 28 March 2017 at 12:46, Martin Sivak  wrote:

>
> I have to be able to find all of them (including the tested directory)
> when I am checking which package version is available for OST for example.
> Nothing there is CI only, developers need all of them when bug is found by
> those systems and investigation is needed.
>
> Guys, we need to know how CI works, what packages it consumes and how we
> can reproduce a test to be able to solve bugs found by CI.
>


This is a different request, and has nothing to do with the structure of
resources.ovirt.org. The experimental flow can and does take packages
directly from build artifacts jobs. It uses the 'repos/ovirt' directory as
a composition space but that is just an aspect of the current
implementation and will change. I agree we can do a better job of
documenting how the experimental flow works.

I'm afraid the way the flow works currently does not allow for easy exact
repoduction because the exact tested composition only exists in
'latest.under_test' for the duration of the test (Its not hard to tell
which packages were tested mind you, but building a usable repo with those
exact packages will take some work). But this is indeed something we might
look at as a future tooling design goal.

I think that for most practical purposes, you probably don't need 100%
exact reproduction. Running the manual OST job against the 'tested' repo
(This is the default configuration for 'master' and can be selected for
other releases), or running it locally, while adding a few extra packages
via direct URLs in the extra_sources file probably allows reproducing most
issues.

-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David commented on OVIRT-1113:
-

[~bkor...@redhat.com] No, the doc isn't up to date.
* From a small brief reading, the permission and the hook sections require an 
update.
* There is a task to update the docs

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6059 - SUCCESS!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6059/,
Build Number: 6059,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: resources.ovirt.org directory layout is a mess

[Martin Sivak]

I have to be able to find all of them (including the tested directory) when
I am checking which package version is available for OST for example.
Nothing there is CI only, developers need all of them when bug is found by
those systems and investigation is needed.

Guys, we need to know how CI works, what packages it consumes and how we
can reproduce a test to be able to solve bugs found by CI.

Martin


On Tue, Mar 28, 2017 at 11:32 AM, Eyal Edri  wrote:

> Hi,
>
> On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak  wrote:
>
>> Hi,
>>
>> I just noticed we have couple of different places for the same kind of
>> content (packages):
>>
>> /pub/ - includes new releases and snapshots repos
>>
>
> This is the official place for oVirt releases and what any user should use.
> The official repositories
>
>
>> /repos/ovirt/{experimental,tested}/ - experimental seems pretty close
>> to snapshots
>>
>
> Experimental - internal repo for CI, no one should use it.
> Tested - official verified repos with packages that passed OST, we
> recommend anyone to use that repo if he wants latest and greatest packages
> and can't wait to an official release
> Snapshots - from next week, ovirt-snapshot-master will be a nightly
> snapshot of tested repo, this is ideal for QE or anyone who wants to test
> oVirt, but can't have the repo refreshed all the time.
>
>
>> /releases - old releases
>>
>
> We don't maintain this, probably kept for history purposes
>
>
>>
>> The /repos prefix by itself is incredibly messy, there are bunch of
>> private directories and ovirt among them.
>>
>
> Please open a ticket on jira.ovirt.org with details and we'll look into
> it, but I don't think that each directory on a release server should matter.
> There is official documentation for oVirt users and release rpms which
> provides you with exactly which repos you should use.
>
> We do need to add documentation on what each repo means and its usage, can
> you please open a ticket on it so we won't forget?
>
>
>>
>> Can you please unify the structure so it is easier to navigate? We
>> should at least have one top level dir for all official public
>>
>
>
>
>> content.
>>
>> Something like
>>
>> /ovirt/{releases,experimental,tested}//
>>
>> and
>>
>> /ovirt/yum-repos/release.rpm
>>
>>  would work well enough I think.
>>
>> Thanks
>>
>> Martin
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
>
> Eyal edri
>
>
> ASSOCIATE MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: resources.ovirt.org directory layout is a mess

[Eyal Edri]

Hi,

On Tue, Mar 28, 2017 at 12:15 PM, Martin Sivak  wrote:

> Hi,
>
> I just noticed we have couple of different places for the same kind of
> content (packages):
>
> /pub/ - includes new releases and snapshots repos
>

This is the official place for oVirt releases and what any user should use.
The official repositories


> /repos/ovirt/{experimental,tested}/ - experimental seems pretty close
> to snapshots
>

Experimental - internal repo for CI, no one should use it.
Tested - official verified repos with packages that passed OST, we
recommend anyone to use that repo if he wants latest and greatest packages
and can't wait to an official release
Snapshots - from next week, ovirt-snapshot-master will be a nightly
snapshot of tested repo, this is ideal for QE or anyone who wants to test
oVirt, but can't have the repo refreshed all the time.


> /releases - old releases
>

We don't maintain this, probably kept for history purposes


>
> The /repos prefix by itself is incredibly messy, there are bunch of
> private directories and ovirt among them.
>

Please open a ticket on jira.ovirt.org with details and we'll look into it,
but I don't think that each directory on a release server should matter.
There is official documentation for oVirt users and release rpms which
provides you with exactly which repos you should use.

We do need to add documentation on what each repo means and its usage, can
you please open a ticket on it so we won't forget?


>
> Can you please unify the structure so it is easier to navigate? We
> should at least have one top level dir for all official public
>



> content.
>
> Something like
>
> /ovirt/{releases,experimental,tested}//
>
> and
>
> /ovirt/yum-repos/release.rpm
>
>  would work well enough I think.
>
> Thanks
>
> Martin
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>



-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


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

Re: resources.ovirt.org directory layout is a mess

[Barak Korren]

On 28 March 2017 at 12:15, Martin Sivak  wrote:
>
> Can you please unify the structure so it is easier to navigate? We
> should at least have one top level dir for all official public
> content.

'/pub' is that place.

'/repos/ovirt/tested' should only concern you if you want to write
jobs that need to pull in post-OST dependencies. I guess we could do a
better job of documenting which repo to use when.

'/repos/ovirt/experimental' should only ever be used by stuff that is
running within the experimental flow. If you see anything that links
to it directly its a bug.

I do agree we probably need to clean older unused stuff from '/repos'.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6058 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6058/,
Build Number: 6058,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

resources.ovirt.org directory layout is a mess

[Martin Sivak]

Hi,

I just noticed we have couple of different places for the same kind of
content (packages):

/pub/ - includes new releases and snapshots repos
/repos/ovirt/{experimental,tested}/ - experimental seems pretty close
to snapshots
/releases - old releases

The /repos prefix by itself is incredibly messy, there are bunch of
private directories and ovirt among them.

Can you please unify the structure so it is easier to navigate? We
should at least have one top level dir for all official public
content.

Something like

/ovirt/{releases,experimental,tested}//

and

/ovirt/yum-repos/release.rpm

 would work well enough I think.

Thanks

Martin
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt_3.6_he-system-tests - Build # 890 - Failure!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ 
Build: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/890/
Build Number: 890
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #890
[Yaniv Bronhaim] Vdsm introduced abrt integration which requires additional 
rpms in

[Sandro Bonazzola] ovirt-engine-sdk: drop fc24 on master

[Sandro Bonazzola] ovirt-guest-agent: drop fc24 on master

[Pavel Zhukov] Revert "Use webhooks instead of polling"

[Eyal Edri] adding hyper converged storage system tests jobs




-
Failed Tests:
-
No tests ran. 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #195

[jenkins]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
 > git --version # timeout=10
 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 395700ab9bea6237d521543aa1b88620d106d71b (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 395700ab9bea6237d521543aa1b88620d106d71b
 > git rev-list 395700ab9bea6237d521543aa1b88620d106d71b # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe 
/tmp/hudson8893048609426993807.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 
jenkins/data/mirrors-reposync.conf

Checking if mirror needs a resync
Traceback (most recent call last):
  File "/usr/bin/reposync", line 343, in 
main()
  File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 687, in 
doRepoSetup
return self._getRepos(thisrepo, True)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, in 
_getRepos
self._repos.doSetup(thisrepo)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in 
retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1451, in 
_commonLoadRepoXML
if self._latestRepoXML(local):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in 
_latestRepoXML
repomd = self.metalink_data.repomd
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in 
metalink_data = property(fget=lambda self: self._getMetalink(),
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, in 
_getMetalink
shutil.move(result, self.metalink_filename)
  File "/usr/lib64/python2.7/shutil.py", line 301, in move
copy2(src, real_dst)
  File "/usr/lib64/python2.7/shutil.py", line 130, in copy2
copyfile(src, dst)
  File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: 
'/home/jenkins/mirrors_cache/fedora-base-fc25/metalink.xml.tmp'
Build step 'Execute shell' marked build as failure
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 32 [7] failed system tests

[oVirt Jenkins]

Change 32 [7] is probably the reason behind recent system test failures in the
"numbers" 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:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/32/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 32 [7] queued for testing

[oVirt Jenkins]

Change 32 [7] was successfully added into the "numbers" queue for testing.
Further messages will be sent when test results are available.

For further details about the change see:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/32/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 31 [6] passed system tests

[oVirt Jenkins]

Change 31 [6] successfully passed the system tests invoked from the "numbers"
queue.

For further details about the change see:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/31/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 31 [6] queued for testing

[oVirt Jenkins]

Change 31 [6] was successfully added into the "numbers" queue for testing.
Further messages will be sent when test results are available.

For further details about the change see:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/31/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 30 [2] passed system tests

[oVirt Jenkins]

Change 30 [2] successfully passed the system tests invoked from the "numbers"
queue.

For further details about the change see:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/30/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Change 30 [2] queued for testing

[oVirt Jenkins]

Change 30 [2] was successfully added into the "numbers" queue for testing.
Further messages will be sent when test results are available.

For further details about the change see:
http://jenkins-staging.phx.ovirt.org/job/numbers_builder/30/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-1113:
-

Here is the existing doc about creating repos:

http://ovirt-infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects/index.html

[~sbend...@redhat.com], [~ederevea] is that doc up to date?

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[vishnu.srkmr (oVirt JIRA)]

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

vishnu.srkmr commented on OVIRT-1113:
-

Can you please add the link to the documentation too?

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
This message was sent by Atlassian JIRA
(v1000.844.2#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra