[CQ]: 99295,1 (cockpit-ovirt) failed "ovirt-master" system tests
Change 99295,1 (cockpit-ovirt) 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/99295/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13784/ ___ 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/PEECCXRPSM7GQMFVQUDWSPUXORK5QZCM/
[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 540 - Still Failing!
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/540/ Build Number: 540 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #533 [Eitan Raviv] hostlib: report host mgmt net and its attachment data Changes for Build #534 [Eitan Raviv] hostlib: report host mgmt net and its attachment data Changes for Build #535 [Eitan Raviv] hostlib: report host mgmt net and its attachment data Changes for Build #536 [Eitan Raviv] hostlib: report host mgmt net and its attachment data Changes for Build #537 [Dominik Holler] basic-suite-master: Use 384MB memory for VM0 [Evgheni Dereveanchin] Make standard-manual-runner run concurrently Changes for Build #538 [Ales Musil] network-suite-master: Add test to for vnic profile live update Changes for Build #539 [Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update [Simone Tiraboschi] Add he-basic-role-remote Changes for Build #540 [Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update - Failed Tests: - 1 tests failed. FAILED: 002_bootstrap.get_host_hooks_42 Error Message: Fault reason is "Operation Failed". Fault detail is "Entity not found: null". HTTP response code is 404. Stack Trace: 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 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 1026, in get_host_hooks hooks = sorted(hooks_service.list(), key=lambda hook: hook.name) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 11608, in list return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error NotFoundError: Fault reason is "Operation Failed". Fault detail is "Entity not found: null". HTTP response code is 404.___ 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/SEEV7FTRO643I5T7OYXQFEP3THRF2ZVF/
[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 540 - Still Failing!
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/540/
Build Number: 540
Build Status: Still Failing
Triggered By: Started by timer
-
Changes Since Last Success:
-
Changes for Build #533
[Eitan Raviv] hostlib: report host mgmt net and its attachment data
Changes for Build #534
[Eitan Raviv] hostlib: report host mgmt net and its attachment data
Changes for Build #535
[Eitan Raviv] hostlib: report host mgmt net and its attachment data
Changes for Build #536
[Eitan Raviv] hostlib: report host mgmt net and its attachment data
Changes for Build #537
[Dominik Holler] basic-suite-master: Use 384MB memory for VM0
[Evgheni Dereveanchin] Make standard-manual-runner run concurrently
Changes for Build #538
[Ales Musil] network-suite-master: Add test to for vnic profile live update
Changes for Build #539
[Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update
[Simone Tiraboschi] Add he-basic-role-remote
Changes for Build #540
[Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update
-
Failed Tests:
-
1 tests failed.
FAILED: 002_bootstrap.add_secondary_storage_domains_41
Error Message:
Fault reason is "Operation Failed". Fault detail is "[Cannot attach Storage.
Storage Domain format V5 is illegal.]". HTTP response code is 409.
>> begin captured logging <<
lago.utils: DEBUG: Error while running thread Thread-624
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
_ret_via_queue
queue.put({'return': func()})
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 423, in add_nfs_storage_domain
add_generic_nfs_storage_domain(prefix, SD_NFS_NAME, SD_NFS_HOST_NAME,
SD_NFS_PATH, nfs_version='v4_2')
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 471, in add_generic_nfs_storage_domain
_add_storage_domain(api, p)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 405, in _add_storage_domain
id=sd.id,
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 3053,
in add
return self._internal_add(storage_domain, headers, query, wait)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in
_internal_add
return future.wait() if wait else future
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in
wait
return self._code(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229, in
callback
self._check_fault(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in
_check_fault
self._raise_error(response, body)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in
_raise_error
raise error
Error: Fault reason is "Operation Failed". Fault detail is "[Cannot attach
Storage. Storage Domain format V5 is illegal.]". HTTP response code is 409.
lago.utils: DEBUG: Error while running thread Thread-626
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
_ret_via_queue
queue.put({'return': func()})
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 429, in add_second_nfs_storage_domain
SD_NFS_HOST_NAME, SD_SECOND_NFS_PATH)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 471, in add_generic_nfs_storage_domain
_add_storage_domain(api, p)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py",
line 410, in _add_storage_domain
lambda: attached_sd_service.get().status ==
sdk4.types.StorageDomainStatus.ACTIVE
File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__
self.gen.throw(type, value, traceback)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/__init__.py",
line 264, in TestEvent
lambda:
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in
assert_true_within_long
assert_equals_within_long(func, True, allowed_exceptions)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in
assert_equals_within_long
func, value, LONG_TIMEOUT,
[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 37 - Failure!
Project:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/
Build:
http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/37/
Build Number: 37
Build Status: Failure
Triggered By: Started by timer
-
Changes Since Last Success:
-
Changes for Build #37
[Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update
-
Failed Tests:
-
1 tests failed.
FAILED: 002_bootstrap.add_master_storage_domain_43
Error Message:
Could not find hosts that are up in DC test-dc
>> begin captured logging <<
lago.ssh: DEBUG: start task:fd100137-78b8-4684-a36c-ee5b6c109bb5:Get ssh client
for lago-compat-4-3-suite-master-engine:
lago.ssh: DEBUG: end task:fd100137-78b8-4684-a36c-ee5b6c109bb5:Get ssh client
for lago-compat-4-3-suite-master-engine:
lago.ssh: DEBUG: Running 12753fbc on lago-compat-4-3-suite-master-engine: cat
/root/multipath.txt
lago.ssh: DEBUG: Command 12753fbc on lago-compat-4-3-suite-master-engine
returned with 0
lago.ssh: DEBUG: Command 12753fbc on lago-compat-4-3-suite-master-engine output:
36001405778220ec14d04b0395174222e
360014059d8f57abb7a5468c9a536db53
36001405a49f2415ca32471bb724578fb
36001405e613fb4abc1a4db19ad92c4f7
36001405eef65609f0c54ab78aab26f46
- >> end captured logging << -
Stack Trace:
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 142, in
wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in
wrapper
return func(get_test_prefix(), *args, **kwargs)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py",
line 417, in add_master_storage_domain
add_iscsi_storage_domain(prefix)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py",
line 561, in add_iscsi_storage_domain
host=_random_host_from_dc(api, DC_NAME),
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py",
line 122, in _random_host_from_dc
return _hosts_in_dc(api, dc_name, True)
File
"/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/002_bootstrap.py",
line 119, in _hosts_in_dc
raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name)
'Could not find hosts that are up in DC test-dc\n >> begin
captured logging << \nlago.ssh: DEBUG: start
task:fd100137-78b8-4684-a36c-ee5b6c109bb5:Get ssh client for
lago-compat-4-3-suite-master-engine:\nlago.ssh: DEBUG: end
task:fd100137-78b8-4684-a36c-ee5b6c109bb5:Get ssh client for
lago-compat-4-3-suite-master-engine:\nlago.ssh: DEBUG: Running 12753fbc on
lago-compat-4-3-suite-master-engine: cat /root/multipath.txt\nlago.ssh: DEBUG:
Command 12753fbc on lago-compat-4-3-suite-master-engine returned with
0\nlago.ssh: DEBUG: Command 12753fbc on lago-compat-4-3-suite-master-engine
output:\n
36001405778220ec14d04b0395174222e\n360014059d8f57abb7a5468c9a536db53\n36001405a49f2415ca32471bb724578fb\n36001405e613fb4abc1a4db19ad92c4f7\n36001405eef65609f0c54ab78aab26f46\n\n-
>> end captured logging << -'___
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/L6KBT7GSA5VO2GVBD2L5BWXINOO4B64H/
oVirt infra daily report - unstable production jobs - 791
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/791//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins RHEVM CI Jenkins Daily Report - 10/04/2019 00 Unstable Critical ovirt-appliance_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-node-ng_4.2_build-artifacts-el7-x86_64 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_ansible-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_compat-4.1-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_compat-4.2-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_hc-basic-suite-4.3 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_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-ansible-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-ansible-suite-4.3 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-role-remote-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-role-remote-suite-4.3 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-role-remote-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_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]: bc61fb2 (v2v-conversion-host) failed "ovirt-4.3" system tests
Change bc61fb2 (v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/bc61fb287ba4a9ddae10e56a589108da89607f5a For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/640/ ___ 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/BVIRPGLOVJN3UW34QKOSMUCYCKWZQRLP/
[CQ]: bc61fb2 (v2v-conversion-host) failed "ovirt-master" system tests
Change bc61fb2 (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/bc61fb287ba4a9ddae10e56a589108da89607f5a For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13780/ ___ 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/KARF3GHJLMUVO4Q7KMJ4AU3OINLFAWYY/
[CQ]: 6942b0e (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
Change 6942b0e (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.3" 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-hosted-engine-setup/commit/6942b0e8039b3d7a853ddd0c23430f4559275c98 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/639/ ___ 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/KNLUMN6KPV36JFN7RZ3BWASA4CLG74PF/
[CQ]: 99301,3 (ovirt-engine) failed "ovirt-4.3" system tests
Change 99301,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99301/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/635/ ___ 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/IA43U7GCQS33TJZLAGOJGTNPJQYDEIRN/
[CQ]: 99196,5 (vdsm) failed "ovirt-master" system tests
Change 99196,5 (vdsm) 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/99196/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13777/ ___ 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/H56BG7VUIEM4F2I53YSBNN32JBILR2OA/
[CQ]: 99284,1 (ovirt-release) failed "ovirt-4.3" system tests
Change 99284,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99284/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/632/ ___ 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/2COHZDX55ZE2YI52UBQY5HTF7QORSBV4/
[CQ]: 99194,2 (vdsm) failed "ovirt-master" system tests
Change 99194,2 (vdsm) 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/99194/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13773/ ___ 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/SKGFDYKX3OV3T3P33HWEGQSWNVYZLMRU/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39242#comment-39242 ] Barak Korren commented on OVIRT-2714: - [~eedri] we can probably move the manual job to use containers if we didn't already, that aught to let it have more executors aviabale. [~gbenh...@redhat.com], [~dbele...@redhat.com] WDYT? [~mskrivanek] please note that moving into containers will have about 30% impact on the job performance, so we're paying in latency for greater throughput... > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7G2AITZEUUU36BMB2ZE7DCOMSG5K2X7Z/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39240#comment-39240 ] Eyal Edri commented on OVIRT-2714: -- We have 5 servers, which are shared between CQ, OST check-patch and nightly OST Jobs. so not so much. Is running OST Manually is an option? you can run the same way it run on the manual job. If we see it's not enough, maybe we consider paying for renting external bare metals, or we can also look into moving another server to run inside OpenShift to run more load as I've asked [~gbenh...@redhat.com] and [~dbele...@redhat.com], same as KubeVirt runs. Why do you think it's not available? as I said, its probably being taken by CQ or OST check-patch... eventually we have a limited amount of hosts, so i'm not sure there are ideal hosts > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QAB2TYAH7NZPZNGKW4TXZEGQWLSMSE3I/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39239#comment-39239 ] Michal Skrivanek commented on OVIRT-2714: - I see. So how many we have? One? Can it be shared with other hosts? And even if we have just one right now - why is it not available? It's happening relatively frequently (roughly once in two weeks from what I've seen) > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WWVYAEIH7TGLZ5VHUOSKI7JNNCPHXWO6/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39238#comment-39238
]
Eyal Edri commented on OVIRT-2714:
--
The manual job has already 10 available executors:
job-template:
name: '{project}_manual'
project: '{project}'
concurrent: true
properties:
- build-discarder:
days-to-keep: 14
- throttle:
enabled: true
option: project
max-total: 10
The fact that jobs are waiting in queue means there aren't enough hosts to run
the tests, something that isn't easily solvable without buying new hardware or
perhaps moving the manual job to run on containers instead of single bare
metals servers.
[~gbenh...@redhat.com][~dbele...@redhat.com] how much time will it take to move
the manual OST Job to run on containers, something that might help here?
> Increase limits on concurrent
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
> Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3UV4ZNV4LWGQA6L7S7RFWOXEGMPTNUOY/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39235#comment-39235 ] Michal Skrivanek edited comment on OVIRT-2714 at 4/10/19 10:04 AM: --- the intent of the original ticket to solve manual OST, but it only solves building artifacts. e still need more concurrent (or at least 1!!!) worker for the actual OST run was (Author: mskrivanek): actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RZTDRLKV7Z5AYRVZJ4JRNV2NV4FW73DG/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Skrivanek updated OVIRT-2714: Status: To Do (was: In Progress) > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/AZCPC4C3DPKOQ7QQTOJOM4NOCDNPDNJM/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Skrivanek reopened OVIRT-2714: - > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KHURQNNWCKDQPMFJQN754IZKSCAAV5PN/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Skrivanek updated OVIRT-2714: Resolution: Duplicate Status: Done (was: To Do) > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZHIC35OHM6H3K5UQW6K4JJ2SX7L44ZND/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39235#comment-39235 ] Michal Skrivanek commented on OVIRT-2714: - actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/I6MF3HZUUEV6IQZLRAQS4M7MLMJ2EOLX/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Skrivanek updated OVIRT-2714: Description: This one is about manual OST runs cloned from OVIRT-2704 --- We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir was: We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YVSCMG4TACN46POLROMWFC3H3V6IZMPZ/
[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Skrivanek updated OVIRT-2714: Summary: Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs (was: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs) > Increase limits on concurrent > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > --- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Michal Skrivanek >Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JELRMFACHVTB6RTUNZJFCL3ZBZ73L2KA/
[JIRA] (OVIRT-2714) CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
Michal Skrivanek created OVIRT-2714: --- Summary: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs Key: OVIRT-2714 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YF4CWIJQTWP6R2PGSWOGBQ44CWGNDZEQ/
[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-2713: --- Assignee: Evgheni Dereveanchin (was: infra) > Package does not match intended download on PHX mirror > -- > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: Evgheni Dereveanchin >Assignee: Evgheni Dereveanchin > > I was working on updating some nodes and hit an issue that was reported > before in CI. Basically, a package fails to install when running "yum update" > with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve > Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: > run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of > metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/F3N72IB2NEIZ6QE5QTRMMT7XQ5FE64OT/
[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39228#comment-39228 ] Evgheni Dereveanchin commented on OVIRT-2713: - The exact URL that fails is: http://mirrors.phx.ovirt.org/repos/yum/centos-updates-el7/base/Packages/polkit-0.112-18.el7_6.1.x86_64.rpm Downloading this file produces an md5sum of 79c1fa6804307bfc54833c880743c358 which matches the file from an upstream mirror: http://mirror.centos.org/centos/7/updates/x86_64/Packages/polkit-0.112-18.el7_6.1.x86_64.rpm Running "rpm -Uvh" on the downloaded RPM does not produce any warnings either so it is intact. > Package does not match intended download on PHX mirror > -- > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: Evgheni Dereveanchin >Assignee: infra > > I was working on updating some nodes and hit an issue that was reported > before in CI. Basically, a package fails to install when running "yum update" > with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve > Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: > run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of > metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SOHJCEZHCAWVSP2FMHHK6GV7UC7HXGA3/
[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
Evgheni Dereveanchin created OVIRT-2713: --- Summary: Package does not match intended download on PHX mirror Key: OVIRT-2713 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: Error downloading packages: polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DEXKBE7C3NZI5PVOMVHTCVOCIYCERC3N/
[JENKINS] Failed to setup proejct vdsm_standard-check-patch
Failed to run project_setup.sh for: #4674 vdsm [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 vm0042.workers-phx.ovirt.org.___ 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/BQVMKM7OKARSMEVDCBFYQO57STEL2ONG/
[CQ]: 98922, 8 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-4.3" change queue including change 98922,8 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 99237,2 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 99237,2 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98922/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99237/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/623/ ___ 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/K4LWRFCGQPEERB6LOCYWRUDJQ5DFORUE/
[CQ]: 98922, 8 (ovirt-provider-ovn) failed "ovirt-master" system tests
Change 98922,8 (ovirt-provider-ovn) 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/98922/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13770/ ___ 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/B5JMIASZXIWMWGGLZDOMHQQOWDHBLBIT/
