- Infra - oVirt List Archives

[JIRA] (OVIRT-1487) ML listing broken
by Marc Dequènes (Duck) (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1487?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-1487: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) So, my bad, I looked at https://lists.phx.ovirt.org/ and not https://lists.ovirt.org/, and as it is not the same domain MM displays differently. Was tired, sorry for the noise :-/ > ML listing broken > ----------------- > > Key: OVIRT-1487 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1487 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Mailing lists (Mailman) > Reporter: Marc Dequènes (Duck) > Assignee: infra > > Quack, > After I rebooted for OVIRT-1473 I checked the services and noticed the list of Mls is empty. The server works well, and even the MLs archives and admin panel are all there, only the listing seem affected. > So there was an upgrade of the package, see changelog: > https://centos.pkgs.org/6/centos-x86_64/mailman-2.1.12-26.el6.x86_64.rpm.ht… > here is the issue solved: > https://bugzilla.redhat.com/show_bug.cgi?id=1363835 > It does not seem to be related, as the rest works. > So it seems this upgrade is unrelated. Maybe the bug was there since a while, or maybe the reboot uncovered it. I did not find anything obvious. Anyway we need to investigate more. > \_o< -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1492) Status.ovirt.org doesn't report real status
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1492?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1492: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Status.ovirt.org doesn't report real status > ------------------------------------------- > > Key: OVIRT-1492 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1492 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Some services are not reachable but it is not shown on status page. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1491) Change oVirt DC production storage
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1491?page=com.atlassian.jira.… ] eedri updated OVIRT-1491: ------------------------- Resolution: Duplicate Status: Done (was: To Do) https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Change oVirt DC production storage > ----------------------------------- > > Key: OVIRT-1491 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > Priority: Highest > > It seems that during the history of the DC, there wasn't one time we really used the DRDB features and it makes our storage configuration more complex and hard to maintain/debug than it brings value. > Lets think on a new SIMPLE storage setup that will increase the availability of oVirt services and will prevent incidents like before where we have a single point of failure if the storage is down. without multiple services that adds more failure points and complexity to the setup. > One suggestion was to install 2 new storage servers running ISCSI and connect them independently to oVirt and spread the load over both of them, so if one is down the other will keep running. > We can consider having a few redundant VMs on both servers if possible like the resources server and maybe others as well. > Please add more suggestions on this ticket, it should be our number one priority right now. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1492) Status.ovirt.org doesn't report real status
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

eedri created OVIRT-1492: ---------------------------- Summary: Status.ovirt.org doesn't report real status Key: OVIRT-1492 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1492 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eedri Assignee: infra Some services are not reachable but it is not shown on status page. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el6-x86_64 #495
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el6-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el6-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-updates-el6-x86_64] $ /bin/bash -xe /tmp/hudson6228168351360021776.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1470, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1248, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1020, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 699, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 694, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 631, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 876, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 873, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 819, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[Lago][HC] tuned service fails to start on one of HC hosts
by Sahina Bose 29 Jun '17

29 Jun '17

One of the host fails to install with Failed to install Host lago-hc-basic-suite-master-host2. Failed to execute stage 'Misc configuration': Failed to start service 'tuned' The installation on other 2 hosts have been successful - all hosts are created from same template/repo. So this is strange. On Wed, Jun 28, 2017 at 8:58 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ > Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/154/ > Build Number: 154 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #154 > [Daniel Belenky] Exclude packages from ovirt-master.repo > > [Barak Korren] Filter builds sent to change queues by version > > [Barak Korren] Make change queue invoke OST basic suit > > [Barak Korren] Various UX improvements in change-queue jobs > > [Barak Korren] Add a job for direct deployments to 'tested' > > [Barak Korren] Use new job to update 'tested' from experimental > > [Barak Korren] Use new tested deploy job in timed builders > > [Eyal Edri] update build retention policy for big artifacts > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: 002_bootstrap.add_hosts > > Error Message: > Host lago-hc-basic-suite-master-host2 failed to install > -------------------- >> begin captured logging << -------------------- > ovirtlago.testlib: ERROR: * Unhandled exception in <function > _host_is_up at 0x3f11cf8> > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, > in assert_equals_within > res = func() > File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ > ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", > line 151, in _host_is_up > raise RuntimeError('Host %s failed to install' % host.name()) > RuntimeError: Host lago-hc-basic-suite-master-host2 failed to install > --------------------- >> end captured logging << --------------------- > > Stack Trace: > File "/usr/lib64/python2.7/unittest/case.py", line 369, in run > testMethod() > File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in > runTest > self.test(*self.arg) > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, > in wrapped_test > test() > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, > in wrapper > return func(get_test_prefix(), *args, **kwargs) > File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ > ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", > line 164, in add_hosts > testlib.assert_true_within(_host_is_up, timeout=15 * 60) > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 256, > in assert_true_within > assert_equals_within(func, True, timeout, allowed_exceptions) > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, > in assert_equals_within > res = func() > File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ > ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", > line 151, in _host_is_up > raise RuntimeError('Host %s failed to install' % host.name()) > Host lago-hc-basic-suite-master-host2 failed to install > -------------------- >> begin captured logging << -------------------- > ovirtlago.testlib: ERROR: * Unhandled exception in <function > _host_is_up at 0x3f11cf8> > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, > in assert_equals_within > res = func() > File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ > ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", > line 151, in _host_is_up > raise RuntimeError('Host %s failed to install' % host.name()) > RuntimeError: Host lago-hc-basic-suite-master-host2 failed to install > --------------------- >> end captured logging << ---------------------

