[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
[ https://ovirt-jira.atlassian.net/browse/OVIRT-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-930: Epic Link: OVIRT-400 > check why ost 4.0 failed on vm run job even though not change was done > -- > > Key: OVIRT-930 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra > > Looks like false positive or race issue, but still needs to be debug for RCA. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleFull -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
eyal edri [Administrator] created OVIRT-931: --- Summary: profile why ovirt-engine check-patch takes between 10-50 min Key: OVIRT-931 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High Same job sometimes takes little as 10 min but sometimes high as 50 min. We need to understand why. http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/buildTimeTrend -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-931: Epic Link: OVIRT-400 > profile why ovirt-engine check-patch takes between 10-50 min > - > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/buildTimeTrend -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24223#comment-24223 ] eyal edri [Administrator] commented on OVIRT-931: - [~gshinar] thanks for the quick debug, [~ederevea] can we have a list of "problematic hypervisors"? we might want to move them to Lago or production DC. > profile why ovirt-engine check-patch takes between 10-50 min > - > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/buildTimeTrend -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-932) Wrong Lago version used in CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-932: --- Assignee: Gal Ben Haim (was: infra) According to [~bkor...@redhat.com] the new changed in mock cache should cause this. Any idea where else it can come from? We cleared the mock cache also on the ovirt-srv22 server, and I now rerun the job to see if it works. > Wrong Lago version used in CI > - > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Yaniv Kaul >Assignee: Gal Ben Haim >Priority: High > > See > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/324/console > : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = > 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
[
https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24230#comment-24230
]
eyal edri [Administrator] commented on OVIRT-933:
-
[~ederevea] didn't we disable or stopped using the repo proxy? I remember
another ticket on it.
> Fix repoproxy service and logging mess
> --
>
> Key: OVIRT-933
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>
> There are a couple of issues with the way repoproxy runs right now, these
> issues probably cause it to be less stable then it can:
> # repoproxy is can currently be invoked only from puppet, because a lot of
> the data on how to run it is stored right now in puppet and nowhere else. We
> should make puppet create a systemd unit file to run repoproxy instead of
> running it itself. This way we can get rid of the cron job that runs puppet
> every 2 minutes on the proxy.
> # repoproxy is configured to run as the '{{squid}}' user and log to
> '{{/var/log/repoproxy.log}}'. That file is pre-created with the right
> permissions bu Puppet so repoproxy can write to it. However, the Python
> logger in repoproxy is configured to try and rotate the log when it becomes
> too big. That, in turn, will cause it to crash because the '{{squid}}' user
> cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere
> else.
--
This message was sent by Atlassian JIRA
(v1000.620.0#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-924) 3.6 DAO tests failing due to missing postgres
[ https://ovirt-jira.atlassian.net/browse/OVIRT-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-924: --- Assignee: Pavel Zhukov (was: infra) I disabled the jobs for now, please check if they are in any YAML, if not we can keep them disabled or delete them. > 3.6 DAO tests failing due to missing postgres > - > > Key: OVIRT-924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-924 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: Evgheni Dereveanchin >Assignee: Pavel Zhukov > > Postgres was removed from Jenkins slaves as part of OVIRT-593 and we expect > that all jobs install packages they need at runtime. > Yet, 3.6 DAO tests are still expecting postgres on slaves: > http://jenkins.ovirt.org/job/ovirt-engine_3.6_dao-unit-tests_created > 08:53:26 /home/jenkins/workspace/ovirt-engine_3.6_dao-unit-tests_created > 08:53:26 + sudo -u postgres psql -d template1 -c 'create role engine;' > 08:53:26 sudo: unknown user: postgres > 08:53:26 sudo: unable to initialize policy plugin > The job needs to be updated. -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-936) [URGENT] Mailing list archives can't be accessed
[ https://ovirt-jira.atlassian.net/browse/OVIRT-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24404#comment-24404 ] eyal edri [Administrator] commented on OVIRT-936: - There is a thread on this already I think, Anyway I can access [1] now without any issues. [1] http://lists.phx.ovirt.org/pipermail/devel/ On Tue, Dec 13, 2016 at 4:56 PM, sbonazzo (oVirt JIRA) < -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > [URGENT] Mailing list archives can't be accessed > > > Key: OVIRT-936 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-936 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Mailing lists (Mailman) >Reporter: sbonazzo >Assignee: infra >Priority: Highest > > Please check lists configuration and fix it to make archives publicly > accessible. > See: > http://lists.phx.ovirt.org/pipermail/devel/ > http://lists.phx.ovirt.org/pipermail/users/ > and others. -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-923) define process to manage and apply ansible playbooks
[ https://ovirt-jira.atlassian.net/browse/OVIRT-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-923: Epic Link: OVIRT-403 > define process to manage and apply ansible playbooks > > > Key: OVIRT-923 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-923 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Evgheni Dereveanchin >Assignee: infra >Priority: Low > > We already have a repository with ansible code, but to use it effectively we > need to define a way to manage playbooks and run them effectively. As Ansible > Tower is not open source we need to investigate other solutions on the market. -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-923) define process to manage and apply ansible playbooks
[ https://ovirt-jira.atlassian.net/browse/OVIRT-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-923: Epic Link: OVIRT-403 > define process to manage and apply ansible playbooks > > > Key: OVIRT-923 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-923 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Evgheni Dereveanchin >Assignee: infra >Priority: Low > > We already have a repository with ansible code, but to use it effectively we > need to define a way to manage playbooks and run them effectively. As Ansible > Tower is not open source we need to investigate other solutions on the market. -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
[
https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24412#comment-24412
]
eyal edri [Administrator] commented on OVIRT-935:
-
[~bkor...@redhat.com] [~sbonazo...@redhat.com] thoughts? we might wait a long
time until the bug is fixed.
> Unable to build fc25 chroots with mock
> --
>
> Key: OVIRT-935
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: infra
>
> Mock fails when trying to build the chroot for fedora25, on installing
> '@buildsys-build' group(with dnf) stage.
> Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781
> Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file.
> Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always
> install 'libcrypt' first.
> Until fixed this will block us from building anything with mock on fc25(hit
> it when trying to build fc25 RPMs for lago).
> Error logs:
> {code}
> DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated',
> '--installroot',
> '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/',
> '--releasever', '25', 'install', '@buildsys-build', 'git', 'python',
> 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils',
> '--setopt=tsflags=nocontexts'] with env {'PS1': ' \\s-\\v\\$ ',
>
> DEBUG util.py:421: Yum command has been deprecated, use dnf instead.
> DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information.
> DEBUG util.py:421: Error: libcrypt conflicts with
> libcrypt-nss-2.24-3.fc25.x86_64
> DEBUG util.py:421: Error: libcrypt-nss conflicts with
> libcrypt-2.24-3.fc25.x86_64
> DEBUG util.py:421: You could try using --skip-broken to work around the
> problem
> DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest
> DEBUG util.py:557: Child return code was: 1
> DEBUG util.py:180: kill orphans
> {code}
--
This message was sent by Atlassian JIRA
(v1000.621.2#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-918) upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ]
[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-918: Summary: upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ] (was: Special characters escaped in Jenkins manual triggering of CI) > upgrade Gerrit Trigger plugin to latest [Special characters escaped in > Jenkins manual triggering of CI ] > > > Key: OVIRT-918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-918 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Allon Mureinik >Assignee: infra > > If a subject of a change has special characters, they get HTML-encoded when > presenting it in the Jenkins manual trigger job. > See screenshot for an example: > http://imgur.com/G1M7vNu -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-918) upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ]
[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-918: --- Assignee: Evgheni Dereveanchin (was: infra) > upgrade Gerrit Trigger plugin to latest [Special characters escaped in > Jenkins manual triggering of CI ] > > > Key: OVIRT-918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-918 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Allon Mureinik >Assignee: Evgheni Dereveanchin > > If a subject of a change has special characters, they get HTML-encoded when > presenting it in the Jenkins manual trigger job. > See screenshot for an example: > http://imgur.com/G1M7vNu -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-910: --- Assignee: Evgheni Dereveanchin (was: infra) I think its duplicate of the 10-50 min task, feel free to close duplicate if its the case. > mock_runner.sh seems to run slower on newer slaves > -- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins >Reporter: Barak Korren >Assignee: Evgheni Dereveanchin > > After implementing speedup improvements for mock_runner.sh (Specifically > enabling it to deploy the chroot by extracting a tarball as opposed to > installing it with yum every time), I started monitoring run times for vdsm > check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to > initialize mock faster then ones running on new slaves (vm*) - 17seconds vs > 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on > /var/cache/mock -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-904: Blocked By: pending response from requestor Status: Blocked (was: To Do) > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > - > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: danken >Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64 -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24415#comment-24415 ] eyal edri [Administrator] commented on OVIRT-904: - What was the decision? Can you move the patternfly to ovirt static repo? > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > - > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: danken >Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64 -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-817) Install notification plugin for jenkins.ovirt.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-817: --- Assignee: Evgheni Dereveanchin (was: infra) > Install notification plugin for jenkins.ovirt.org > - > > Key: OVIRT-817 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-817 > Project: oVirt - virtualization made easy > Issue Type: New Feature >Reporter: eyal edri [Administrator] >Assignee: Evgheni Dereveanchin > > please follow > https://ovirt-jenkins.getbadges.io/manager/project/2924/app/5820/show -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-881) prepare for bugizlla 5 upgrade - api changes
[ https://ovirt-jira.atlassian.net/browse/OVIRT-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-881: --- Assignee: Shlomo Ben David (was: infra) > prepare for bugizlla 5 upgrade - api changes > > > Key: OVIRT-881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-881 > Project: oVirt - virtualization made easy > Issue Type: New Feature >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David >Priority: High > > oVirt Bugzilla will be upgraded to Bugzilla 5.0 in the following months, > We should make sure all our automation still works with the new API and > verify mostly Gerrit Hooks still works. > Also, the new version will include RESTAPI as oppose to XMLRPC which was used > until now. > Worth looking for existing tools / SDKs which exists that we might be able to > use. > cc [~amarchuk] [~sbend...@redhat.com] [~ederevea] -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-845) Build oVirt 4.0.6 RC1
[ https://ovirt-jira.atlassian.net/browse/OVIRT-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24422#comment-24422 ] eyal edri [Administrator] commented on OVIRT-845: - can we close it? > Build oVirt 4.0.6 RC1 > - > > Key: OVIRT-845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-845 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Repositories Mgmt >Reporter: sbonazzo >Assignee: infra >Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24424#comment-24424 ] eyal edri [Administrator] commented on OVIRT-904: - NP, I'm just concerned if CI will keep failing because the copr repo isn't reliable. If thats not an issue then we can wait for 4.2. Also, if you are building it, we can add it to standard CI, and built it automatically. > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > - > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: danken >Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64 -- This message was sent by Atlassian JIRA (v1000.621.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-885) lago-devel list stopped archiving mails from November 2016
[ https://ovirt-jira.atlassian.net/browse/OVIRT-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-885: Resolution: Fixed Status: Done (was: To Do) seems that post the lists migration to PHX the issue is fixed and we can see lago-devel archives now: http://lists.phx.ovirt.org/pipermail/lago-devel/ > lago-devel list stopped archiving mails from November 2016 > -- > > Key: OVIRT-885 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-885 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra > > Can't see any mails from Nov [1] even though the settings was set to weekly. > [1] http://lists.ovirt.org/pipermail/lago-devel/ -- This message was sent by Atlassian JIRA (v1000.621.3#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-944) Prepare CI for 4.1 oVirt branch
[ https://ovirt-jira.atlassian.net/browse/OVIRT-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-944: Epic Link: OVIRT-400 > Prepare CI for 4.1 oVirt branch > --- > > Key: OVIRT-944 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-944 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > We need to add all relevant jobs and flows for 4.1, lets use this ticket to > track all progress > * system tests > * experimental flows > * publishers > * deploy to experimental > * gerrit hooks (?) > * standard flows for various projects > cc [~sbonazo...@redhat.com] [~ederevea] [~bkor...@redhat.com] [~amarchuk] > [~sbend...@redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.4#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-944) Prepare CI for 4.1 oVirt branch
eyal edri [Administrator] created OVIRT-944: --- Summary: Prepare CI for 4.1 oVirt branch Key: OVIRT-944 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-944 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest We need to add all relevant jobs and flows for 4.1, lets use this ticket to track all progress * system tests * experimental flows * publishers * deploy to experimental * gerrit hooks (?) * standard flows for various projects cc [~sbonazo...@redhat.com] [~ederevea] [~bkor...@redhat.com] [~amarchuk] [~sbend...@redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.4#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-920) Add a standard-CI job and button "build-scratch-artifacts"
[ https://ovirt-jira.atlassian.net/browse/OVIRT-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-920: --- Assignee: eyal edri [Administrator] (was: infra) > Add a standard-CI job and button "build-scratch-artifacts" > -- > > Key: OVIRT-920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-920 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: eyal edri [Administrator] > > Hi, > I think it will be useful to have an option to very easily (such as > pressing a button in gerrit) to do a full build of a project, > similarly to current build-artifacts, but for a pending patch - so it > will not be collected by any publisher, and will keep its artifacts > for a short time (say, 2 days). > This will allow to use these artifacts for manual tests, perhaps > longer than check-patch, in case a developer wants to do them. > -- > Didi -- This message was sent by Atlassian JIRA (v1000.621.4#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
[
https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24707#comment-24707
]
eyal edri [Administrator] commented on OVIRT-935:
-
This comes with a price - if we'll have more fedora slaves than centos due to
this, then we'll need to to mass upgrades much more often, due to the speed of
fedora releases goes EOL
> Unable to build fc25 chroots with mock
> --
>
> Key: OVIRT-935
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: infra
>
> Mock fails when trying to build the chroot for fedora25, on installing
> '@buildsys-build' group(with dnf) stage.
> Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781
> Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file.
> Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always
> install 'libcrypt' first.
> Until fixed this will block us from building anything with mock on fc25(hit
> it when trying to build fc25 RPMs for lago).
> Error logs:
> {code}
> DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated',
> '--installroot',
> '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/',
> '--releasever', '25', 'install', '@buildsys-build', 'git', 'python',
> 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils',
> '--setopt=tsflags=nocontexts'] with env {'PS1': ' \\s-\\v\\$ ',
>
> DEBUG util.py:421: Yum command has been deprecated, use dnf instead.
> DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information.
> DEBUG util.py:421: Error: libcrypt conflicts with
> libcrypt-nss-2.24-3.fc25.x86_64
> DEBUG util.py:421: Error: libcrypt-nss conflicts with
> libcrypt-2.24-3.fc25.x86_64
> DEBUG util.py:421: You could try using --skip-broken to work around the
> problem
> DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest
> DEBUG util.py:557: Child return code was: 1
> DEBUG util.py:180: kill orphans
> {code}
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
eyal edri [Administrator] created OVIRT-967: --- Summary: add support for notification plugin in standard CI Key: OVIRT-967 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-967: Epic Link: OVIRT-400 > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24822#comment-24822 ] eyal edri [Administrator] commented on OVIRT-967: - Integration with GetBadges Gamification which is working nice until now with the GitHub integration, this will allow oVirt users/developers to get badges / points on having successful builds ( or lose on failing builds ). We already got positive feedback from developers on it, and adding another integration will increase visibility of the game [1] and hopefully make oVirt more fun to use/fix bugs/make ci happy. Fedora has something similar which works well [1] [1] https://badges.fedoraproject.org/ > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24823#comment-24823 ] eyal edri [Administrator] commented on OVIRT-967: - any project which will want to use it need to pass the URL as parameter > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24824#comment-24824 ] eyal edri [Administrator] commented on OVIRT-967: - Of course it doesn't only have to serve GetBadgets, we can use it in the future to capture events from Jenkins from other systems, one example will be a reporting system that can aggregate results into a cental datawarehouse which we can then create reports from. > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24825#comment-24825 ] eyal edri [Administrator] commented on OVIRT-967: - Forgot to add the link to the game: https://ovirt-ovirt-engine.getbadges.io/activity > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24832#comment-24832 ] eyal edri [Administrator] commented on OVIRT-967: - Not sure I understand, the current patch is as generic as it gets without any relation to getbadgets or gamification, If its merged nothing will happen on CI (already verified) because the URL for the webhook is empty by default. Only if you provide a URL as param from a project then its activated, for e.g for jenkins project: https://gerrit.ovirt.org/#/c/68903/1/jobs/confs/projects/jenkins/jenkins_standard.yaml The alternative is to create a new template for it and change multiple projects to use it if we want, which I don't see a reason for, if by default the plugin is not active. > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-967: --- Assignee: eyal edri [Administrator] (was: infra) > add support for notification plugin in standard CI > -- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: eyal edri [Administrator] > -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-968) Import image-tools in gerrit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-968: --- Assignee: eyal edri [Administrator] (was: infra) > Import image-tools in gerrit > > > Key: OVIRT-968 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-968 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: sbonazzo >Assignee: eyal edri [Administrator] > > Please import https://github.com/fabiand/image-tools.git > in ovirt gerrit. > Thanks, > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
[
https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] reassigned OVIRT-935:
---
Assignee: bkorren (was: infra)
> Unable to build fc25 chroots with mock
> --
>
> Key: OVIRT-935
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: bkorren
>
> Mock fails when trying to build the chroot for fedora25, on installing
> '@buildsys-build' group(with dnf) stage.
> Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781
> Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file.
> Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always
> install 'libcrypt' first.
> Until fixed this will block us from building anything with mock on fc25(hit
> it when trying to build fc25 RPMs for lago).
> Error logs:
> {code}
> DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated',
> '--installroot',
> '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/',
> '--releasever', '25', 'install', '@buildsys-build', 'git', 'python',
> 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils',
> '--setopt=tsflags=nocontexts'] with env {'PS1': ' \\s-\\v\\$ ',
>
> DEBUG util.py:421: Yum command has been deprecated, use dnf instead.
> DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information.
> DEBUG util.py:421: Error: libcrypt conflicts with
> libcrypt-nss-2.24-3.fc25.x86_64
> DEBUG util.py:421: Error: libcrypt-nss conflicts with
> libcrypt-2.24-3.fc25.x86_64
> DEBUG util.py:421: You could try using --skip-broken to work around the
> problem
> DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest
> DEBUG util.py:557: Child return code was: 1
> DEBUG util.py:180: kill orphans
> {code}
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-20) Document oVirt infra SLA
[ https://ovirt-jira.atlassian.net/browse/OVIRT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-20: -- Assignee: Evgheni Dereveanchin (was: infra) > Document oVirt infra SLA > - > > Key: OVIRT-20 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-20 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General >Reporter: quaid >Assignee: Evgheni Dereveanchin >Priority: Highest > > We need to document how we make changes: > * What services need notices out to the world? > * What are the timeframes for notices? > \\- 1 hour for critical > \\- 12 to 24 hours for non-critical > * Who needs to be notified for what? > \\- e.g. leave announce out of administrivia > \\- arch, users, and infra are the defaults so far > \\- perhaps create an infra-announce list that just includes the others? > * When do we not make changes? > \\- change freeze around releases > \\- other change freeze reasons > * What is the process to make a change during a freeze? > \\- When is the freeze slushy? > \\- When is the freeze solid and should not be broken because of the > potential risk at that moment? (We need something to weigh risk against risk.) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-226: Resolution: Won't Do (was: Won't Fix) Status: Done (was: To Do) Already tracked by QE, see more info on the Bugzilla bug. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins >Reporter: sbonazzo >Assignee: infra >Priority: Lowest > > Original request is on bugzilla: > https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-296) [jenkins] take offline faulty bad slaves
[ https://ovirt-jira.atlassian.net/browse/OVIRT-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-296: --- Assignee: Evgheni Dereveanchin (was: infra) > [jenkins] take offline faulty bad slaves > > > Key: OVIRT-296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-296 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins >Affects Versions: Test >Reporter: eyal edri [Administrator] >Assignee: Evgheni Dereveanchin > Labels: jenkins, monitoring, > > it seems that quite often we hit an issue with a specific slave on phx, due > to various reasons (out of space/git/network/etc..). > which leads to multiple jobs trying to run on it and failing. > we need an automated way of finding this. > proposal: > add post groovy build to jobs that will take a slave offline if it's > misbehaves using: > manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) > the trick is to find such a slave and to be able to know if it failed > consistently in the past X hours to justify it's disable. > we need some sort of counter or service to track slaves and thier error state > and according to it take offline a specific slave. > for example: > if a slave was failing x jobs in Y time and runtime was < Z min , it might > indicate such a problem. > (e.g 10 jobs were failing on the same slave in a timeframe of 5 min and job > runtime was less than a 1 min.. ) > the post script should email infra@ovirt.org that it disabled a slave and we > should look into it. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
[ https://ovirt-jira.atlassian.net/browse/OVIRT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-969: Epic Link: OVIRT-403 > Install new gerrit plugin: Gerrit webhooks plugin > - > > Key: OVIRT-969 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > > Info at https://github.com/GetBadges/gerrit-webhooks. > cc [~sbend...@redhat.com]. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
eyal edri [Administrator] created OVIRT-969: --- Summary: Install new gerrit plugin: Gerrit webhooks plugin Key: OVIRT-969 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Info at https://github.com/GetBadges/gerrit-webhooks. cc [~sbend...@redhat.com]. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-970: Epic Link: OVIRT-400 > Add support for GitHub projects in standard CI > -- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: eyal edri [Administrator] >Assignee: infra > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago > and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from > GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
eyal edri [Administrator] created OVIRT-970: --- Summary: Add support for GitHub projects in standard CI Key: OVIRT-970 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-970: --- Assignee: Pavel Zhukov (was: infra) This can get started regardless of the projects who wish to join, we need to have the support in templates,triggers,builders first, so when we want to add new projects, the templates will be ready. Most of the work should start at: (on jenkins repo) jobs/confs/yaml/triggers/github.yml jobs/confs/yaml/templates/standard-stage.yml > Add support for GitHub projects in standard CI > -- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: eyal edri [Administrator] >Assignee: Pavel Zhukov > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago > and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from > GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-974) Document ovirt.org hosting info and troubleshooting
[ https://ovirt-jira.atlassian.net/browse/OVIRT-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-974: Epic Link: OVIRT-403 > Document ovirt.org hosting info and troubleshooting > --- > > Key: OVIRT-974 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-974 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > > Currently ovirt.org is hosted on OpenShift gear and managed by OSAS. > We need to document the procedure on how to fix issues on it when they arrise > and list contact persons who can help. > [~ederevea] maybe documenting it on infra-docs is a good idea. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-974) Document ovirt.org hosting info and troubleshooting
eyal edri [Administrator] created OVIRT-974: --- Summary: Document ovirt.org hosting info and troubleshooting Key: OVIRT-974 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-974 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Currently ovirt.org is hosted on OpenShift gear and managed by OSAS. We need to document the procedure on how to fix issues on it when they arrise and list contact persons who can help. [~ederevea] maybe documenting it on infra-docs is a good idea. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-981) ovirt-release 4.1 doesn't build 4.1 experimental rpms
[ https://ovirt-jira.atlassian.net/browse/OVIRT-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-981: Epic Link: OVIRT-411 > ovirt-release 4.1 doesn't build 4.1 experimental rpms > - > > Key: OVIRT-981 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-981 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > > We have 4.1 experimental repos but we didn't create release rpm for them ( > missing the .in file on ovirt-4.1 branch ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-981) ovirt-release 4.1 doesn't build 4.1 experimental rpms
eyal edri [Administrator] created OVIRT-981: --- Summary: ovirt-release 4.1 doesn't build 4.1 experimental rpms Key: OVIRT-981 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-981 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We have 4.1 experimental repos but we didn't create release rpm for them ( missing the .in file on ovirt-4.1 branch ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-17) repoman should only sync el7 rpms
[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OST-17: Assignee: infra (was: eyal edri [Administrator]) > repoman should only sync el7 rpms > -- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only > test el7. > we should include only el7 x86_64 for now to save time and avoid errors when > network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-17) repoman should only sync el7 rpms
[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OST-17: Assignee: Daniel Belenky (was: infra) > repoman should only sync el7 rpms > -- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: Daniel Belenky >Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only > test el7. > we should include only el7 x86_64 for now to save time and avoid errors when > network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-17) repoman should only sync el7 rpms
[ https://ovirt-jira.atlassian.net/browse/OST-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24951#comment-24951 ] eyal edri [Administrator] commented on OST-17: -- +1 if it can evaluate $distro when it runs. > repoman should only sync el7 rpms > -- > > Key: OST-17 > URL: https://ovirt-jira.atlassian.net/browse/OST-17 > Project: oVirt system tests > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > on OST jobs repoman also syncs fc24 rpms without any reason, since we only > test el7. > we should include only el7 x86_64 for now to save time and avoid errors when > network is unstable. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental
[ https://ovirt-jira.atlassian.net/browse/OVIRT-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25003#comment-25003 ] eyal edri [Administrator] commented on OVIRT-985: - [~gshinar] please add the relevant failing job ( mark it to keep forever ) and paste the exception here. > Fix the way repoman deploy to experimental > -- > > Key: OVIRT-985 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Gil Shinar >Assignee: infra > > Please consult with Eyal on that. > No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-984) Add emails to deploy to experimental jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-984: --- Assignee: Pavel Zhukov (was: infra) > Add emails to deploy to experimental jobs > - > > Key: OVIRT-984 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-984 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Gil Shinar >Assignee: Pavel Zhukov > > When deploy to experimental fails, we need to alert. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-986) remove gerrit hooks from infra repos
[ https://ovirt-jira.atlassian.net/browse/OVIRT-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-986: Epic Link: OVIRT-411 > remove gerrit hooks from infra repos > > > Key: OVIRT-986 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-986 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > > We don't need to run oVirt gerrit hooks on infra repos like gerrit-admin or > jenkins since we don't use bugzilla for tracking issues. > We might want to add support for JIRA ticket added to a commit msg for > handling infra repos, but that should require another ticket, for now we just > need to remove the hooks from projects which are not relevant like > jenkins,infra-docs,infra-puppet,gerrit-admin and others -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-986) remove gerrit hooks from infra repos
eyal edri [Administrator] created OVIRT-986: --- Summary: remove gerrit hooks from infra repos Key: OVIRT-986 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-986 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We don't need to run oVirt gerrit hooks on infra repos like gerrit-admin or jenkins since we don't use bugzilla for tracking issues. We might want to add support for JIRA ticket added to a commit msg for handling infra repos, but that should require another ticket, for now we just need to remove the hooks from projects which are not relevant like jenkins,infra-docs,infra-puppet,gerrit-admin and others -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-449) Add junit report to ovirt-engine standard ci
[ https://ovirt-jira.atlassian.net/browse/OVIRT-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-449: --- Assignee: eyal edri [Administrator] (was: infra) > Add junit report to ovirt-engine standard ci > > > Key: OVIRT-449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-449 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: David Caro Estevez >Assignee: eyal edri [Administrator] >Priority: Low > > Currently there are to ways of doing it: > * Using a special job template for ovirt-engine (easy to do now, hard to > maintain/reuse) > * Using jenkins pipeline plugin to dynamically add it to any job that > generates a report (hard to do right now, easy to maintain/reuse) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental
[ https://ovirt-jira.atlassian.net/browse/OVIRT-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25018#comment-25018 ] eyal edri [Administrator] commented on OVIRT-985: - we need longer history, please update the deploy experimental job to keep history for 14 days ( other projects were updated already ) > Fix the way repoman deploy to experimental > -- > > Key: OVIRT-985 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Gil Shinar >Assignee: infra > > Please consult with Eyal on that. > No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
eyal edri [Administrator] created OVIRT-990: --- Summary: Re: Gerrit don't check for "Signed-Off" anymore Key: OVIRT-990 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan wrote: > Last night I've push a serious of patches and forgot to sign off, up until > not long ago there was a hook that enforces that but it seems like it's not > working anymore and I was able to push the patches without the sign off: > https://gerrit.ovirt.org/#/c/69219/1 > > Its not a hook, its a definition per project, each project has the defenition if to enforce signed-off commit: 'Require Signed-off-by in commit message:' - and its on TRUE now for ovirt-engine, so I'm not sure how its possible that a patch got in, we'll need to check gerrit logs to see. Opening a ticket on it. > > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25030#comment-25030 ] eyal edri [Administrator] commented on OVIRT-990: - [~tni...@redhat.com] the permission needed to rebase on other commits is 'forge author identity' and that is still valid for all registered uses. > Re: Gerrit don't check for "Signed-Off" anymore > --- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-834) checkout keen dashboard for oVirt services
[ https://ovirt-jira.atlassian.net/browse/OVIRT-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25031#comment-25031 ] eyal edri [Administrator] commented on OVIRT-834: - A suggestion raised to add one useful dashboard view is on uptime on oVirt version stability taken from the OST experimental job, So the dashboard will contain block per version with the following info: oVirt master is stable for [ X hours+min ] ( link to last successful job + name of authors from commits who triggered the job ] if not stable: oVirt master is broken for [ X hours+min ] ( link to job with the failure, link to patch(es) suspected of failure, list of authors of patches ) One option is to use [1], but its not an official dashboard, so we might want to wait for Jenkins 2.0 upgrade or Blue Ocean\ [1] https://jenkins.io/blog/2016/01/10/beautiful-jenkins-dashboard/ > checkout keen dashboard for oVirt services > -- > > Key: OVIRT-834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-834 > Project: oVirt - virtualization made easy > Issue Type: New Feature >Reporter: eyal edri [Administrator] >Assignee: infra > > https://github.com/keen/dashboards -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-991) vdsm master check-patch not run on https://gerrit.ovirt.org/#/c/69032/5
[ https://ovirt-jira.atlassian.net/browse/OVIRT-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25032#comment-25032 ] eyal edri [Administrator] commented on OVIRT-991: - Jenkins was just restarted, when was the job triggered? can you try triggering it with the manual trigger job or via rebase? On Dec 28, 2016 7:20 PM, "danken (oVirt JIRA)" < > vdsm master check-patch not run on https://gerrit.ovirt.org/#/c/69032/5 > --- > > Key: OVIRT-991 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-991 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: danken >Assignee: infra > > https://gerrit.ovirt.org/#/c/69032/4 as well. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25037#comment-25037
]
eyal edri [Administrator] commented on OVIRT-973:
-
[~vojtech][~sbonazo...@redhat.com] not sure if we want to add this, but we may
want to add update the current macro in Makefile to do also chrome, WDYT?
> nightly ovirt-engine build is missing Chrome permutation
>
>
> Key: OVIRT-973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
>Reporter: Greg Sheremeta
>Assignee: infra
>
> mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that
> the nightly ovirt-engine build is missing the Chrome permutation.
> From the
> [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/2068/consoleFull]:
> {noformat}
> 21:13:24 [INFO]Compiling 1 permutation
> 21:13:24 [INFO] Compiling permutation 0...
> 21:16:54 [INFO]Compile of permutations succeeded
> {noformat}
> That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
> mburman reports this started on November 30. I'm not sure what changed.
> Adding build flags will fix:
> DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-903: --- Assignee: Daniel Belenky (was: infra) reminder to add to upgrade suites > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: Daniel Belenky > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-993) add manual jobs for OST to allow running on custom repos
[ https://ovirt-jira.atlassian.net/browse/OVIRT-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-993: Epic Link: OVIRT-400 > add manual jobs for OST to allow running on custom repos > > > Key: OVIRT-993 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-993 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: High > > It has been requested by dev to be able to run easily OST jobs on an open > patch(es). > We plan to refactor experimental flow completely when we move to Zuul, but it > will take some time until we have a new job fully working that we can utilize > also to allow manual testing. > Fortunately we recently added new 'build-on-demand' jobs which adds > capability to generate new rpms from any open patch. > With some effort, we can utilize existing system jobs to accept custom repo > list and run on rpms created by the 'build-on-demand' jobs using repoman. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-993) add manual jobs for OST to allow running on custom repos
eyal edri [Administrator] created OVIRT-993: --- Summary: add manual jobs for OST to allow running on custom repos Key: OVIRT-993 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-993 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High It has been requested by dev to be able to run easily OST jobs on an open patch(es). We plan to refactor experimental flow completely when we move to Zuul, but it will take some time until we have a new job fully working that we can utilize also to allow manual testing. Fortunately we recently added new 'build-on-demand' jobs which adds capability to generate new rpms from any open patch. With some effort, we can utilize existing system jobs to accept custom repo list and run on rpms created by the 'build-on-demand' jobs using repoman. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-993) add manual jobs for OST to allow running on custom repos
[ https://ovirt-jira.atlassian.net/browse/OVIRT-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-993: --- Assignee: eyal edri [Administrator] (was: infra) > add manual jobs for OST to allow running on custom repos > > > Key: OVIRT-993 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-993 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: eyal edri [Administrator] >Priority: High > > It has been requested by dev to be able to run easily OST jobs on an open > patch(es). > We plan to refactor experimental flow completely when we move to Zuul, but it > will take some time until we have a new job fully working that we can utilize > also to allow manual testing. > Fortunately we recently added new 'build-on-demand' jobs which adds > capability to generate new rpms from any open patch. > With some effort, we can utilize existing system jobs to accept custom repo > list and run on rpms created by the 'build-on-demand' jobs using repoman. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25075#comment-25075
]
eyal edri [Administrator] commented on OVIRT-973:
-
How much time it will add if we'll add chrome to the permutations? I wouldn't
want to pay a constant time penalty just because a single manual test needed it.
> nightly ovirt-engine build is missing Chrome permutation
>
>
> Key: OVIRT-973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
>Reporter: Greg Sheremeta
>Assignee: infra
>
> mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that
> the nightly ovirt-engine build is missing the Chrome permutation.
> From the
> [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/2068/consoleFull]:
> {noformat}
> 21:13:24 [INFO]Compiling 1 permutation
> 21:13:24 [INFO] Compiling permutation 0...
> 21:16:54 [INFO]Compile of permutations succeeded
> {noformat}
> That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
> mburman reports this started on November 30. I'm not sure what changed.
> Adding build flags will fix:
> DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25076#comment-25076
]
eyal edri [Administrator] commented on OVIRT-973:
-
You can easily send a patch to build-artifacts with the permutations you want
and then use the 'build-on-demand' job using 'ci please build' to build rpms
using the new PARAMS.
> nightly ovirt-engine build is missing Chrome permutation
>
>
> Key: OVIRT-973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
>Reporter: Greg Sheremeta
>Assignee: infra
>
> mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that
> the nightly ovirt-engine build is missing the Chrome permutation.
> From the
> [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/2068/consoleFull]:
> {noformat}
> 21:13:24 [INFO]Compiling 1 permutation
> 21:13:24 [INFO] Compiling permutation 0...
> 21:16:54 [INFO]Compile of permutations succeeded
> {noformat}
> That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
> mburman reports this started on November 30. I'm not sure what changed.
> Adding build flags will fix:
> DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-998) Re: Enable Github gh-pages for project ovirt-engine-api-model
eyal edri [Administrator] created OVIRT-998: --- Summary: Re: Enable Github gh-pages for project ovirt-engine-api-model Key: OVIRT-998 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-998 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Sending ticket to infra-support. Pavel - let me know if you need help, its just clicking on the gh-pages generate button on GitHub ( last time we did it for SDK ) On Mon, Jan 2, 2017 at 11:43 PM, Juan Hernández wrote: > Hello, > > In order to have a public and stable location for the documentation of > the API I would like to start using the Github gh-pages mechanism. I > have already created a 'gh-pages' branch in the 'ovirt-engine-api-model' > project, and merged to that branch the first version of the > documentation. The next step is to enable the use of that 'gh-pages' > branch as the source of the documentation in the settins of that > project. But that needs to be done by an administrator of the oVirt > organization. Would you be so kind to do that? > > Thanks in advance, > Juan Hernandez > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25080#comment-25080 ] eyal edri [Administrator] commented on OVIRT-990: - [~tni...@redhat.com] any open issues still or we can close this? > Re: Gerrit don't check for "Signed-Off" anymore > --- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental
[ https://ovirt-jira.atlassian.net/browse/OVIRT-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-985: Resolution: Cannot Reproduce Status: Done (was: To Do) since we don't have link to the failing job, we'll need to wait until next time it happens. > Fix the way repoman deploy to experimental > -- > > Key: OVIRT-985 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Gil Shinar >Assignee: infra > > Please consult with Eyal on that. > No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-956) trigger jobs on jenkins
[ https://ovirt-jira.atlassian.net/browse/OVIRT-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-956: Resolution: Fixed Status: Done (was: To Do) > trigger jobs on jenkins > --- > > Key: OVIRT-956 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-956 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yuval Turgeman >Assignee: infra > > Hi, > Can I please get permissions to trigger jobs in jenkin ? > I need to trigger this one: > http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-pre_build-artifacts-el7-x86_64/56/ > Thanks, > Yuval. -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
[ https://ovirt-jira.atlassian.net/browse/OVIRT-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-999: Epic Link: OVIRT-400 > experimental 4.1 tests work even though rpms where missing from repos > - > > Key: OVIRT-999 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > We need to find out why experimetnal flow 4.1 worked although it had missing > RPMs. > My guess is that repoman is using latest-snapshot to complete missing rpms, > we need to stop taking rpms from snapshot repos and only take from snapshot > static -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
eyal edri [Administrator] created OVIRT-999: --- Summary: experimental 4.1 tests work even though rpms where missing from repos Key: OVIRT-999 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest We need to find out why experimetnal flow 4.1 worked although it had missing RPMs. My guess is that repoman is using latest-snapshot to complete missing rpms, we need to stop taking rpms from snapshot repos and only take from snapshot static -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
[ https://ovirt-jira.atlassian.net/browse/OVIRT-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-999: --- Assignee: Daniel Belenky (was: infra) > experimental 4.1 tests work even though rpms where missing from repos > - > > Key: OVIRT-999 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: Daniel Belenky >Priority: Highest > > We need to find out why experimetnal flow 4.1 worked although it had missing > RPMs. > My guess is that repoman is using latest-snapshot to complete missing rpms, > we need to stop taking rpms from snapshot repos and only take from snapshot > static -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-990: Resolution: Fixed Status: Done (was: To Do) > Re: Gerrit don't check for "Signed-Off" anymore > --- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25087#comment-25087 ] eyal edri [Administrator] commented on OVIRT-1000: -- [~j...@redhat.com][~omach...@redhat.com] we have too many hacks right now to make SDK work on the same repos for V3 and V4. We can't continue to do it as you see it generate problems. We need to decide on a split of repos so each project will have its own repo ( it already has its own name and differnet rpm version ). otherwise we're bound to keep hitting issues with this setup. > Java SDK 4.1 branch don't execute jenkins jobs > -- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Ondra Machacek >Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK > project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not > sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25090#comment-25090 ] eyal edri [Administrator] commented on OVIRT-1000: -- There shouldn't be a problem to keep existing repos, we will just not build from them in CI, but no problem to keep the old branches in place. Yea, creating new projects and new jobs will give us flexibility to keep existing status in tact until we switch to new repos + jobs. > Java SDK 4.1 branch don't execute jenkins jobs > -- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Ondra Machacek >Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK > project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not > sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25092#comment-25092 ] eyal edri [Administrator] commented on OVIRT-1000: -- I thought we would leave all current repos alone and create new projects both for v3 and v4, keeping the old repo for new version is a problem, since we have a diff between repo name and rpm names > Java SDK 4.1 branch don't execute jenkins jobs > -- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Ondra Machacek >Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK > project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not > sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] updated OVIRT-973:
Summary: add support for custom build params on build-on-demand jobs (was:
nightly ovirt-engine build is missing Chrome permutation)
> add support for custom build params on build-on-demand jobs
> ---
>
> Key: OVIRT-973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
>Reporter: Greg Sheremeta
>Assignee: infra
>
> mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that
> the nightly ovirt-engine build is missing the Chrome permutation.
> From the
> [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/2068/consoleFull]:
> {noformat}
> 21:13:24 [INFO]Compiling 1 permutation
> 21:13:24 [INFO] Compiling permutation 0...
> 21:16:54 [INFO]Compile of permutations succeeded
> {noformat}
> That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
> mburman reports this started on November 30. I'm not sure what changed.
> Adding build flags will fix:
> DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25097#comment-25097
]
eyal edri [Administrator] commented on OVIRT-973:
-
I changed the job to add support for it, but its not trivial and not sure when
we can do it,
If someone needs a specific build, he'll need to run it locally for now or send
a patch like suggested in this ticket
> add support for custom build params on build-on-demand jobs
> ---
>
> Key: OVIRT-973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
>Reporter: Greg Sheremeta
>Assignee: infra
>
> mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that
> the nightly ovirt-engine build is missing the Chrome permutation.
> From the
> [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/2068/consoleFull]:
> {noformat}
> 21:13:24 [INFO]Compiling 1 permutation
> 21:13:24 [INFO] Compiling permutation 0...
> 21:16:54 [INFO]Compile of permutations succeeded
> {noformat}
> That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
> mburman reports this started on November 30. I'm not sure what changed.
> Adding build flags will fix:
> DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25098#comment-25098 ] eyal edri [Administrator] commented on OVIRT-1000: -- So what do you suggest? can you layout the new repos/name you'd like to see for V3+V4 and where they should be built? > Java SDK 4.1 branch don't execute jenkins jobs > -- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Ondra Machacek >Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK > project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not > sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25099#comment-25099 ] eyal edri [Administrator] commented on OVIRT-1001: -- Usually the maintainer of the project does it from GitHub, So you just need to permission updated - who should be the maintainer on the GitHub project? > GitHub token for ovirt-engine-api-model and Travis CI > - > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Petr Horacek >Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25101#comment-25101 ] eyal edri [Administrator] commented on OVIRT-1001: -- done, you should have admin rights on that repo now. > GitHub token for ovirt-engine-api-model and Travis CI > - > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Petr Horacek >Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-1001: - Resolution: Fixed Status: Done (was: To Do) > GitHub token for ovirt-engine-api-model and Travis CI > - > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Petr Horacek >Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1007) repo closure jobs failed to find missing pkg on experimental 4.1
eyal edri [Administrator] created OVIRT-1007: Summary: repo closure jobs failed to find missing pkg on experimental 4.1 Key: OVIRT-1007 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1007) repo closure jobs failed to find missing pkg on experimental 4.1
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-1007: - Epic Link: OVIRT-400 > repo closure jobs failed to find missing pkg on experimental 4.1 > > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-1007: - Summary: repo closure job should find also optional pkg (was: repo closure jobs failed to find missing pkg on experimental 4.1) > repo closure job should find also optional pkg > -- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25211#comment-25211 ] eyal edri [Administrator] commented on OVIRT-1007: -- The job should: 1. monitoring experimental reops ( right now it checks only snapshot ) 2. detect any missing rpms that are also optional ( maybe compare to stable version? ) > repo closure job should find also optional pkg > -- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: eyal edri [Administrator] >Assignee: infra >Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-998) Re: Enable Github gh-pages for project ovirt-engine-api-model
[ https://ovirt-jira.atlassian.net/browse/OVIRT-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-998: --- Assignee: Pavel Zhukov (was: infra) > Re: Enable Github gh-pages for project ovirt-engine-api-model > - > > Key: OVIRT-998 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-998 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Pavel Zhukov > > Sending ticket to infra-support. > Pavel - let me know if you need help, its just clicking on the gh-pages > generate button on GitHub ( last time we did it for SDK ) > On Mon, Jan 2, 2017 at 11:43 PM, Juan Hernández wrote: > > Hello, > > > > In order to have a public and stable location for the documentation of > > the API I would like to start using the Github gh-pages mechanism. I > > have already created a 'gh-pages' branch in the 'ovirt-engine-api-model' > > project, and merged to that branch the first version of the > > documentation. The next step is to enable the use of that 'gh-pages' > > branch as the source of the documentation in the settins of that > > project. But that needs to be done by an administrator of the oVirt > > organization. Would you be so kind to do that? > > > > Thanks in advance, > > Juan Hernandez > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.670.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1011) Please add omachace as project maintainer for ovirt-engine-sdk project on Github
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-1011: - Resolution: Fixed Assignee: eyal edri [Administrator] (was: infra) Status: Done (was: To Do) > Please add omachace as project maintainer for ovirt-engine-sdk project on > Github > > > Key: OVIRT-1011 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1011 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Ondra Machacek >Assignee: eyal edri [Administrator] > > Hi, > can you please add me (omach...@redhat.com) as project maintainer > in github for ovirt-engine-sdk. > We would like to setup automatic build of SDK documentation. > Thank you. -- This message was sent by Atlassian JIRA (v1000.670.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-912) Brand oVirt Gerrit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-912: --- Assignee: Evgheni Dereveanchin (was: infra) > Brand oVirt Gerrit > -- > > Key: OVIRT-912 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-912 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git >Reporter: Barak Korren >Assignee: Evgheni Dereveanchin > Labels: branding, gerrit, look-and-feel > > It is not branded - we need to brand it so it feels more like what it is - > oVirt's development home. > We need to find ways to make people proud to belong to a project big enough > to have its own code hosting, instead of constantly looking to GitHub. (Maybe > this should be an epic) > Look at OpenStack's Gerrit for example: > https://review.openstack.org/#/q/status:open -- This message was sent by Atlassian JIRA (v1000.670.2#100024) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-682) Improve CI logging
[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-682: Summary: Improve CI logging (was: Improve CI logging - check if its possible to include mock errors in console output) > Improve CI logging > -- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: eyal edri [Administrator] > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.20160829.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.20160829.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.692.0#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-682) Improve CI logging
[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25608#comment-25608 ] eyal edri [Administrator] commented on OVIRT-682: - some improvements were added recently to mock runner, but there is more we can do to simplify the output of jobs to ease debugging. keeping this as place holder for any improvement we'll add or consider > Improve CI logging > -- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: eyal edri [Administrator] > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.20160829.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.20160829.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.692.0#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-682) Improve CI logging
[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-682: Status: To Do (was: In Progress) > Improve CI logging > -- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: eyal edri [Administrator] > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.20160829.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.20160829.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.692.0#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1024) Re: github ovirt project sync
eyal edri [Administrator] created OVIRT-1024: Summary: Re: github ovirt project sync Key: OVIRT-1024 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1024 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Because its not enabled by default, only by request as its a manual process. Adding infra-support to create a ticket on it. On Thu, Jan 12, 2017 at 5:41 PM, Yaniv Bronheim wrote: > do you know maybe why doesn't ovirt github in sync with the gerrit? ( > https://github.com/ovirt/ovirt-container-node) > > Thanks. > > -- > *Yaniv Bronhaim.* > > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.692.0#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-1028: Assignee: infra (was: eyal edri [Administrator]) > Configure experimental job with ANSI output - so it'd be easier to look at > -- > > Key: OVIRT-1028 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1028 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Yaniv Kaul >Assignee: infra > Labels: jenkins > > O-S-T uses ANSI colors for easier output. For some reason, some jobs aren't > configured with it. > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_master/4739/console > is such an example. -- This message was sent by Atlassian JIRA (v1000.695.1#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25713#comment-25713
]
eyal edri [Administrator] commented on OVIRT-1028:
--
Possible solution using the AnsiColor build wrapper:
https://jenkins.io/doc/pipeline/examples:
// This shows a simple build wrapper example, using the AnsiColorBuildWrapper
plugin.
node {
// This is the current syntax for invoking a build wrapper, naming the
class.
wrap([$class: 'AnsiColorBuildWrapper']) {
// Just some echoes to show the ANSI color.
stage "\u001B[31mI'm Red\u001B[0m Now not"
}
}
> Configure experimental job with ANSI output - so it'd be easier to look at
> --
>
> Key: OVIRT-1028
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1028
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Yaniv Kaul
>Assignee: infra
> Labels: jenkins
>
> O-S-T uses ANSI colors for easier output. For some reason, some jobs aren't
> configured with it.
> http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_master/4739/console
> is such an example.
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-1028: - Labels: experimental jenkins system-tests (was: jenkins) > Configure experimental job with ANSI output - so it'd be easier to look at > -- > > Key: OVIRT-1028 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1028 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Yaniv Kaul >Assignee: infra > Labels: experimental, jenkins, system-tests > > O-S-T uses ANSI colors for easier output. For some reason, some jobs aren't > configured with it. > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_master/4739/console > is such an example. -- This message was sent by Atlassian JIRA (v1000.695.1#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25715#comment-25715 ] eyal edri [Administrator] commented on OVIRT-1028: -- the check-patch isn't using the pipeline plugin, its a normal free type job and it uses the AnsiColor plugin, so its not comparable to the experimental jobs. > Configure experimental job with ANSI output - so it'd be easier to look at > -- > > Key: OVIRT-1028 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1028 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Yaniv Kaul >Assignee: infra > Labels: experimental, jenkins, system-tests > > O-S-T uses ANSI colors for easier output. For some reason, some jobs aren't > configured with it. > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_master/4739/console > is such an example. -- This message was sent by Atlassian JIRA (v1000.695.1#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1031) check why proxy was not reachable casuing repoman to fail on OST job
eyal edri [Administrator] created OVIRT-1031:
Summary: check why proxy was not reachable casuing repoman to fail
on OST job
Key: OVIRT-1031
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1031
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: eyal edri [Administrator]
Assignee: infra
http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_4.1/253/artifact/exported-artifacts/basic_suite_4.1.sh-el7/exported-artifacts/lago_logs/lago.log
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 576, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 424, in
send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError:
HTTPConnectionPool(host='proxy.phx.ovirt.org', port=3128): Max retries exceeded
with url:
http://plain.resources.ovirt.org/repos/ovirt/experimental/4.1/latest.under_testing/rpm//el7Server//SRPMS//ovirt-setup-lib-1.1.0-1.20170103120007.git402fec4.el7.centos.src.rpm
(Caused by ProxyError('Cannot connect to proxy.', error(111, 'Connection
refused')))
2017-01-14 12:57:00,751::INFO::repoman.common.repo::Cleaning up temporary dir
/tmp/tmpKfWNmc
2017-01-14 12:57:00,766::utils.py::run_command::226::lago.utils::DEBUG::command
exit with 1
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
