March 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-411) Any build or release of oVirt
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-411?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-411: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > Any build or release of oVirt > ----------------------------- > > Key: OVIRT-411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-411 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > Any task related to release or builds. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-384) DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-384?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-384: ----------------------------------------------- Assignee: snaftaly (was: infra) > DB upgrade jobs are not using engine-setup > ------------------------------------------ > > Key: OVIRT-384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-384 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eli Mesika > Assignee: snaftaly > > Hi > > Currently DB upgrade jobs are using schema.sh script and not engine-setup > This may cause CI upgrade tests to be successful while they are actually > failed when running from engine-setup > Since we are using engine-setup to upgrade the database, CI tests must use > the same exact method in order to be reliable > I had faced this week 2 different cases when my patches passed CI but failed > actually engine-setup causing a loose of time to me and to other that > already rebased on a problematic patch. > > > Thanks > Eli Mesika -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-386) puppet-agent not stopped even after it's disabled
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-386?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-386: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > puppet-agent not stopped even after it's disabled > ------------------------------------------------- > > Key: OVIRT-386 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-386 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: eyal edri [Administrator] > > Subject was: > Re: [oVirt Jenkins] ovirt-engine_3.6_upgrade-from-3.5_el6_merged - > Build # 814 - Still Failing! > On Wed, Jan 20, 2016 at 11:46 AM, Yedidyah Bar David <didi(a)redhat.com> wrote: > > On Tue, Jan 19, 2016 at 6:20 PM, <jenkins(a)ovirt.org> wrote: > >> Project: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/ > >> Build: http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/8… > > > > Might be affected by puppet? > > > > Sandro sent me a sosreport, /var/log/messages has there: > > > > Jan 19 14:27:57 el6-vm07 puppet-agent[30215]: Disabling Puppet. > > Jan 19 14:30:36 el6-vm07 puppet-agent[6849]: Finished catalog run in > > 159.80 seconds > > Jan 19 15:22:17 el6-vm07 dhclient[1063]: DHCPREQUEST on eth0 to > > 66.187.230.11 port 67 (xid=0x4649ae69) > > Jan 19 15:22:17 el6-vm07 dhclient[1063]: DHCPACK from 66.187.230.11 > > (xid=0x4649ae69) > > Jan 19 15:22:23 el6-vm07 dhclient[1063]: bound to 66.187.230.59 -- > > renewal in 14843 seconds. > > Jan 19 15:29:02 el6-vm07 puppet-agent[6849]: Finished catalog run in > > 1771.73 seconds > > Jan 19 15:32:43 el6-vm07 puppet-agent[6849]: Finished catalog run in > > 63.61 seconds > > Jan 19 15:47:36 el6-vm07 yum[29322]: Erased: postgresql-server > > Jan 19 15:48:50 el6-vm07 yum[29369]: Installed: > > postgresql-server-8.4.20-4.el6_7.x86_64 > > Jan 19 15:53:08 el6-vm07 yum[29581]: Installed: > > httpd-2.2.15-47.el6.centos.1.x86_64 > > Jan 19 15:53:14 el6-vm07 yum[29581]: Installed: > > 1:mod_ssl-2.2.15-47.el6.centos.1.x86_64 > > Jan 19 15:58:19 el6-vm07 yum[29613]: Installed: > > ovirt-engine-lib-3.5.6.2-1.el6.noarch > > Jan 19 15:58:58 el6-vm07 yum[29613]: Installed: > > ovirt-engine-sdk-python-3.5.6.0-1.el6.noarch > > Jan 19 15:59:20 el6-vm07 yum[29613]: Installed: > > ovirt-iso-uploader-3.5.2-1.el6.noarch > > Jan 19 15:59:27 el6-vm07 yum[29613]: Installed: > > ovirt-engine-cli-3.5.0.6-1.el6.noarch > > Jan 19 15:59:39 el6-vm07 yum[29613]: Installed: > > ovirt-image-uploader-3.5.1-1.el6.noarch > > Jan 19 15:59:52 el6-vm07 yum[29613]: Installed: > > ovirt-engine-setup-base-3.5.6.2-1.el6.noarch > > Jan 19 16:00:06 el6-vm07 yum[29613]: Installed: > > ovirt-engine-setup-plugin-ovirt-engine-common-3.5.6.2-1.el6.noarch > > Jan 19 16:00:25 el6-vm07 yum[29613]: Installed: > > ovirt-engine-setup-plugin-websocket-proxy-3.5.6.2-1.el6.noarch > > Jan 19 16:00:33 el6-vm07 yum[29613]: Installed: > > ovirt-engine-websocket-proxy-3.5.6.2-1.el6.noarch > > Jan 19 16:00:36 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_ident.conf]/content) content changed > > '{md5}3b96a52aed8884a160d7855d0c080c20' to > > '{md5}9300ac105fe777787ac9e793b8df8d25' > > Jan 19 16:00:36 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_ident.conf]/mode) mode changed '0600' to > > '0640' > > Jan 19 16:00:36 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_ident.conf]/seluser) seluser changed > > 'unconfined_u' to 'system_u' > > Jan 19 16:00:51 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_hba.conf]/content) content changed > > '{md5}1054a721225d54243d0877dc32c7db19' to > > '{md5}085d05a044adfa878bb08669f787c473' > > Jan 19 16:00:51 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_hba.conf]/mode) mode changed '0600' to > > '0640' > > Jan 19 16:00:51 el6-vm07 puppet-agent[6849]: > > (/File[/var/lib/pgsql/data/pg_hba.conf]/seluser) seluser changed > > 'unconfined_u' to 'system_u' > > Jan 19 16:00:52 el6-vm07 puppet-agent[6849]: > > (/Stage[main]/Postgresql::Server::Service/Service[postgresqld]/enable) > > enable changed 'false' to 'true' > > Jan 19 16:00:53 el6-vm07 puppet-agent[6849]: > > (/Stage[main]/Postgresql::Server::Reload/Exec[postgresql_reload]) > > Triggered 'refresh' from 1 events > > Jan 19 16:00:54 el6-vm07 puppet-agent[6849]: Finished catalog run in > > 62.08 seconds > > Jan 19 16:01:04 el6-vm07 yum[29613]: Installed: > > ovirt-engine-jboss-as-7.1.1-1.el6.x86_64 > > Jan 19 16:01:08 el6-vm07 yum[29613]: Installed: > > ovirt-engine-extensions-api-impl-3.5.6.2-1.el6.noarch > > Jan 19 16:01:21 el6-vm07 yum[29613]: Installed: > > vdsm-jsonrpc-java-1.0.15-1.el6.noarch > > Jan 19 16:02:54 el6-vm07 yum[29613]: Installed: > > ovirt-engine-userportal-3.5.6.2-1.el6.noarch > > Jan 19 16:02:57 el6-vm07 yum[29613]: Installed: > > ovirt-engine-tools-3.5.6.2-1.el6.noarch > > Jan 19 16:03:04 el6-vm07 yum[29613]: Installed: > > ovirt-engine-setup-3.5.6.2-1.el6.noarch > > Jan 19 16:03:06 el6-vm07 yum[29613]: Installed: > > ovirt-engine-setup-plugin-ovirt-engine-3.5.6.2-1.el6.noarch > > Jan 19 16:03:12 el6-vm07 yum[29613]: Installed: > > ovirt-engine-dbscripts-3.5.6.2-1.el6.noarch > > Jan 19 16:03:20 el6-vm07 yum[29613]: Installed: > > ovirt-engine-backend-3.5.6.2-1.el6.noarch > > Jan 19 16:03:21 el6-vm07 yum[29613]: Installed: > > ovirt-engine-restapi-3.5.6.2-1.el6.noarch > > Jan 19 16:03:42 el6-vm07 yum[29613]: Installed: > > ovirt-engine-webadmin-portal-3.5.6.2-1.el6.noarch > > Jan 19 16:03:48 el6-vm07 yum[29613]: Installed: > > ovirt-engine-3.5.6.2-1.el6.noarch > > Jan 19 16:08:26 el6-vm07 puppet-agent[30732]: Enabling Puppet. > > > > Perhaps something slowed down puppet-agent so it finished doing its stuff after > > it was disabled. > > > >> Build Number: 814 > >> Build Status: Still Failing > >> Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/52416 > >> > >> ------------------------------------- > >> Changes Since Last Success: > >> ------------------------------------- > >> Changes for Build #812 > >> [Scott J Dickerson] webadmin: auto-scroll SetupNetworks interfaces list during > >> > >> > >> Changes for Build #813 > >> [Alona Kaplan] engine: both null and empty gateway should be considered as no gateway > >> > >> [Sharon Naftaly] Adding engine pacakge variable to upgrade jobs > >> > >> > >> Changes for Build #814 > >> [Yedidyah Bar David] packaging: rename: fixes for vmconsole proxy helper > >> > >> [David Caro] vdsm-jsonrpc-java:Added standard ci jobs > >> > >> > >> > >> > >> ----------------- > >> Failed Tests: > >> ----------------- > >> No tests ran. > >> > > > > > > > > -- > > Didi > -- > Didi -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-383: ----------------------------------------------- Assignee: snaftaly (was: infra) > Re: DB upgrade jobs are not using engine-setup > ---------------------------------------------- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri <eedri(a)redhat.com> wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scr… > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika <emesika(a)redhat.com> wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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 (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-400) various improvement and new jobs required for oVirt projects
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-400?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-400: -------------------------------------------- Epic Name: oVirt Continuous Integration (was: Misc CI tasks for oVirt ) > various improvement and new jobs required for oVirt projects > ------------------------------------------------------------ > > Key: OVIRT-400 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-400 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: Jenkins > Reporter: eyal edri [Administrator] > Assignee: infra > > This epic should include all tasks related to adding more CI jobs for various oVirt project, > improvements for CI, and anything that isn't related to the infra itself or hosting. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-400) various improvement and new jobs required for oVirt projects
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-400?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-400: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > various improvement and new jobs required for oVirt projects > ------------------------------------------------------------ > > Key: OVIRT-400 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-400 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: Jenkins > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > This epic should include all tasks related to adding more CI jobs for various oVirt project, > improvements for CI, and anything that isn't related to the infra itself or hosting. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-404) Any doc task related to the team/project
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-404?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-404: -------------------------------------------- > Any doc task related to the team/project > ---------------------------------------- > > Key: OVIRT-404 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-404 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-405) any request made to infra-support
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-405?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-405: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > any request made to infra-support > ---------------------------------- > > Key: OVIRT-405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-405 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > first tier bucket for support tickets requested from the team. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-169) Lists of server and services
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-169?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-169: -------------------------------------------- Priority: Highest > Lists of server and services > ---------------------------- > > Key: OVIRT-169 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-169 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: misc > Assignee: infra > Priority: Highest > > We need to have a lists of server and services, so we can know what is not in foreman, what is not supervised, and what backup are missing. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-306) [wiki] write a wiki page on how developer can add a jenkins job via jjb
by eyal edri [Administrator] (oVirt JIRA) 14 Mar '16

14 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-306?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-306: -------------------------------------------- Priority: Highest > [wiki] write a wiki page on how developer can add a jenkins job via jjb > ----------------------------------------------------------------------- > > Key: OVIRT-306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-306 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > we need a wiki explaining how to add a new job in jenkins via jjb. > it should be easy to anyone not familiar with jjb. > should contain guidelines on naming conventions and code in the job as well. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0