- Infra - oVirt List Archives

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by sbonazzo (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2201: --------------------------------- {quote}"As an oVirt developer, I want to see the build status for the HEAD commit of a particular branch of my project so that I can <need to fill in reason here>"{quote} - get the general CI health of a release (master vs 4.2) - take immediate action on the specific branch of a project {quote}"As an oVirt developer I want to have a way to acquire the lasted CI build on a particular branch on a particular project so that I can use it as a dependency for other jobs". About this last one - I guess we can ask people in devel if "tested" would be a good enough compromise? {quote} Issue with this is that you may have a change which depends on a change in another package (example: ovirt-host-deploy with otopi) and having to rely on tested instead of lastSuccessfullBuild means you need to wait for change queue to succeed and publish to tested before being able to run check-patch. This means a delay on the handling of the patch of ~1 hour which is suboptimal. > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 116 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '18

20 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/116/ Build Number: 116 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #116 [Gal Ben Haim] upgrade_from_release_suite_master Update pre-reposync ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 258 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 258 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #258 [Gal Ben Haim] upgrade_from_release_suite_master Update pre-reposync [Sandro Bonazzola] automation: add missing python-six package ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 275 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/275/ Build Number: 275 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #275 [Milan Zamazal] Make a separate screenshot directory for each DC version [Sandro Bonazzola] automation: add missing python-six package ----------------- Failed Tests: ----------------- No tests ran.

1 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1673
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Sandro Bonazzola] automation: add missing python-six package ------------------------------------------ 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-el7-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/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 16730ba6637684961f7acf86a07cce81c0dd19f8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 16730ba6637684961f7acf86a07cce81c0dd19f8 Commit message: "automation: add missing python-six package" > git rev-list --no-walk f68ee1c69229c9244eba01bcac4c409b9049e49f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1639502393174931532.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2221) Reposync builder will no work with DNF
by Gal Ben Haim (oVirt JIRA) 19 Jun '18

19 Jun '18

Gal Ben Haim created OVIRT-2221: ----------------------------------- Summary: Reposync builder will no work with DNF Key: OVIRT-2221 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2221 Project: oVirt - virtualization made easy Issue Type: Task Components: OST Reporter: Gal Ben Haim Assignee: infra Part of the reposync builder tool is a Yum plugin which auto-generates the reposync-config with "includepkgs" field. DNF doesn't support Yum plugins, so we will have to rewrite the plugin for DNF, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1932) proxy server not working for jenkins jobs
by Evgheni Dereveanchin (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1932?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1932: ---------------------------------------- Resolution: Duplicate Status: Done (was: To Do) This is being worked on in OVIRT-2214 > proxy server not working for jenkins jobs > ----------------------------------------- > > Key: OVIRT-1932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > > I've seen: > *13:42:06* Failed to contact proxy http://proxy01.phx.ovirt.org:3128, > falling back to non-proxied config > right now on > http://jenkins.ovirt.org/job/cockpit-ovirt_4.2_check-patch-fc27-x86_64/117/… > Please have a look > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 493 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/493/ Build Number: 493 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #493 [Yedidyah Bar David] UI sanity: Increase timeout [Sandro Bonazzola] ovirt-jboss-modules-maven-plugin: move to v2 ----------------- Failed Tests: ----------------- No tests ran.

1 2

[JIRA] (OVIRT-1932) proxy server not working for jenkins jobs
by Evgheni Dereveanchin (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1932?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1932: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > proxy server not working for jenkins jobs > ----------------------------------------- > > Key: OVIRT-1932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > > I've seen: > *13:42:06* Failed to contact proxy http://proxy01.phx.ovirt.org:3128, > falling back to non-proxied config > right now on > http://jenkins.ovirt.org/job/cockpit-ovirt_4.2_check-patch-fc27-x86_64/117/… > Please have a look > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1658) Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale)
by Evgheni Dereveanchin (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1658?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1658: ---------------------------------------- Resolution: Won't Do Status: Done (was: To Do) This issue is still present on slaves upgraded from 7.3 to 7.4 yet after all this time it hasn't caused any visible issues. We will eventually rebuild all CentOS systems from a clean 7.5 issue where this warning should no longer appear. I think we can close this ticket. > Potential issue coming to CentOS7 slaves (glibc, missing UTF-8 locale) > ---------------------------------------------------------------------- > > Key: OVIRT-1658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1658 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Seems there is an issue with locale files in recent CentOS versions, > and we're hitting it in slaves that have been updated recently. > The symptoms are that Jenkins disconnects from the slave and then > refuses to reconnect to it. The agent log in Jenkins shows: > [09/19/17 15:42:56] [SSH] Connection closed. > [09/19/17 15:58:48] [SSH] Opening SSH connection to > vm0002.workers-phx.ovirt.org:22. > [09/19/17 15:58:48] [SSH] WARNING: SSH Host Keys are not being > verified. Man-in-the-middle attacks may be possible against this > connection. > [09/19/17 15:58:48] [SSH] Authentication successful. > SSH connection reports a garbage before a command execution. > Check your .bashrc, .profile, and so on to make sure it is quiet. > The received junk text is as follows: > /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot > change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 20: warning: setlocale: LC_COLLATE: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 23: warning: setlocale: LC_MESSAGES: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 26: warning: setlocale: LC_NUMERIC: > cannot change locale (en_US.utf8): No such file or directory > /etc/profile.d/lang.sh: line 29: warning: setlocale: LC_TIME: cannot > change locale (en_US.utf8): No such file or directory > null > [09/19/17 15:58:48] Launch failed - cleaning up connection > [09/19/17 15:58:48] [SSH] Connection closed. > The same locale error messages can also be reproduced on the slave by > running an interactive login from the console or 'su -'. When running > 'locale -a' you can also see the en_US.UTF-8 locale is somehow > missing. > Looking around for this I found the following: > https://github.com/CentOS/sig-cloud-instance-images/issues/71 > I tried downgrading glibc back to the version we had before, but that > did not seem to resolve the issue. Eventually I managed to resolve it > by running 'localedef -i en_US -f UTF-8 en_US.UTF-8' on the slave. > I've seen this happen on 'vm0002.workers-phx.ovirt.org' which is > attached to the staging Jenkins, but I've no reason to believe this > won't start impacting production slaves. > We need to research this further and find out if we need to do > something to prevent this issue from surfacing on production slaves. > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0