2 3

[JIRA] (OVIRT-1491) Change oVirt DC production storage
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

eedri created OVIRT-1491: ---------------------------- Summary: Change oVirt DC production storage Key: OVIRT-1491 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eedri Assignee: infra Priority: Highest It seems that during the history of the DC, there wasn't one time we really used the DRDB features and it makes our storage configuration more complex and hard to maintain/debug than it brings value. Lets think on a new SIMPLE storage setup that will increase the availability of oVirt services and will prevent incidents like before where we have a single point of failure if the storage is down. without multiple services that adds more failure points and complexity to the setup. One suggestion was to install 2 new storage servers running ISCSI and connect them independently to oVirt and spread the load over both of them, so if one is down the other will keep running. We can consider having a few redundant VMs on both servers if possible like the resources server and maybe others as well. Please add more suggestions on this ticket, it should be our number one priority right now. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1491) Change oVirt DC production storage
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1491?page=com.atlassian.jira.… ] eedri updated OVIRT-1491: ------------------------- Epic Link: OVIRT-403 > Change oVirt DC production storage > ----------------------------------- > > Key: OVIRT-1491 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > Priority: Highest > > It seems that during the history of the DC, there wasn't one time we really used the DRDB features and it makes our storage configuration more complex and hard to maintain/debug than it brings value. > Lets think on a new SIMPLE storage setup that will increase the availability of oVirt services and will prevent incidents like before where we have a single point of failure if the storage is down. without multiple services that adds more failure points and complexity to the setup. > One suggestion was to install 2 new storage servers running ISCSI and connect them independently to oVirt and spread the load over both of them, so if one is down the other will keep running. > We can consider having a few redundant VMs on both servers if possible like the resources server and maybe others as well. > Please add more suggestions on this ticket, it should be our number one priority right now. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1490) Simplify oVirt sotrage configuration
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1490: ------------------------------------- [~eedri] [~ederevea] lets start discussion here. > Simplify oVirt sotrage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1490) Simplify oVirt sotrage configuration
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

Barak Korren created OVIRT-1490: ----------------------------------- Summary: Simplify oVirt sotrage configuration Key: OVIRT-1490 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 Project: oVirt - virtualization made easy Issue Type: Improvement Components: storage Reporter: Barak Korren Assignee: infra Priority: Highest Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. I suggest we implement a new storage layout that meets the following criteria: # Ultimate simplicity at the lower level of the stack. More specifically: ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. ## Only simple storage will be presented to oVirt for use as storage domains # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1490) Simplify oVirt sotrage configuration
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1490: -------------------------------- Epic Link: OVIRT-403 > Simplify oVirt sotrage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1489) refactor git push map file to be regex instead of url
by Gil Shinar (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1489?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1489: --------------------------------- Assignee: Gil Shinar (was: infra) > refactor git push map file to be regex instead of url > ----------------------------------------------------- > > Key: OVIRT-1489 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1489 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > > changing the way the poll script reads stuff from the git push map file. > Instead of using implicit URL, use regex to be able to support in whatever comes in the future -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1489) refactor git push map file to be regex instead of url
by Gil Shinar (oVirt JIRA) 29 Jun '17

