June 2017 - Infra - oVirt List Archives

Change 78740,1 (ovirt-log-collector) failed system tests
by oVirt Jenkins 27 Jun '17

27 Jun '17

Change 78740,1 (ovirt-log-collector) 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/78740/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/954/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7379 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_48_1745367497.1498575016954 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7379/, Build Number: 7379, Build Status: FAILURE ------=_Part_48_1745367497.1498575016954--

1 4

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-723: ------------------------------------ We're using both DNF and Pytohn3 in the '{{check-patch.sh}}' of the Jenkins repo. So we know they work. Is there other requirement in this ticket besides just checking? > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1485: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: Daniel Belenky > Labels: containers > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1485: -------------------------------- Labels: containers (was: ) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: infra > Labels: containers > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1485: -------------------------------- Issue Type: New Feature (was: Task) > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Juan Hernández > Assignee: infra > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 28 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_593_1515763556.1497982382061 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build Number: 28 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #28 [Gil Shinar] Added shubham dubey to jenkins whitelist [Tomas Jelinek] adding pkotas to CI whitelist [Sandro Bonazzola] ovirt-engine-sdk: disable fc26 ppc64le [Sandro Bonazzola] ioprocess: add fc26 support [Shirly Radco] ovirt-engine-metrics: add build-on-demand job [Yuval Turgeman] Revert "engine-appliance: build in selinux enforcing mode" ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_593_1515763556.1497982382061--

1 1

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Juan Hernández (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1485?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1485: --------------------------------------- /cc [~ybronhei(a)redhat.com] [~stirabos(a)redhat.com] [~oourfali(a)redhat.com] [~fdeutsch] > Create a GitHub releases deployment token for ovirt-containers > -------------------------------------------------------------- > > Key: OVIRT-1485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Juan Hernández > Assignee: infra > > The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: > Configure Travis CI to do GitHub releases > https://gerrit.ovirt.org/78732 > That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1485) Create a GitHub releases deployment token for ovirt-containers
by Juan Hernández (oVirt JIRA) 27 Jun '17

27 Jun '17

Juan Hernández created OVIRT-1485: ------------------------------------- Summary: Create a GitHub releases deployment token for ovirt-containers Key: OVIRT-1485 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1485 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Juan Hernández Assignee: infra The ovirt-containers project produces a binary that we want to release automatically using the Travis CI and GitHub releases mechanism. To do so we need to add to the project an encrypted GitHub token with permissions to add files to releases. The details are in the following patch: Configure Travis CI to do GitHub releases https://gerrit.ovirt.org/78732 That token can only be generated by the owner of the GitHub project. Can you please generate it? -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI
by Yedidyah Bar David (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] Yedidyah Bar David commented on OVIRT-723: ------------------------------------------ On Tue, Jun 27, 2017 at 5:55 PM, eedri (oVirt JIRA) Can't see why not - we still want python3 support eventually. Didn't check recently about actual status, and this was postponed to oVirt 4.3. -- Didi > check/add support for python3 + dnf on standard CI > -------------------------------------------------- > > Key: OVIRT-723 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Patch [1] fails jenkins [2] like this: > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ INFO ] Stage: Environment packages setup > 11:35:21 [ INFO ] DNF Repository updates-testing is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Repository updates-testing-debuginfo is listed > more than once in the configuration > 11:35:21 [ INFO ] DNF Repository updates is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository updates-debuginfo is listed more > than once in the configuration > 11:35:21 [ INFO ] DNF Repository fedora is listed more than once in > the configuration > 11:35:21 [ INFO ] DNF Repository fedora-debuginfo is listed more than > once in the configuration > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Downloading 1 files, 0.00KB > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'fedora', disabling. > 11:35:21 [ INFO ] DNF Failed to synchronize cache for repo 'updates', > disabling. > 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched > 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages > setup': no package matched > I suspected, based on the log, that something is broken about dnf > configuration, so pushed [3] and ran the job again [4] with [3] > cherry-picked, and it succeeded. I thought that's enough for a > verification, so asked to merge it, and it was merged. Later on, lago > tests started breaking [5] with: > 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by > python-lago-ovirt-0.24.0-1.fc23.noarch > So [3] was reverted [6], Currently pending, but I expect it to be merged soon. > So we need a better solution. > While investigating this, Nadav partially understood the issue - we have, at > certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf. > Not sure why and whether we need both. > We tried also various variations on this patch in [7][8][9][10], none worked. > Probably better to fully support dnf instead of this hack, not sure > what this requires. > Thanks, > [1] https://gerrit.ovirt.org/59831 > [2] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console > [3] https://gerrit.ovirt.org/63249 > [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/ > [5] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/conso… > [6] https://gerrit.ovirt.org/63405 > [7] https://gerrit.ovirt.org/63386 > [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203 > [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/ > [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/ > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0