[JIRA] (OVIRT-1980) CI test never reported back to Gerrit?

Yaniv Kaul created OVIRT-1980: - Summary: CI test never reported back to Gerrit? Key: OVIRT-1980 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1980 Project: oVirt - virtualization made easy

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35926#comment-35926 ] Yaniv Kaul commented on OST-99: --- I think it'd be easier to start with running those tests from the Engine VM,

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas

Yaniv Kaul created OVIRT-1911: - Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1911: -- Epic Link: OVIRT-411 > RFE: Add relevant git commit messages as comments in the relevant Bugzillas >

[JIRA] (OVIRT-1910) Strange Lago CI test failure

Yaniv Kaul created OVIRT-1910: - Summary: Strange Lago CI test failure Key: OVIRT-1910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 Project: oVirt - virtualization made easy Issue

[JIRA] (OVIRT-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35608#comment-35608 ] Yaniv Kaul commented on OVIRT-1829: --- Ah, my mistake. We actually don't use HTTPS... Please close the

[JIRA] (OVIRT-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1829: -- Epic Link: OVIRT-403 > link in 'Build successful' message is showing 'http' and not 'https' (to >

[JIRA] (OVIRT-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)

Yaniv Kaul created OVIRT-1829: - Summary: link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins) Key: OVIRT-1829 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1829 Project:

[JIRA] (OVIRT-1763) Increase entropy for hosts

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35369#comment-35369 ] Yaniv Kaul commented on OVIRT-1763: --- [~dron] - the above looks like vm_run failed - took more than 3m. It

[JIRA] (OVIRT-1763) Increase entropy for hosts

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35341#comment-35341 ] Yaniv Kaul commented on OVIRT-1763: --- How? We have virtio-rng. What else would you like to add? rngd? >

[JIRA] (OVIRT-1509) Please upload CirrOS 0.3.5 to Glance

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1509: -- Epic Link: OVIRT-400 > Please upload CirrOS 0.3.5 to Glance > >

[JIRA] (OVIRT-1509) Please upload CirrOS 0.3.5 to Glance

Yaniv Kaul created OVIRT-1509: - Summary: Please upload CirrOS 0.3.5 to Glance Key: OVIRT-1509 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1509 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-1459) Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory

Yaniv Kaul created OVIRT-1459: - Summary: Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory Key: OVIRT-1459 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1459

[JIRA] (OVIRT-1459) Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1459: -- Epic Link: OVIRT-400 > Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file >

[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=30304#comment-30304 ] Yaniv Kaul commented on OVIRT-1367: --- [~eedri] - we are quite explicit taking 0.3.4 (downloading it from

[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org

Yaniv Kaul created OVIRT-1367: - Summary: Please add latest CirrOS to glance.ovirt.org Key: OVIRT-1367 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1367 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1367: -- Epic Link: OVIRT-400 > Please add latest CirrOS to glance.ovirt.org >

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29503#comment-29503 ] Yaniv Kaul commented on OVIRT-1295: --- I think we need to see how many of those we have - and how many have

[JIRA] (OVIRT-1195) Unexplained failure in CI job

Yaniv Kaul created OVIRT-1195: - Summary: Unexplained failure in CI job Key: OVIRT-1195 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1195 Project: oVirt - virtualization made easy Issue

[JIRA] (OVIRT-1195) Unexplained failure in CI job

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1195: -- Epic Link: OVIRT-400 > Unexplained failure in CI job > - > >

[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org

Yaniv Kaul created OVIRT-1164: - Summary: Remove most of the images from glance.ovirt.org Key: OVIRT-1164 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1164 Project: oVirt - virtualization made easy

[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1164: -- Epic Link: OVIRT-403 > Remove most of the images from glance.ovirt.org >

[JIRA] (OVIRT-1133) CI fails on "java.io.IOException: Remote call on ovirt-srv24.phx.ovirt.org failed"

Yaniv Kaul created OVIRT-1133: - Summary: CI fails on "java.io.IOException: Remote call on ovirt-srv24.phx.ovirt.org failed" Key: OVIRT-1133 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1133

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26430#comment-26430 ] Yaniv Kaul commented on OST-39: --- 0. I think it's time to understand if we want to use Lago for Kubevirt or not. I

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26428#comment-26428 ] Yaniv Kaul commented on OST-39: --- [~eedri] - too many items there, I think. We should probably document it in

[JIRA] (OVIRT-1048) Run OST against vdsm+Engine on kubernetes

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=26402#comment-26402 ] Yaniv Kaul commented on OVIRT-1048: --- [~eedri] - I strongly agree. I think lago has just gained good support

[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=25714#comment-25714 ] Yaniv Kaul commented on OVIRT-1028: --- Others

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=24228#comment-24228 ] Yaniv Kaul commented on OVIRT-933: -- Moving priority to High, based on 'will cause it to crash' statement

[JIRA] (OVIRT-933) Fix repoproxy service and logging mess

[ https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-933: - Priority: High (was: Medium) > Fix repoproxy service and logging mess >

[JIRA] (OVIRT-932) Wrong Lago version used in CI

Yaniv Kaul created OVIRT-932: Summary: Wrong Lago version used in CI Key: OVIRT-932 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 Project: oVirt - virtualization made easy Issue Type:

[JIRA] (OVIRT-932) Wrong Lago version used in CI

[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-932: - Epic Link: OVIRT-400 > Wrong Lago version used in CI > - > >

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23804#comment-23804 ] Yaniv Kaul commented on OVIRT-902: -- 1. I'm not sure if it's here or requires a different ticket, but this is

[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14210#comment-14210 ] Yaniv Kaul commented on OVIRT-459: -- Ideally, yes. I'd separate the test plan (which I hope QE would add a bit)

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=13907#comment-13907 ] Yaniv Kaul commented on OVIRT-95: - Theoretically, of course. Practically, I'm not sure Lago is ready yet for