- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 384 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '18

24 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 384 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #384 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2237) Fail to run ovirt-engine on Fedora 28
by Eyal Edri (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2237?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2237: ---------------------------------- cc [~mwperina] maybe we need a new wildfly build? > Fail to run ovirt-engine on Fedora 28 > ------------------------------------- > > Key: OVIRT-2237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2237 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > ovirt-engine Failed to start on Fedora 28 due to missing Java module `nimbus-jose-jwt.jar` > {code:java} > "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => [ > "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", > "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" > ], > "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] > } > } > {code} > {code:java} > Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'nimbus-jose-jwt.jar' at path 'nimbus-jose-jwt.jar' (position: END_TAG seen ...<resources>\n <resource-root path="nimbus-jose-jwt.jar"/>... @6:48) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/common/com/nimbusds/main/nimbus-jose-jwt.jar (No such file or directory) > {code} > For the full `server.log`: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2237) Fail to run ovirt-engine on Fedora 28
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2237?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2237: ------------------------------------- [~sbonazzo(a)redhat.com] Does it relate to your change (e4b87cc1194e7c362fedb191d0dac207b4913f5b) in ovirt-engine? > Fail to run ovirt-engine on Fedora 28 > ------------------------------------- > > Key: OVIRT-2237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2237 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > ovirt-engine Failed to start on Fedora 28 due to missing Java module `nimbus-jose-jwt.jar` > {code:java} > "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => [ > "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", > "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" > ], > "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] > } > } > {code} > {code:java} > Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'nimbus-jose-jwt.jar' at path 'nimbus-jose-jwt.jar' (position: END_TAG seen ...<resources>\n <resource-root path="nimbus-jose-jwt.jar"/>... @6:48) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/common/com/nimbusds/main/nimbus-jose-jwt.jar (No such file or directory) > {code} > For the full `server.log`: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2237) Fail to run ovirt-engine on Fedora 28
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2237?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2237: -------------------------------- Description: "ovirt-engine Failed to start on Fedora 28 due to missing Java module `nimbus-jose-jwt.jar`\r\n\r\n\r\n{code:java}\r\n \"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available.\" => {\r\n \"Services that were unable to start:\" => [\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"bll.jar\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"docs.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"enginesso.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"root.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"services.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"webadmin.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.subunit.\\\"engine.ear\\\".\\\"welcome.war\\\".FIRST_MODULE_USE\",\r\n \"jboss.deployment.unit.\\\"engine.ear\\\".FIRST_MODULE_USE\"\r\n ],\r\n \"Services that may be the cause:\" => [\"jboss.naming.context.java.global.engine.bll.\\\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\\\"\"]\r\n }\r\n}\r\n{code}\r\n\r\n\r\n{code:java}\r\nCaused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'nimbus-jose-jwt.jar' at path 'nimbus-jose-jwt.jar' (position: END_TAG seen ...<resources>\\n <resource-root path=\"nimbus-jose-jwt.jar\"/>... @6:48) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/common/com/nimbusds/main/nimbus-jose-jwt.jar (No such file or directory)\r\n{code}\r\n\r\n\r\nFor the full `server.log`:\r\n\r\nhttps://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/artifact/exported-artifacts/check-patch.basic_fc_suite_master.el7.x86_64/test_logs/basic-fc-suite-master/post-001_initialize_engine.py/lago-basic-fc-suite-master-engine/_var_log/ovirt-engine/server.log/*view*/" (was: ovirt-engine Failed to start on Fedora 28 due to missing Java modules. {code:java} "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => [ "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" ], "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] } } {code} The full `server.log` contains the names of the missing modules: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/…) > Fail to run ovirt-engine on Fedora 28 > ------------------------------------- > > Key: OVIRT-2237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2237 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > ovirt-engine Failed to start on Fedora 28 due to missing Java module `nimbus-jose-jwt.jar` > {code:java} > "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => [ > "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", > "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" > ], > "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] > } > } > {code} > {code:java} > Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'nimbus-jose-jwt.jar' at path 'nimbus-jose-jwt.jar' (position: END_TAG seen ...<resources>\n <resource-root path="nimbus-jose-jwt.jar"/>... @6:48) caused by: java.io.FileNotFoundException: /usr/share/ovirt-engine/modules/common/com/nimbusds/main/nimbus-jose-jwt.jar (No such file or directory) > {code} > For the full `server.log`: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2180) Missing packages when trying to create reposync-config ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2180: -------------------------------- Resolution: Fixed Status: Done (was: To Do) > Missing packages when trying to create reposync-config ovirt-master on Fedora 28 > -------------------------------------------------------------------------------- > > Key: OVIRT-2180 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2180 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > When trying to create reposync-config for ovirt-master on FC28 the following packges are missing: > {code:java} > Error: > Problem 1: conflicting requests > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180308070539.git35a6428.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180530065728.git836691d.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180530070102.git836691d.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180604121623.git6aeb275.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180604121713.git6aeb275.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180607122548.gitbdfe919.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180607122828.gitbdfe919.fc28.x86_64 > Problem 2: conflicting requests > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 3: conflicting requests > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 4: conflicting requests > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2237) Fail to run ovirt-engine on Fedora 28
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

