- Infra - oVirt List Archives

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Epic Name: Automate standard-CI job creation > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Issue Type: Epic (was: Improvement) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Epic Link: (was: OVIRT-400) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Summary: Automate standard-CI job creation (was: Automate standard-CI job creation (V2)) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1679) Move Lago to use the STDCI pipelines
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1679?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1679: -------------------------------- Epic Link: OVIRT-2175 (was: OVIRT-400) > Move Lago to use the STDCI pipelines > ------------------------------------ > > Key: OVIRT-1679 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1679 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, github, jenkins, lago, standard-ci > > Because of work on OVIRT-1522, OVIRT-1599, we now have new pipeline jobs for GitHub projects. OVIRT-1486 and OVIRT-1534 gave us the ability to create change queues for GitHub projects. This is time to seriosly consider moving Lago from its old lago-specific STDCI clone to the general STDCI/CQ scheme. > Once we do that, we can also remove all the templates that are only used by Lago ATM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1679) Move Lago to use the STDCI pipelines
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1679?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1679: -------------------------------- Epic Link: OVIRT-2175 (was: OVIRT-400) > Move Lago to use the STDCI pipelines > ------------------------------------ > > Key: OVIRT-1679 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1679 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, github, jenkins, lago, standard-ci > > Because of work on OVIRT-1522, OVIRT-1599, we now have new pipeline jobs for GitHub projects. OVIRT-1486 and OVIRT-1534 gave us the ability to create change queues for GitHub projects. This is time to seriosly consider moving Lago from its old lago-specific STDCI clone to the general STDCI/CQ scheme. > Once we do that, we can also remove all the templates that are only used by Lago ATM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2182?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2182: -------------------------------- Description: The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. > Create timed jobs > ----------------- > > Key: OVIRT-2182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Gal Ben Haim > Assignee: infra > > The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2182: ----------------------------------- Summary: Create timed jobs Key: OVIRT-2182 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2181: ----------------------------------- Summary: Release lago-ovirt for fc28 Key: OVIRT-2181 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 Project: oVirt - virtualization made easy Issue Type: Sub-task Components: OST Reporter: Gal Ben Haim Assignee: infra -- 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) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2180: -------------------------------- Description: 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} was: When trying to install 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} > 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-2180) Missing packages when trying to create reposync-config ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2180: -------------------------------- Summary: Missing packages when trying to create reposync-config ovirt-master on Fedora 28 (was: Missing packages when trying to install ovirt-master on Fedora 28) > 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 install 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-2180) Missing packages when trying to install ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2180: ----------------------------------- Summary: Missing packages when trying to install 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 install 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-2179) Allow connections to the JNLP port of our jnekins instances
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2179?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2179: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Allow connections to the JNLP port of our jnekins instances > ----------------------------------------------------------- > > Key: OVIRT-2179 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2179 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > We want to be able to "borrow" slaves from other systems by having them connect back to our Jenkins instances via JNLP. > Could we open the JNLP port in the various firewalls we have in front of our systems? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2179) Allow connections to the JNLP port of our jnekins instances
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

Barak Korren created OVIRT-2179: ----------------------------------- Summary: Allow connections to the JNLP port of our jnekins instances Key: OVIRT-2179 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2179 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Master Reporter: Barak Korren Assignee: infra Priority: High We want to be able to "borrow" slaves from other systems by having them connect back to our Jenkins instances via JNLP. Could we open the JNLP port in the various firewalls we have in front of our systems? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2179) Allow connections to the JNLP port of our jnekins instances
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2179?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2179: -------------------------------- Epic Link: OVIRT-2178 > Allow connections to the JNLP port of our jnekins instances > ----------------------------------------------------------- > > Key: OVIRT-2179 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2179 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > Priority: High > > We want to be able to "borrow" slaves from other systems by having them connect back to our Jenkins instances via JNLP. > Could we open the JNLP port in the various firewalls we have in front of our systems? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2177) Add Fedora master suite
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2177?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2177: -------------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > Add Fedora master suite > ----------------------- > > Key: OVIRT-2177 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2177 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > > A master suite that runs on Fedora will help us to detect bugs on the next Centos. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2178) "Borrow" slaves from CentOS CI
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2178?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2178: -------------------------------- Description: [CentOS CI|https://wiki.centos.org/QaWiki/CI] is a generic shared platform for building CI service for Open Source projects. Amount other things, CentOS CI makes physical and virtual hosts available for running CI processes via the [Duffy|http://wiki.centos.org/QaWiki/CI/Duffy] system. We should make oVirt CI able to consume resources from CentOs CI to augment and someday replace the hardware resources available to oVirt CI. > "Borrow" slaves from CentOS CI > ------------------------------ > > Key: OVIRT-2178 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2178 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Barak Korren > Assignee: infra > > [CentOS CI|https://wiki.centos.org/QaWiki/CI] is a generic shared platform for building CI service for Open Source projects. > Amount other things, CentOS CI makes physical and virtual hosts available for running CI processes via the [Duffy|http://wiki.centos.org/QaWiki/CI/Duffy] system. > We should make oVirt CI able to consume resources from CentOs CI to augment and someday replace the hardware resources available to oVirt CI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2178) "Borrow" slaves from CentOS CI
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

Barak Korren created OVIRT-2178: ----------------------------------- Summary: "Borrow" slaves from CentOS CI Key: OVIRT-2178 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2178 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: Barak Korren Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2177) Add Fedora master suite
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2177: ----------------------------------- Summary: Add Fedora master suite Key: OVIRT-2177 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2177 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: Gal Ben Haim Assignee: infra A master suite that runs on Fedora will help us to detect bugs on the next Centos. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Network test that randomly fails on CI
by Ala Hino 10 Jun '18

