November 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-780: ------------------------------------------------- any action item here? > engine upgrade job is disabling puppet on slaves > ------------------------------------------------ > > Key: OVIRT-780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-780 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > I found a lot of out-of-sync slaves in Foreman and further investigation revealed that puppet agent is disabled on them. > The journal indicates that it's the upgrade job doing this: > Oct 19 14:24:51 vm0079.workers-phx.ovirt.org sudo[18213]: jenkins : TTY=unknown ; PWD=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-4.0_el7_created ; USER=root ; COMMAND=/bin/puppet agent --disable > Oct 19 14:24:54 vm0079.workers-phx.ovirt.org puppet-agent[18215]: Disabling Puppet. > The job seems to re-enable puppet after it runs, but once there's several consecutive jobs in the queue this causes puppet to be effectively turned off for hours. > Do we really need this? Can we run engine upgrade jobs inside mock to not affect the node itself? -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-780: -------------------------------------------- Epic Link: OVIRT-400 > engine upgrade job is disabling puppet on slaves > ------------------------------------------------ > > Key: OVIRT-780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-780 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > I found a lot of out-of-sync slaves in Foreman and further investigation revealed that puppet agent is disabled on them. > The journal indicates that it's the upgrade job doing this: > Oct 19 14:24:51 vm0079.workers-phx.ovirt.org sudo[18213]: jenkins : TTY=unknown ; PWD=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-4.0_el7_created ; USER=root ; COMMAND=/bin/puppet agent --disable > Oct 19 14:24:54 vm0079.workers-phx.ovirt.org puppet-agent[18215]: Disabling Puppet. > The job seems to re-enable puppet after it runs, but once there's several consecutive jobs in the queue this causes puppet to be effectively turned off for hours. > Do we really need this? Can we run engine upgrade jobs inside mock to not affect the node itself? -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-780: -------------------------------------------- Epic Link: OVIRT-400 > engine upgrade job is disabling puppet on slaves > ------------------------------------------------ > > Key: OVIRT-780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-780 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > I found a lot of out-of-sync slaves in Foreman and further investigation revealed that puppet agent is disabled on them. > The journal indicates that it's the upgrade job doing this: > Oct 19 14:24:51 vm0079.workers-phx.ovirt.org sudo[18213]: jenkins : TTY=unknown ; PWD=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-4.0_el7_created ; USER=root ; COMMAND=/bin/puppet agent --disable > Oct 19 14:24:54 vm0079.workers-phx.ovirt.org puppet-agent[18215]: Disabling Puppet. > The job seems to re-enable puppet after it runs, but once there's several consecutive jobs in the queue this causes puppet to be effectively turned off for hours. > Do we really need this? Can we run engine upgrade jobs inside mock to not affect the node itself? -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-774) 121206963795481 infra-support
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-774?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-774: -------------------------------------------- > 121206963795481 infra-support > ----------------------------- > > Key: OVIRT-774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-774 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: wwm.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by Barak Korren (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-763: ------------------------------------ I think this is more of am ovirt-system-tests issue then a Lago issue, so not appropriate for Github. > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-792) Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...'
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-792?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-792: -------------------------------------------- Epic Link: OVIRT-400 > Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...' > --------------------------------------------------------------------------------------- > > Key: OVIRT-792 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-792 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > Not sure if this is a regression, maybe added in [1], or a temporary glitch: > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/336/console > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/337/console > for now going to clean it manually. > [1] https://gerrit.ovirt.org/#/c/64511/ -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-792) Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...'
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-792?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-792: -------------------------------------------- Epic Link: OVIRT-400 > Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...' > --------------------------------------------------------------------------------------- > > Key: OVIRT-792 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-792 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: infra > > Not sure if this is a regression, maybe added in [1], or a temporary glitch: > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/336/console > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/337/console > for now going to clean it manually. > [1] https://gerrit.ovirt.org/#/c/64511/ -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-782) Problems with item delivery, n.0000558223
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-782?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-782: -------------------------------------------- > Problems with item delivery, n.0000558223 > ----------------------------------------- > > Key: OVIRT-782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-782 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx International Ground > Assignee: infra > > Dear Customer, > Your parcel has arrived at October 17. Courier was unable to deliver the parcel to you. > Please, open email attachment to print shipment label. > Kind regards, > Oscar Hendrix, > FedEx Operation Agent. -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-763: -------------------------------------------- Resolution: Won't Fix Status: Done (was: To Do) please open in Lago github project if still relevant. https://github.com/lago-project/lago/ > [Lago][rfe] ability to choose version to be installed > ----------------------------------------------------- > > Key: OVIRT-763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > I started to test using lago with master repos and my custom engine built. > It was built on 7.10 one test failed and I noticed that newer engine was > installed instead of my specific version. It seems that we need an ability > to define which version of the rpms should be used during the tests. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0

[JIRA] (OVIRT-783) Fwd: [ovirt-users] ovirt list's smtp on blacklist?
by eyal edri [Administrator] (oVirt JIRA) 03 Nov '16

03 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-783?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-783: ----------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Fwd: [ovirt-users] ovirt list's smtp on blacklist? > -------------------------------------------------- > > Key: OVIRT-783 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-783 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Marc Dequènes (Duck) > > ---------- Forwarded message ---------- > From: Jiří Sléžka <jiri.slezka(a)slu.cz> > Date: Mon, Oct 17, 2016 at 9:27 PM > Subject: [ovirt-users] ovirt list's smtp on blacklist? > To: "users(a)ovirt.org" <users(a)ovirt.org> > Hello, > it looks like mailserver which serving users(a)ovirt.org is on blacklist. > line from our smtp server log... > Oct 17 15:31:25 hermes postfix/smtpd[14082]: NOQUEUE: reject: RCPT from > lists.ovirt.org[2600:3c01::f03c:91ff:fe93:4b0d]: 554 5.7.1 Service > unavailable; Client host [2600:3c01::f03c:91ff:fe93:4b0d] blocked using > sbl.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS; from=< > users-bounces(a)ovirt.org> to=<jiri.slezka(a)slu.cz> proto=ESMTP helo=< > lists.ovirt.org> > Cheers, > Jiri > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.482.6#100017)

1 0