[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform
releases
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-2176:
-------------------------------------
Putting this under OVIRT-2184 as it seems full gating of platform changes would solve this as well.
> 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)
6 years, 7 months
[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform
releases
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2176:
--------------------------------
Epic Link: OVIRT-2184
> 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)
6 years, 7 months
[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform
releases
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2176:
--------------------------------
Epic Link: OVIRT-2184
> 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)
6 years, 7 months
[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform
releases
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2176:
--------------------------------
Epic Link: (was: 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)
6 years, 7 months
[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform
releases
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2176:
--------------------------------
Epic Link: (was: 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)
6 years, 7 months
[JIRA] (OVIRT-2193) vdsm project CQ failure:
004_basic_sanity.preview_snapshot_with_memory
by Dafna Ron (oVirt JIRA)
Dafna Ron created OVIRT-2193:
--------------------------------
Summary: vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
Key: OVIRT-2193
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra
we have a failed vdsm test in basic master suite.
004_basic_sanity.preview_snapshot_with_memory
seems like a regression.
' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth
2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe
/previewsnapshot'.
2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was
not provided.
at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:]
at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171]
at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]'
Change 90532,7 (vdsm) is probably the reason behind recent system test failures
in the "ovirt-master" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/90532/7
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2180) Missing packages when trying to create
reposync-config ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jir... ]
Gal Ben Haim commented on OVIRT-2180:
-------------------------------------
Thanks.
If I understand you correctly, until we drop the fluentd requirement from ovirt-engine, installing oVirt on Fedora is blocked?
> 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)
6 years, 7 months