10 Jun '18

Hi, From time to time, I see the following failure of a network test. I understood from Ed that it is a CI known issue. Would appreciate if this can be fixed ASAP. Thanks. *09:59:56* self = <network.integration.ovs.ovs_info_test.TestOvsInfo testMethod=test_ovs_info_with_sb_nic>*09:59:56* *09:59:56* def test_ovs_info_with_sb_nic(self):*09:59:56* with dummy_device() as nic:*09:59:56* > with _setup_ovs_network(self.ovsdb, nic):*09:59:56* *09:59:56* network/integration/ovs/ovs_info_test.py:78: *09:59:56* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *09:59:56* /usr/lib64/python2.7/contextlib.py:17: in __enter__*09:59:56* return self.gen.next()*09:59:56* network/integration/ovs/ovs_info_test.py:63: in _setup_ovs_network*09:59:56* t.add(*_northbound_port())*09:59:56* ../lib/vdsm/network/ovs/driver/__init__.py:46: in __exit__*09:59:56* self.result = self.commit()*09:59:56* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *09:59:56* *09:59:56* self = <vdsm.network.ovs.driver.vsctl.Transaction object at 0x7fdbab22db50>*09:59:56* *09:59:56* def commit(self):*09:59:56* if not self.commands:*09:59:56* return*09:59:56* *09:59:56* timeout_option = []*09:59:56* if self.timeout:*09:59:56* timeout_option = ['--timeout=' + str(self.timeout)]*09:59:56* *09:59:56* args = []*09:59:56* for command in self.commands:*09:59:56* args += ['--'] + command.cmd*09:59:56* exec_line = [_ovs_vsctl_cmd()] + timeout_option + OUTPUT_FORMAT + args*09:59:56* logging.debug('Executing commands: %s' % ' '.join(exec_line))*09:59:56* *09:59:56* rc, out, err = netcmd.exec_sync(exec_line)*09:59:56* if rc != 0:*09:59:56* err = err.splitlines()*09:59:56* if OvsDBConnectionError.is_ovs_db_conn_error(err):*09:59:56* raise OvsDBConnectionError('\n'.join(err))*09:59:56* else:*09:59:56* raise ConfigNetworkError(*09:59:56* ne.ERR_BAD_PARAMS,*09:59:56* > 'Executing commands failed: %s' % '\n'.join(err))*09:59:56* E ConfigNetworkError: (21, 'Executing commands failed: ovs-vsctl: cannot create a bridge named vdsmbr_test because a bridge named vdsmbr_test already exists')*09:59:56* *09:59:56* ../lib/vdsm/network/ovs/driver/vsctl.py:78: ConfigNetworkError

2 3

