- Infra - oVirt List Archives

[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

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

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-723?page=com.atlassian.jira.p… ] eedri commented on OVIRT-723: ----------------------------- [~didi(a)redhat.com] is this still relevant? > 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)

2 1

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-768?page=com.atlassian.jira.p… ] eedri updated OVIRT-768: ------------------------ Issue Type: Improvement (was: By-EMAIL) > Decomission of MD5 Password Hashes for Infra Users > -------------------------------------------------- > > Key: OVIRT-768 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > During the work of moving password parameters from foreman to internal > hiera I noted that there are some users that still have their passwords > hashed by MD5 algorithm. > MD5 has known crypto research that make it no longer suitable for storing > passwords securely: > https://en.wikipedia.org/wiki/MD5#Security (and corresponding links). > While the hashes are stored in internal repo it is still shared and prone > to information leaks. We should ask all users to rehash their passwords > with SHA-512 and when it is done we can remove MD5 exception > in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no > longer accepted. > The current list of users left is available in infra-hiera repo. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-769) infra-hiera Autodeploy via Gerrit Hooks
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-769?page=com.atlassian.jira.p… ] eedri updated OVIRT-769: ------------------------ Issue Type: Improvement (was: By-EMAIL) > infra-hiera Autodeploy via Gerrit Hooks > --------------------------------------- > > Key: OVIRT-769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-769 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > infra-hiera repo is already used and configured in r10k to deploy from git. > However in gerrit there is not hooks that run CI on it and that trigger > publish when it is merged to git. > Looks like it is easy to fix and we can reuse most of the hooks we have for > infra-puppet. Basically the deploy should be done using the same jenkins > job and it already does that just not triggered. > As for CI check than we need to check if puppetlint we use is sufficient. > But it might be a good start. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eedri updated OVIRT-978: ------------------------ Issue Type: Improvement (was: By-EMAIL) > Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service > ---------------------------------------------------------------------------------------- > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: danken > Assignee: infra > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1128) Add Jenkins job for testing
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ] eedri updated OVIRT-1128: ------------------------- Issue Type: New Feature (was: By-EMAIL) > Add Jenkins job for testing > --------------------------- > > Key: OVIRT-1128 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Pavel Zhukov > Assignee: infra > Labels: staging > > it'd be good to have jenkins job to test and regenerate jenkins jobs :) > which uses "good" jjb configuration and available for infra team from > any machine. > Currently local JJB instances and configs are used which is not perfect > because configs can be different as well as jjb versions, not rebased > repos can be used for testing Besides of that it requires copying of > configs between machines and so on. > -- > Pavel -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1156?page=com.atlassian.jira.… ] eedri updated OVIRT-1156: ------------------------- Issue Type: Bug (was: By-EMAIL) > Fwd: build-artifacts-on-demand marks CI +1 > ------------------------------------------ > > Key: OVIRT-1156 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > Forwarding to Jira. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: 16 February 2017 at 15:02 > Subject: build-artifacts-on-demand marks CI +1 > To: infra <infra(a)ovirt.org> > Hi all, > I have a change [1] that currently fails some jenkins jobs, so it gets > -1 from it. After pushing patchset 4 (a mere rebase actually), I ran > build-artifacts-on-demand ("ci please build"), and it passed, and set > CI +1. Then I rebased again and again got -1 as expected. > IMO build-artifacts-on-demand should not set CI +1, it might be > misleading for the maintainer to think that all is good when in fact > CI failed. > [1] https://gerrit.ovirt.org/71590 > -- > Didi > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0