29 Jun '17

Gil Shinar created OVIRT-1489: --------------------------------- Summary: refactor git push map file to be regex instead of url Key: OVIRT-1489 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1489 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra changing the way the poll script reads stuff from the git push map file. Instead of using implicit URL, use regex to be able to support in whatever comes in the future -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?
by Marc Dequènes (Duck) (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.… ] Marc Dequènes (Duck) commented on OVIRT-1231: --------------------------------------------- So, the only place using it is the new ML3 server, which is on production only for redirects. We're currently using the 'httpd' Ansible role to deploy the configuration, which activates it. The role also activates 'includeSubDomains'; this is a desired setting but only when all the vhosts on the domain are able to do HTTPS. This is not the case on all oVirt infra yet so it was deactivated manually at some point IIRC. So, this solution is not perfect but avoiding protocol downgrade is already a very important protection and we should use it. We should also use 'includeSubDomains' too when all our vhosts are ready. And we must not create new vhosts without HTTPS support even for testing. Here are my recommendations. > Security: do we need HSTS for oVirt services? > --------------------------------------------- > > Key: OVIRT-1231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > > https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security > Most of the browsers already supports it and some websites started to enforce it. > cc [~dfediuck] -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

Outage in network affecting oVirt services
by Eyal Edri 29 Jun '17

29 Jun '17

FYI, It looks like we have an outage in the DC we're running our oVirt services, it is currently affecting multiple services like Jenkins and Resources but not Gerrit. We are escalating it to the relevant teams to check what is causing it and will report once we have an update. -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 457 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_125_2130288522.1498681300825 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 457 Build Status: Failure Triggered By: Started by user Yuval Turgeman ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #457 [Yuval Turgeman] automation: adding timestamp to squashfs ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_125_2130288522.1498681300825--

1 1

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 154 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_84_325694316.1498620535803 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/154/ Build Number: 154 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #154 [Daniel Belenky] Exclude packages from ovirt-master.repo [Barak Korren] Filter builds sent to change queues by version [Barak Korren] Make change queue invoke OST basic suit [Barak Korren] Various UX improvements in change-queue jobs [Barak Korren] Add a job for direct deployments to 'tested' [Barak Korren] Use new job to update 'tested' from experimental [Barak Korren] Use new tested deploy job in timed builders [Eyal Edri] update build retention policy for big artifacts ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-master-host2 failed to install -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3f11cf8> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) RuntimeError: Host lago-hc-basic-suite-master-host2 failed to install --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 164, in add_hosts testlib.assert_true_within(_host_is_up, timeout=15 * 60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 256, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) Host lago-hc-basic-suite-master-host2 failed to install -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up at 0x3f11cf8> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 217, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt_master_hc-system-tests/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 151, in _host_is_up raise RuntimeError('Host %s failed to install' % host.name()) RuntimeError: Host lago-hc-basic-suite-master-host2 failed to install --------------------- >> end captured logging << --------------------- ------=_Part_84_325694316.1498620535803--

1 1

planned Gerrit maintenance
by Evgheni Dereveanchin 28 Jun '17

28 Jun '17

Hi everyone, I will be performing updates on gerrit.ovirt.org during the next two hours. Within this period the Gerrit UI and Git repositories may be unavailable. I will follow up as soon as maintenance activities are over. -- Regards, Evgheni Dereveanchin

2 3

[JIRA] (OVIRT-1488) gerrit is down
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1488?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1488: --------------------------------------------- This was a planned maintenance window and alerts have been sent to devel and infra lists. Gerrit should be back up and running now, sorry for the inconvenience. > gerrit is down > -------------- > > Key: OVIRT-1488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1488 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: gshereme(a)redhat.com > Assignee: Evgheni Dereveanchin > Priority: Highest > > Hi, > https://gerrit.ovirt.org/ > Service Temporarily Unavailable > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 > -- > Greg Sheremeta, MBA > Sr. Software Engineer > Red Hat, Inc. > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1488) gerrit is down
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1488?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1488: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > gerrit is down > -------------- > > Key: OVIRT-1488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1488 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: gshereme(a)redhat.com > Assignee: Evgheni Dereveanchin > Priority: Highest > > Hi, > https://gerrit.ovirt.org/ > Service Temporarily Unavailable > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 > -- > Greg Sheremeta, MBA > Sr. Software Engineer > Red Hat, Inc. > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

