[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2017-01-20 Thread Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-780: -- Assignee: Evgheni Dereveanchin (was: infra) > engine upgrade

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-11-03 Thread eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-780: Resolution: Fixed Status: Done (was: To Do) > engine upgrade

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-11-03 Thread Evgheni Dereveanchin (oVirt JIRA)
- that should fix the issue. In general, disabling puppet during a job run is not critical and is only visible when there's a lot of builds so dozens of nodes get stale on Foreman. I think we can close this case. > engine upgrade job is disabling puppet on sla

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-11-03 Thread eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22204#comment-22204 ] eyal edri [Administrator] commented on OVIRT-780: - any action item here? > engine upgrade

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-11-03 Thread eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-780: Epic Link: OVIRT-400 > engine upgrade job is disabling puppet on sla

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-11-03 Thread eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-780: Epic Link: OVIRT-400 > engine upgrade job is disabling puppet on sla

[JIRA] (OVIRT-780) engine upgrade job is disabling puppet on slaves

2016-10-25 Thread Barak Korren (oVirt JIRA)
a ticket somewhere to migrate the upgrade jobs to Lago. > engine upgrade job is disabling puppet on slaves > > > Key: OVIRT-780 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-780 >

engine upgrade job

2013-06-04 Thread Kiril Nesenko
Hello, Finally after few real bugs in upgrade flow upgrade job is green ! [1]. Creating a new job that will perform upgrade per patch. [1] http://jenkins.ovirt.org/job/ovirt_engine_upgrade_stable_32_to_latest_32/74/console - Kiril ___ Infra mailing

Re: engine upgrade job

2013-06-04 Thread Eyal Edri
-related changes. kudos for the effort on ci engine bug fixes. Eyal. - Original Message - From: Kiril Nesenko ki...@redhat.com To: infra infra@ovirt.org Sent: Tuesday, June 4, 2013 3:21:27 PM Subject: engine upgrade job Hello, Finally after few real bugs in upgrade flow upgrade

Re: engine upgrade job

2013-06-04 Thread Kiril Nesenko
, 2013 3:28:32 PM Subject: Re: engine upgrade job +1 that's great news! this will help us keep both engine-setup and engine-upgrade stable and detect regressions in spec files or any other misc packaging issues. in the per patch job we should limit the job to run only on changed

Re: Engine Upgrade job

2013-05-16 Thread Sandro Bonazzola
Subject: Re: Engine Upgrade job go for it. I changed the hostname. But there is no A record for slaves ip. Alix, Sandro because we are talking about public servers, I think that there will be some issues with hostnames. Is there any workaround for this ? To pass this validation ? - Kiril

Re: Engine Upgrade job

2013-05-09 Thread Kiril Nesenko
, 2013 2:37:16 PM Subject: Re: Engine Upgrade job go for it. I changed the hostname. But there is no A record for slaves ip. Alix, Sandro because we are talking about public servers, I think that there will be some issues with hostnames. Is there any workaround for this ? To pass

Re: Engine Upgrade job

2013-05-08 Thread Kiril Nesenko
- Original Message - From: Alex Lourie alou...@redhat.com To: Ohad Basan oba...@redhat.com Cc: Sandro Bonazzola sbona...@redhat.com, Kiril Nesenko ki...@redhat.com, infra infra@ovirt.org Sent: Wednesday, May 8, 2013 12:37:06 AM Subject: Re: Engine Upgrade job On Tue, May 7

Re: Engine Upgrade job

2013-05-08 Thread Eyal Edri
: Engine Upgrade job - Original Message - From: Alex Lourie alou...@redhat.com To: Ohad Basan oba...@redhat.com Cc: Sandro Bonazzola sbona...@redhat.com, Kiril Nesenko ki...@redhat.com, infra infra@ovirt.org Sent: Wednesday, May 8, 2013 12:37:06 AM Subject: Re: Engine Upgrade

Re: Engine Upgrade job

2013-05-07 Thread Ohad Basan
- Original Message - From: Kiril Nesenko ki...@redhat.com To: Alex Lourie alou...@redhat.com, Sandro Bonazzola sbona...@redhat.com Cc: infra infra@ovirt.org Sent: Tuesday, May 7, 2013 10:33:33 PM Subject: Engine Upgrade job Hello, I am working on engine upgrade job. I have

Re: Engine Upgrade job

2013-05-07 Thread Alex Lourie
: Engine Upgrade job Hello, I am working on engine upgrade job. I have a slave with 'ip-10-82-253-208' hostname. This job fails on engine-setup [1] because of this hostname. Sandro, Alex can you take a look please ? this is due to the following code: if not validateDomain(param,options