Gal Ben Haim created OVIRT-2237: ----------------------------------- Summary: Fail to run ovirt-engine on Fedora 28 Key: OVIRT-2237 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2237 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra ovirt-engine Failed to start on Fedora 28 due to missing Java modules. {code:java} "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => [ "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" ], "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] } } {code} The full `server.log` contains the names of the missing modules: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2237) Fail to run ovirt-engine on Fedora 28
by Gal Ben Haim (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2237?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2237: -------------------------------- Epic Link: OVIRT-2177 > Fail to run ovirt-engine on Fedora 28 > ------------------------------------- > > Key: OVIRT-2237 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2237 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > ovirt-engine Failed to start on Fedora 28 due to missing Java modules. > {code:java} > "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => [ > "jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"docs.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"enginesso.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"root.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"services.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"webadmin.war\".FIRST_MODULE_USE", > "jboss.deployment.subunit.\"engine.ear\".\"welcome.war\".FIRST_MODULE_USE", > "jboss.deployment.unit.\"engine.ear\".FIRST_MODULE_USE" > ], > "Services that may be the cause:" => ["jboss.naming.context.java.global.engine.bll.\"Backend!org.ovirt.engine.core.common.interfaces.BackendLocal\""] > } > } > {code} > The full `server.log` contains the names of the missing modules: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1335/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2236) Write pusher log to stdout instead of a file in standard-stage
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2236?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2236: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Write pusher log to stdout instead of a file in standard-stage > -------------------------------------------------------------- > > Key: OVIRT-2236 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2236 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: Daniel Belenky > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2236) Write pusher log to stdout instead of a file in standard-stage
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2236?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2236: ---------------------------------- Epic Link: OVIRT-400 > Write pusher log to stdout instead of a file in standard-stage > -------------------------------------------------------------- > > Key: OVIRT-2236 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2236 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2236) Write pusher log to stdout instead of a file in standard-stage
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2236: ------------------------------------- Summary: Write pusher log to stdout instead of a file in standard-stage Key: OVIRT-2236 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2236 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2235) Tag successfully deployed artifacts that passed CQ
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2235?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2235: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Tag successfully deployed artifacts that passed CQ > -------------------------------------------------- > > Key: OVIRT-2235 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2235 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > When CQ test is successful, all changes that were tested in the batch needs to be tagged. > ** Still need to think where is the best place to tag the changes ** > ** It can be CQ code that will do the tagging or it can be done from Groovy code ** -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2235) Tag successfully deployed artifacts that passed CQ
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2235: ------------------------------------- Summary: Tag successfully deployed artifacts that passed CQ Key: OVIRT-2235 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2235 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra When CQ test is successful, all changes that were tested in the batch needs to be tagged. ** Still need to think where is the best place to tag the changes ** ** It can be CQ code that will do the tagging or it can be done from Groovy code ** -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2235) Tag successfully deployed artifacts that passed CQ
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2235?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2235: ---------------------------------- Epic Link: OVIRT-1717 > Tag successfully deployed artifacts that passed CQ > -------------------------------------------------- > > Key: OVIRT-2235 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2235 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > When CQ test is successful, all changes that were tested in the batch needs to be tagged. > ** Still need to think where is the best place to tag the changes ** > ** It can be CQ code that will do the tagging or it can be done from Groovy code ** -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2234) Encapsulate tag-on-release option in queue_build_args
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2234?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2234: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Encapsulate tag-on-release option in queue_build_args > ----------------------------------------------------- > > Key: OVIRT-2234 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2234 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue, Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > In order to support reverse tagging in CQ, we have to encapsulate the 'tag-on-release' option when creating a new change object. > *Acceptance criteria:* > * Read the configuration from the DSL's output. > * Pass the configuration to the relevant CQ code when generating the change object. > * Change object needs to be able to handle such field and store it's data properly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2234) Encapsulate tag-on-release option in queue_build_args
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2234?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2234: ---------------------------------- Epic Link: OVIRT-1717 > Encapsulate tag-on-release option in queue_build_args > ----------------------------------------------------- > > Key: OVIRT-2234 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2234 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue, Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > In order to support reverse tagging in CQ, we have to encapsulate the 'tag-on-release' option when creating a new change object. > *Acceptance criteria:* > * Read the configuration from the DSL's output. > * Pass the configuration to the relevant CQ code when generating the change object. > * Change object needs to be able to handle such field and store it's data properly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2234) Encapsulate tag-on-release option in queue_build_args
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2234: ------------------------------------- Summary: Encapsulate tag-on-release option in queue_build_args Key: OVIRT-2234 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2234 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Change Queue, Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra In order to support reverse tagging in CQ, we have to encapsulate the 'tag-on-release' option when creating a new change object. *Acceptance criteria:* * Read the configuration from the DSL's output. * Pass the configuration to the relevant CQ code when generating the change object. * Change object needs to be able to handle such field and store it's data properly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2233?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2233: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add 'tag-on-release' configuration to STDCI DSL > ----------------------------------------------- > > Key: OVIRT-2233 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. > *Acceptance criteria:* > * Verify the structure of tag-on-release option > * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2233?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2233: ---------------------------------- Epic Link: OVIRT-1717 > Add 'tag-on-release' configuration to STDCI DSL > ----------------------------------------------- > > Key: OVIRT-2233 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > > As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. > *Acceptance criteria:* > * Verify the structure of tag-on-release option > * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2233: ------------------------------------- Summary: Add 'tag-on-release' configuration to STDCI DSL Key: OVIRT-2233 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. *Acceptance criteria:* * Verify the structure of tag-on-release option * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1983) Switch to using JJB >= 2.0.6
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1983?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1983: ----------------------------------- Assignee: Barak Korren (was: infra) > Switch to using JJB >= 2.0.6 > ---------------------------- > > Key: OVIRT-1983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > > Version 2.0.6 is the latest released version of JJB at the time of this writing. We've been using a very old development version of JJB (1.4.1.dev50) for a long time and its about time we upgraded. Other then that the post 2.0.0 has one major feature which is Jinja2 support which may be very useful for us. > In order to upgrade, we probably need to implement OVIRT-1466 first. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92435, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '18