oVirt infra daily report - unstable production jobs - 367
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_129_1942579765.1498699004655 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/367//artifact/exported-a… Cheers, Jenkins ------=_Part_129_1942579765.1498699004655 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 29/06/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/">ovirt_4.1_system-tests_pre</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/">ovirt_master_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_129_1942579765.1498699004655--

1 0

[JIRA] (OVIRT-1488) gerrit is down
by gshereme＠redhat.com (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1488?page=com.atlassian.jira.… ] gshereme(a)redhat.com updated OVIRT-1488: --------------------------------------- Resolution: Fixed Status: Done (was: To Do) > gerrit is down > -------------- > > Key: OVIRT-1488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1488 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: gshereme(a)redhat.com > Assignee: infra > Priority: Highest > > Hi, > https://gerrit.ovirt.org/ > Service Temporarily Unavailable > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 > -- > Greg Sheremeta, MBA > Sr. Software Engineer > Red Hat, Inc. > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1488) gerrit is down
by gshereme＠redhat.com (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1488?page=com.atlassian.jira.… ] gshereme(a)redhat.com updated OVIRT-1488: --------------------------------------- Priority: Highest (was: Medium) > gerrit is down > -------------- > > Key: OVIRT-1488 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1488 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: gshereme(a)redhat.com > Assignee: infra > Priority: Highest > > Hi, > https://gerrit.ovirt.org/ > Service Temporarily Unavailable > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 > -- > Greg Sheremeta, MBA > Sr. Software Engineer > Red Hat, Inc. > gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1488) gerrit is down
by gshereme＠redhat.com (oVirt JIRA) 28 Jun '17

28 Jun '17

gshereme(a)redhat.com created OVIRT-1488: ------------------------------------------ Summary: gerrit is down Key: OVIRT-1488 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1488 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: gshereme(a)redhat.com Assignee: infra Hi, https://gerrit.ovirt.org/ Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 -- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

gerrit is down
by Greg Sheremeta 28 Jun '17

28 Jun '17

Hi, https://gerrit.ovirt.org/ Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.15 (Red Hat) Server at gerrit.ovirt.org Port 443 -- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme(a)redhat.com

1 0

[JIRA] (OVIRT-1487) ML listing broken
by Marc Dequènes (Duck) (oVirt JIRA) 28 Jun '17

28 Jun '17

