May 2021 - Infra - oVirt List Archives

[CQ]: 114369, 19 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '21

15 May '21

A system test invoked by the "ovirt-master" change queue including change 114369,19 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114369/19 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29700/

1 0

[CQ]: 114806, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '21

15 May '21

A system test invoked by the "ovirt-master" change queue including change 114806,2 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114806/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29698/

1 0

oVirt infra daily report - unstable production jobs - 1556
by jenkins＠jenkins.phx.ovirt.org 15 May '21

15 May '21

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1556//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 114725, 11 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '21

14 May '21

A system test invoked by the "ovirt-master" change queue including change 114725,11 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114725/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29696/

1 0

[CQ]: 114657, 13 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '21

14 May '21

A system test invoked by the "ovirt-master" change queue including change 114657,13 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114657/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29692/

1 0

[CQ]: 114808, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests
by oVirt Jenkins 14 May '21

14 May '21

Change 114808,1 (ovirt-node-ng-image) 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/ovirt-node-ng-image/+/#/c/114808/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29691/

1 0

[CQ]: 114727, 13 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '21

14 May '21

A system test invoked by the "ovirt-master" change queue including change 114727,13 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114727/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29687/

1 0

[CQ]: 114807, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '21

14 May '21

A system test invoked by the "ovirt-master" change queue including change 114807,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114807/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29686/

1 0

[CQ]: 114776, 8 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '21

14 May '21

A system test invoked by the "ovirt-master" change queue including change 114776,8 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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/ovirt-system-tests/+/#/c/114776/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/29684/

1 0

Note about Ansible httpd role design
by Marc Dequènes (Duck) 14 May '21

14 May '21

Quack, In the meeting you seem to be astonished the role does not handle rewrite rules and I wanted to comment on that. There are services like Apache or postfix which have a lot of directives, and sometimes to make things worse order matters. In this case it is simply not possible to maintain a solution that would be able to do just ANYTHING. If you added wrappers around these directives then you would have to maintain a lot of code that just bring nothing really to help you in your deployment. So the design of httpd that Misc originally created and was extended is the following: an opinionated way to setup the basics of a web server and vhost configuration, and a way to include extra custom config. Some often used features like redirects, reverse proxying etc are included but they simply cannot handle all possible customization. So what makes the design practical is that with the inclusion system you can add your own Apache rules and either complement what the role does (that's what we're doing for Jenkins) or simply replace it. With that in mind, you can easily extend the role features with companion roles. The httpd role sets important variables (remember _vhost_confdir and httpd_usergroup?) and you do not need to guess were to put files, what user to use for Apache, all is calculated for you depending on your vhost installation and OS too (the Apache user and systemd service name differ from OS to OS for eg.). This way we created roles for specific usage that complement httpd without conflicting: - httpd_php_fpm - httpd_wsgi (for Python) - httpd_passenger (originally for Ruby but Python and NodeJS are supported now) and you can add your own. So this role is old and things like variable names could be improved, the TLS method choice could be set in one practical variable instead of ~3, there's just no way to handle ports other than 80 and 443 at the moment, and do we need to be able to setup local .htpasswd password files nowadays? So it could still be improved but I think the foundation is solid. Anyway, suggestions are welcome :-). \_o<

1 0