August 2018 - Infra - Ovirt List Archives

Please use package versions when building rpms

by Dafna Ron

Hi All, As some of you may have noticed, we have been having failures for some of the tests in master in the past 24 hours with the following yum error: https://pastebin.com/vqJCLgrP After some debugging we found that the issue is caused because the package which is failing had two different commits and no version set which caused two different packages with exactly the same name to be created. To solve this issue we would need the package to be re-build with a new version set. Here are the details on the package and how it failed. As you can see below we had two different commits creating two different packages by the same name: https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/30/ which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0 https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/31/ which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4 checking the packages that exist in the 4.2 and master tested repos I can see that we have the same exact name for two different packages: 4.2: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c) MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20) master: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912) MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767) This would cause yum to fail because we cannot have the same package name with different checksums. If anyone needs help in setting up versioning please contact myself or anyone from the CI team and we would be happy to assist. Thanks, Dafna

6 years, 3 months

3
2
0 / 0

[CQ]: a3cb0b3 (ovirt-ansible-vm-infra) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change a3cb0b3 (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 0d6d028 (ovirt-ansible-vm-infra) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 0d6d028 (ovirt-ansible-vm- infra) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/a3cb0b303ed43c5541... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/0d6d02824aa8d86162... For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9146/

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2405: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-fc28-x86_64 - Build # 36 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc28-x8... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc28-x8... Build Number: 36 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #36 [Liora Milbaum] add Liora Milbaum to white list [Yuval Turgeman] build: add version and release.dist to iso name ----------------- Failed Tests: ----------------- No tests ran.

6 years, 3 months

1
1
0 / 0

[JIRA] (OVIRT-2437) patch fails CQ but not submitted to CQ message appears

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2437?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2437: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > patch fails CQ but not submitted to CQ message appears > ------------------------------------------------------ > > Key: OVIRT-2437 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2437 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > we have an alert for a patch that failed CQ but when I look at the patch I see the "This change was not submitted to any change queues" message. > I am also not seeing any build-artifacts job for the patch. > I see that the message continues with: > "If your project uses STDCI V2 and you have release branches configured, you may disregard this message." > However, if the package had not failed, is there any way for me to know that it is actually submitted to CQ? > example patch: https://gerrit.ovirt.org/#/c/93528/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2437) patch fails CQ but not submitted to CQ message appears

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2437?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2437: ---------------------------------- only way to know is to look at the job pipeline and see if its submitted to CQ. > patch fails CQ but not submitted to CQ message appears > ------------------------------------------------------ > > Key: OVIRT-2437 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2437 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > we have an alert for a patch that failed CQ but when I look at the patch I see the "This change was not submitted to any change queues" message. > I am also not seeing any build-artifacts job for the patch. > I see that the message continues with: > "If your project uses STDCI V2 and you have release branches configured, you may disregard this message." > However, if the package had not failed, is there any way for me to know that it is actually submitted to CQ? > example patch: https://gerrit.ovirt.org/#/c/93528/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2433) check-patch fails on reposync of ovirt-ansible-vm-infra-1.1.8-1.el7.noarch.rpm

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2433?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2433: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > check-patch fails on reposync of ovirt-ansible-vm-infra-1.1.8-1.el7.noarch.rpm > ------------------------------------------------------------------------------ > > Key: OVIRT-2433 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2433 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_cleanup, ost_failures > > I see random failures on > '05:42:12 [check-patch.upgrade-from-release_suite_master.el7.x86_64] - reposync command failed for repoid: ovirt-4.2-tested-el7' > it seems that the package which is failing is ovirt-ansible-vm-infra-1.1.8-1 > I can see that we are cleaning the package and still failing: https://pastebin.com/z6VA5KVk > I am trying to clean it manually on one of the hosts and see if it helps. > I see the same error on CQ and in check-patch on the same suite. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9090/conso... > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1653... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2433) check-patch fails on reposync of ovirt-ansible-vm-infra-1.1.8-1.el7.noarch.rpm

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2433?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2433: ---------------------------------- The issue was that the developer build the package without version change. this caused the same package to be build with the same name and different checksum. new package was merged that bumped version and should be resolving the issue today. > check-patch fails on reposync of ovirt-ansible-vm-infra-1.1.8-1.el7.noarch.rpm > ------------------------------------------------------------------------------ > > Key: OVIRT-2433 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2433 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_cleanup, ost_failures > > I see random failures on > '05:42:12 [check-patch.upgrade-from-release_suite_master.el7.x86_64] - reposync command failed for repoid: ovirt-4.2-tested-el7' > it seems that the package which is failing is ovirt-ansible-vm-infra-1.1.8-1 > I can see that we are cleaning the package and still failing: https://pastebin.com/z6VA5KVk > I am trying to clean it manually on one of the hosts and see if it helps. > I see the same error on CQ and in check-patch on the same suite. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9090/conso... > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1653... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2429) log collector fails on ovirt-master

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2429?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2429: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > log collector fails on ovirt-master > ----------------------------------- > > Key: OVIRT-2429 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2429 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures, ost_packages > > The issue is that they changed spec to a new package and the patch for the new package is not merged yet. > This is the patch that failed: https://gerrit.ovirt.org/#/c/93611/ > it needs to be re-triggered after this patch is merged: https://gerrit.ovirt.org/#/c/93376/ > Error: > '14:13:11 [basic-suite.el7.x86_64] Error: Package: ovirt-log-collector-4.3.0-0.0.master.20180809125418.gitc6718a9.el7.noarch (alocalsync) > 14:13:11 [basic-suite.el7.x86_64] Requires: python2-ovirt-engine-lib' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2429) log collector fails on ovirt-master

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2429?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2429: ---------------------------------- patch merged > log collector fails on ovirt-master > ----------------------------------- > > Key: OVIRT-2429 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2429 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures, ost_packages > > The issue is that they changed spec to a new package and the patch for the new package is not merged yet. > This is the patch that failed: https://gerrit.ovirt.org/#/c/93611/ > it needs to be re-triggered after this patch is merged: https://gerrit.ovirt.org/#/c/93376/ > Error: > '14:13:11 [basic-suite.el7.x86_64] Error: Package: ovirt-log-collector-4.3.0-0.0.master.20180809125418.gitc6718a9.el7.noarch (alocalsync) > 14:13:11 [basic-suite.el7.x86_64] Requires: python2-ovirt-engine-lib' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra August 2018