Marc Dequènes (Duck) created OVIRT-1487: ------------------------------------------- Summary: ML listing broken Key: OVIRT-1487 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1487 Project: oVirt - virtualization made easy Issue Type: Bug Components: Mailing lists (Mailman) Reporter: Marc Dequènes (Duck) Assignee: infra Quack, After I rebooted for OVIRT-1473 I checked the services and noticed the list of Mls is empty. The server works well, and even the MLs archives and admin panel are all there, only the listing seem affected. So there was an upgrade of the package, see changelog: https://centos.pkgs.org/6/centos-x86_64/mailman-2.1.12-26.el6.x86_64.rpm.ht… here is the issue solved: https://bugzilla.redhat.com/show_bug.cgi?id=1363835 It does not seem to be related, as the rest works. So it seems this upgrade is unrelated. Maybe the bug was there since a while, or maybe the reboot uncovered it. I did not find anything obvious. Anyway we need to investigate more. \_o< -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1487) ML listing broken
by Marc Dequènes (Duck) (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1487?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-1487: ---------------------------------------- Epic Link: OVIRT-403 > ML listing broken > ----------------- > > Key: OVIRT-1487 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1487 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Mailing lists (Mailman) > Reporter: Marc Dequènes (Duck) > Assignee: infra > > Quack, > After I rebooted for OVIRT-1473 I checked the services and noticed the list of Mls is empty. The server works well, and even the MLs archives and admin panel are all there, only the listing seem affected. > So there was an upgrade of the package, see changelog: > https://centos.pkgs.org/6/centos-x86_64/mailman-2.1.12-26.el6.x86_64.rpm.ht… > here is the issue solved: > https://bugzilla.redhat.com/show_bug.cgi?id=1363835 > It does not seem to be related, as the rest works. > So it seems this upgrade is unrelated. Maybe the bug was there since a while, or maybe the reboot uncovered it. I did not find anything obvious. Anyway we need to investigate more. > \_o< -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7393 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_111_78032725.1498665585609 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7393/, Build Number: 7393, Build Status: FAILURE ------=_Part_111_78032725.1498665585609--

1 1

[oVirt Jenkins] standard-enqueue - Build #2118 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '17

28 Jun '17

------=_Part_113_596784380.1498666404045 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/2118/ Build Name: 2118 ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78758 - title: webadmin: TemplateBackupModel streams - project: ovirt-engine - branch: master - author: Allon Mureinik <amureini(a)redhat.com> ------=_Part_113_596784380.1498666404045--

1 0

[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1164?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1164: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Remove most of the images from glance.ovirt.org > ----------------------------------------------- > > Key: OVIRT-1164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1164 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Yaniv Kaul > Assignee: Evgheni Dereveanchin > > I'd like to make sure people are not abusing and downloading images from Glance that are not directly related to oVirt. Providing it as a service for download is not our aim. > Currently, it has a lot of different images, multiple versions of them, etc. > Specifically, multiple versions of Ubuntu, and older versions of Atomic, CentOS, Fedora should be removed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1231: --------------------------------------------- [~duck] are we already using this? > Security: do we need HSTS for oVirt services? > --------------------------------------------- > > Key: OVIRT-1231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > > https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security > Most of the browsers already supports it and some websites started to enforce it. > cc [~dfediuck] -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1245) Consider way for organize disaster recovery solution for lists
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1245?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1245: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Consider way for organize disaster recovery solution for lists > -------------------------------------------------------------- > > Key: OVIRT-1245 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1245 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: Marc Dequènes (Duck) > > │08:50:51 sbonazzo1 | landgraf: we're lucky enough we have mirrors for users │ > │08:51:05 sbonazzo1 | landgraf: too bad we don't have redundant CI infra :-) │ > │08:51:27 landgraf | sbonazzo1: and lists.. │ > │08:51:40 landgraf | sbonazzo1: so we cannot send outage ntifications there :) │ > │08:51:51 sbonazzo1 | landgraf: yep │ > │08:52:03 sbonazzo1 | landgraf: maybe worth to open a jira ticket for it │ > │08:52:10 sbonazzo1 | landgraf: it will be a huge improvement │ > │08:53:30 sbonazzo1 | landgraf: do we have a disaster recovery plan? -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1281: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1288) Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1288?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1288: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Find out why Gerrit always fails re-basing when trying to submit more then 3 changes at once > -------------------------------------------------------------------------------------------- > > Key: OVIRT-1288 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1288 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Gerrit has a feature where if you have multiple dependant patches, and they all have all the flags properly set, the submit button for changes with unmerged dependencies becomes 'Submit including parents' and lets you submit a whole set of changes at once. > I've found out that of you have more then 3 dependent changes in a chain, Gerrit will always fail submitting the 4th change and claim there is a rebase conflict, even when there is none. > This sounds like an artificial limitation, and we need to at least know where it comes from. And consider removing it. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1295: ---------------------------------------- Priority: Low (was: Medium) > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1311: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1311) Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1311?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1311: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Nightliy publisher 'move_jenkins_nightly' cron job failes when the *.ready dir is empty > --------------------------------------------------------------------------------------- > > Key: OVIRT-1311 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1311 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > If The '{{*.ready}}' directory does not contain any RPMs, the cron job fails. This failure causes all repos not to get published until the failure is fixed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1312: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1312: ---------------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Make 'scan_for_artifacts.sh' publish repos separately > ----------------------------------------------------- > > Key: OVIRT-1312 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions. > The issue is that if one of the repos fails to sync, the rest do not get synced either. > We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1331) Enable fc26 updates mirror
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1331?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1331: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Enable fc26 updates mirror > -------------------------- > > Key: OVIRT-1331 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1331 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Since fc26 is not releases yet, there is no 'updates' repo. > Once fc26 is releases we will need to create the 'updates' mirror. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1334) Setup a cleanup job for the mirrors
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1334?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1334: ------------------------------------------- Assignee: Barak Korren (was: infra) > Setup a cleanup job for the mirrors > ----------------------------------- > > Key: OVIRT-1334 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1334 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > > Out transactional mirrors do not currently have a cleanup job. This means packages are kept forever, or at least until specific mirrors are removed. > This means we may run out of space. > Need to first verify this is actually needed in practice once OVIRT-1332 and OVIRT-1333 are implemented. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1387) change gateway IP on PHX HE hypervisors
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1387?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1387: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > change gateway IP on PHX HE hypervisors > --------------------------------------- > > Key: OVIRT-1387 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1387 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > We have an incorrect gateway set in HA configs of ovirt-srv01, ovirt-srv02 and ovirt-srv03v which can cause issues like the ones described in OVIRT-1369 > During the next host update window we need to edit /etc/ovirt-hosted-engine/hosted-engine.conf and change the gateway before rebooting. This has to be done in global maintenance to avoid unnecessary Engine restarts. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1415) Add more FC26 slaves
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1415?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1415: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add more FC26 slaves > -------------------- > > Key: OVIRT-1415 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1415 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > We only have one ATM, this means that many jobs need to wait in queue for it. > Please add more. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1416) Preserve Gerrit CR flags on rebase.
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1416?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1416: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Preserve Gerrit CR flags on rebase. > ------------------------------------ > > Key: OVIRT-1416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Sometimes a patch finishes review and then needs to be rebased for some reason. This causes all flags to be lost. > We currently have settings to keep the +v flag on trivial rebase, we need the same for at least the CR flag. > Doing this for the WF flag might not be necessary though, b/c it is controlled by the patch author. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1418) Lets remove the 'workflow' flag
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1418?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1418: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Lets remove the 'workflow' flag > ------------------------------- > > Key: OVIRT-1418 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1418 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > I don't remember what was David's idea behind adding it, I'm pretty sure nobody else does, and for now its just annoying. People just forget to set it, and you need to have it set to +2 to merge. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1468: --------------------------------------------- as proposed by [~bkorren(a)redhat.com] we can actually inject repo information using Jenkins and not puppet, then we can have more control over which snapshot is in use. > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1486) Add GitHub support for standard-enqueue (change-queue)
by Barak Korren (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1486?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1486: ----------------------------------- Assignee: Barak Korren (was: infra) > Add GitHub support for standard-enqueue (change-queue) > ------------------------------------------------------ > > Key: OVIRT-1486 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1486 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > Labels: change-queue, github, standard-ci, vdsm-fake > > The standard-enqueue job that currently sends changes to the change queue, does not support events from GitHub. > The only project in GitHub we have currently, that works with STD-CI is 'vdsm-fake'. > 'vdsm-fake' is currently releasing packages to the oVirt repos via the 'expermental' flow. In order to allow it to keep releasing packages, we need to make the change-queue support merge events in GitHub. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1486) Add GitHub support for standard-enqueue (change-queue)
by Barak Korren (oVirt JIRA) 28 Jun '17