24 Jun '18

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

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2231: ------------------------------------- This should probably be done from {{globals_setup.sh}} so setting component as "Jenkins Slaves" > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2231: -------------------------------- Component/s: (was: Lago) Jenkins Slaves > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1144) Make projects support more than one CI system
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1144?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1144: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We're not going to support other CI systems. > Make projects support more than one CI system > --------------------------------------------- > > Key: OVIRT-1144 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1144 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Eyal Edri > Assignee: infra > > Today we use 'automation' dir for running all standard CI flows on oVirt CI. > We need to take into consideration future projects will use multiple CI systems and be a part of multiple projects. > So a question is raised on how will the structure of dirs/files served in oVirt will look like. > One suggestion was to use .ovirtci which will translate to all the needs the oVirt CI will need. > There can be other options, this is the place to discuss them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-891: ------------------------------- Resolution: Fixed Status: Done (was: To Do) We already have support for doing various things with containers in STDCI. > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Eyal Edri > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-914: ------------------------------- Epic Link: (was: OVIRT-400) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-914: ------------------------------- Epic Link: (was: OVIRT-400) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-914: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: OVIRT-2189 > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: OVIRT-2189 > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: (was: OVIRT-400) > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: (was: OVIRT-400) > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-983: ------------------------------- Component/s: Standard CI (Pipelines) > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-983: ------------------------------- Epic Link: (was: OVIRT-400) > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-983: ------------------------------- Epic Link: (was: OVIRT-400) > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Epic Link: (was: OVIRT-400) > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Epic Link: (was: OVIRT-400) > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1135?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1135: -------------------------------- Component/s: Jenkins Master > consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1135 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > > Thanks, > I've removed the duplicate message, and opening a ticket on this to > consider more meaningful links or layout on the main page. > On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > If you click the "All" tab, you get double welcome message with > > similar content. > > Welcome to oVirt Jenkins continuous integration serverFor more > > information about the oVirt project visit http://www.ovirt.org > > Welcome to oVirt Jenkins continuous integration serverFor more info about > > the oVirt project, visit oVirt.org <http://ovirt.org/> > > See http://jenkins.ovirt.org/view/All/ > > > > I think we can remove the welcome message entirely, it makes sense only > > when > > you visit http://jenkins.ovirt.org/, and only for unlogged users. > > > > Logged users do not need the welcome message, it takes valuable space on > > the screen that > > can be used for useful data. > > > > Nir > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Component/s: Standard CI (Pipelines) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: (was: OVIRT-400) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Epic Link: (was: OVIRT-400) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Status: Done (was: To Do) We no longer use deploy-to-experimental anywhere. > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1174) deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1174: -------------------------------- Epic Link: (was: OVIRT-400) > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not create any RPMs > ------------------------------------------------------------------------------------------------------------ > > Key: OVIRT-1174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1174 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > deploy-to-experimental job fails when it is triggered by a build-artifacts job that does not crate any RPMs. It happens because {{repoman}} fails when it doesn't find any RPMs in the Jenkins build that was passed to it. > To solve this we probably just need to make build-artifacts not run deploy-to-experimental at all if no RPMs were created by it. > Here is an example run of deploy-to-experimental that failed because of this: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/12473/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1247) Re-factor SDK standard-CI jobs to not be different from other jobs
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1247?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1247: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Closing as wontfix since this ticket talks about the STDCI V1 jobs - we should convert the project to STDCI V2 anyway, so replacing this ticket with OVIRT-2232 > Re-factor SDK standard-CI jobs to not be different from other jobs > ------------------------------------------------------------------ > > Key: OVIRT-1247 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1247 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Right now the SDK building jobs use specialized YAML. This makes them different from all other Standard-CI jobs. Need to find a way make them like all the rest. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2232) Move SDK projects to STDCI V2
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2232?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2232: -------------------------------- Epic Link: OVIRT-2175 > Move SDK projects to STDCI V2 > ----------------------------- > > Key: OVIRT-2232 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2232 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > We have a strong incentive to do this since the SDK V1 jobs have their own messy job templates the require special maintenance... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0