[oVirt] [CQ weekly status] [04-10-2019]
by Dusan Fodor
Hi,
This mail is to provide the current status of CQ and allow people to
review status before and after the weekend.
Please refer to below colour map for further information on the meaning of
the colours.
*CQ-4.3*: GREEN (#1)
Last failure was on 03-10 caused by pipeline configuration, it was fixed
soon after.
*CQ-Master:* RED (#1)
Last failure was on 04-10 caused when vdsm failed building using bad
interpreter. Patch 103655 <https://gerrit.ovirt.org/103655> is pending to
fix this issue.
Current running jobs for 4.3 [1] and master [2] can be found here:
[1]
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change...
[2]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
Have a nice week!
Dusan
-------------------------------------------------------------------------------------------------------------------
COLOUR MAP
Green = job has been passing successfully
** green for more than 3 days may suggest we need a review of our test
coverage
1.
1-3 days GREEN (#1)
2.
4-7 days GREEN (#2)
3.
Over 7 days GREEN (#3)
Yellow = intermittent failures for different projects but no lasting or
current regressions
** intermittent would be a healthy project as we expect a number of
failures during the week
** I will not report any of the solved failures or regressions.
1.
Solved job failures YELLOW (#1)
2.
Solved regressions YELLOW (#2)
Red = job has been failing
** Active Failures. The colour will change based on the amount of time the
project/s has been broken. Only active regressions would be reported.
1.
1-3 days RED (#1)
2.
4-7 days RED (#2)
3.
Over 7 days RED (#3)
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)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/devel@ovirt.org/message/YCNCKRK3G4E...
5 years, 1 month
[JIRA] (OVIRT-2809) imageio not working in PHX
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2809?page=com.atlassian.jir... ]
Evgheni Dereveanchin commented on OVIRT-2809:
---------------------------------------------
The error in engine.log seems to point to a certificate mismatch when engine connects to the proxy:
2019-10-04 05:37:45,533-04 ERROR \[org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-48) \[b643d084-99fb-4105-86c9-1e87b60349b6] Failed to add image ticket to ovirt-imageio-proxy: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
The following software versions are currently installed:
ovirt-engine-4.3.5.4-1.el7.noarch
ovirt-imageio-proxy-1.5.1-0.el7.noarch
/etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf contains the standard values:
use_ssl = true
ssl_key_file = /etc/pki/ovirt-engine/keys/imageio-proxy.key.nopass
ssl_cert_file = /etc/pki/ovirt-engine/certs/imageio-proxy.cer
engine_cert_file = /etc/pki/ovirt-engine/certs/engine.cer
engine_ca_cert_file = /etc/pki/ovirt-engine/ca.pem
verify_certificate = true
On engine side, /etc/ovirt-engine/engine.conf.d/10-setup-pki.conf also looks standard:
ENGINE_PKI="/etc/pki/ovirt-engine"
ENGINE_PKI_CA="/etc/pki/ovirt-engine/ca.pem"
ENGINE_PKI_ENGINE_CERT="/etc/pki/ovirt-engine/certs/engine.cer"
ENGINE_PKI_TRUST_STORE="/etc/pki/ovirt-engine/.truststore"
ENGINE_PKI_ENGINE_STORE="/etc/pki/ovirt-engine/keys/engine.p12"
{{I also see that /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf has the following override:}}
{{ENGINE_HTTPS_PKI_TRUST_STORE="/etc/pki/java/cacerts"}}
We use Let’s Encrypt on the Apache front-end and this may be the reason as this step is described in the docs:
[https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL.html|h...]
[https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/...]
I did have a certificate mismatch on the proxy itself so configuring {{ssl_key_file and ssl_cert_file}} values according to the docs may help in this situation.
> imageio not working in PHX
> --------------------------
>
> Key: OVIRT-2809
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2809
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Evgheni Dereveanchin
> Assignee: infra
>
> I tried to import an image into the PHX oVirt instance and this fails with a "paused by system" message in UI. Logging a ticket to see if it's a bug in oVirt or a misconfiguration in our particular deployment
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100111)
5 years, 1 month
[JIRA] (OVIRT-2809) imageio not working in PHX
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2809:
-------------------------------------------
Summary: imageio not working in PHX
Key: OVIRT-2809
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2809
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra
I tried to import an image into the PHX oVirt instance and this fails with a "paused by system" message in UI. Logging a ticket to see if it's a bug in oVirt or a misconfiguration in our particular deployment
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100111)
5 years, 1 month