28 Jun '17

Barak Korren created OVIRT-1486: ----------------------------------- Summary: Add GitHub support for standard-enqueue (change-queue) Key: OVIRT-1486 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1486 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High The standard-enqueue job that currently sends changes to the change queue, does not support events from GitHub. The only project in GitHub we have currently, that works with STD-CI is 'vdsm-fake'. 'vdsm-fake' is currently releasing packages to the oVirt repos via the 'expermental' flow. In order to allow it to keep releasing packages, we need to make the change-queue support merge events in GitHub. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1486) Add GitHub support for standard-enqueue (change-queue)
by Barak Korren (oVirt JIRA) 28 Jun '17

28 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1486?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1486: -------------------------------- Epic Link: OVIRT-400 > Add GitHub support for standard-enqueue (change-queue) > ------------------------------------------------------ > > Key: OVIRT-1486 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1486 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, github, standard-ci, vdsm-fake > > The standard-enqueue job that currently sends changes to the change queue, does not support events from GitHub. > The only project in GitHub we have currently, that works with STD-CI is 'vdsm-fake'. > 'vdsm-fake' is currently releasing packages to the oVirt repos via the 'expermental' flow. In order to allow it to keep releasing packages, we need to make the change-queue support merge events in GitHub. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

Change 78770,1 (ovirt-engine-api-model) failed system tests
by oVirt Jenkins 28 Jun '17

28 Jun '17

Change 78770,1 (ovirt-engine-api-model) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78770/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/961/

1 0