[JIRA] (OVIRT-2156) create gerrit repo: ovirt-engine-ui-extensions
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2156?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2156: -------------------------------- Assignee: Gal Ben Haim (was: infra) > create gerrit repo: ovirt-engine-ui-extensions > ---------------------------------------------- > > Key: OVIRT-2156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2156 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Gal Ben Haim > > Hi, > Please create ovirt-engine-ui-extensions in gerrit, mirrored to github > It can have the same people + permissions as ovirt-engine-dashboard (it > will probably replace ovirt-engine-dashbaord) > Best wishes, > Greg > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2176: ------------------------------------- Actually I think the user story is quite simple here - "As an ovirt developer, I would like to know as early as possible if platform changes are going to break oVirt so that I can react to them in a timely manner". Or perhaps its "As a platform component developer I would like to know if changes I make are causing issues in oVirt as early as possible so I can eliminate those issues as early as possible and have newer version of my component be adopted by oVirt". Actually which one of the two stories above we decide to aim for has significant influence on the kind of implementation we aim for. > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2164: ---------------------------------- [~ena(a)redhat.com] since you moved Python-Errata, do you think you can handle moving repoman as well? [~amarchuk] WDYT? > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- [~amarchuk] FYI > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- People want to run Lago on their FC28, so its quite important we'll prioritize it. > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2163: ----------------------------- Priority: Highest (was: Medium) > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2163: ---------------------------------- [~ena(a)redhat.com] is that something you can do? did you have time to go over repoman a bit? > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2176: ----------------------------- Epic Link: OVIRT-400 > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by eyal edri (oVirt JIRA) 10 Jun '18

10 Jun '18

eyal edri created OVIRT-2176: -------------------------------- Summary: oVirt CI should support fast moving platform releases Key: OVIRT-2176 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri Assignee: infra It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2164: -------------------------------- Epic Link: OVIRT-2175 > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2164: -------------------------------- Epic Link: OVIRT-2175 > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2175: ------------------------------------- Summary: Move oVirt projects to STDCI V2 Key: OVIRT-2175 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175 Project: oVirt - virtualization made easy Issue Type: Epic Components: oVirt CI Reporter: Daniel Belenky Assignee: infra As STDCI V2 is live and production for a while now, it's time to proactively push and assist oVirt projects to move to STDCI V2. Projects will benefit from new STDCI V2 features such as the ability to modify the distributions and architectures they build on without having to send patches to the 'Jenkins' repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2174: ---------------------------------- Epic Link: OVIRT-400 > Show dedicated message to early infra failures on STDCI build summary > --------------------------------------------------------------------- > > Key: OVIRT-2174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2174: ------------------------------------- Summary: Show dedicated message to early infra failures on STDCI build summary Key: OVIRT-2174 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2173: ------------------------------------- Summary: STDCI build summary to include details about the STDCI event Key: OVIRT-2173 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2173: ---------------------------------- Epic Link: OVIRT-400 > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2172: ---------------------------------- Epic Link: OVIRT-400 > STDCI build summary to write message when no threads were found > --------------------------------------------------------------- > > Key: OVIRT-2172 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2172: ------------------------------------- Summary: STDCI build summary to write message when no threads were found Key: OVIRT-2172 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2171) Add support for HTML artifacts in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2171: ------------------------------------- Summary: Add support for HTML artifacts in STDCI build summary Key: OVIRT-2171 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra Priority: Low As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2171) Add support for HTML artifacts in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2171?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2171: ---------------------------------- Epic Link: OVIRT-400 > Add support for HTML artifacts in STDCI build summary > ----------------------------------------------------- > > Key: OVIRT-2171 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > Priority: Low > > As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2170) Link from SCM to STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2170: ------------------------------------- Summary: Link from SCM to STDCI build summary Key: OVIRT-2170 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2170) Link from SCM to STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2170?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2170: ---------------------------------- Epic Link: OVIRT-400 > Link from SCM to STDCI build summary > ------------------------------------ > > Key: OVIRT-2170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2169) Show important thread information in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2169: ------------------------------------- Summary: Show important thread information in STDCI build summary Key: OVIRT-2169 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2169) Show important thread information in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2169?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2169: ---------------------------------- Epic Link: OVIRT-400 > Show important thread information in STDCI build summary > -------------------------------------------------------- > > Key: OVIRT-2169 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2168: ------------------------------------- Summary: Show build artifacts as soon as they are created in STDCI build summary Key: OVIRT-2168 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2168: ---------------------------------- Epic Link: OVIRT-400 > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2167: ---------------------------------- Epic Link: OVIRT-400 > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

Daniel Belenky created OVIRT-2167: ------------------------------------- Summary: Near real time log updates for STDCI build summary Key: OVIRT-2167 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Gerrit is slow again
by Nir Soffer 10 Jun '18

10 Jun '18

It was also very slow last week, moving between patches takes many seconds. It seems that there is some caching mechanism in gerrit, so after very slow page retrieval, the next request is fast. But this happens too many times. We need to understand why this slowdown happens and make sure the system is kept responsive. Nir

2 1

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 10 Jun '18

10 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/183/

1 0