June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2223: ---------------------------------------- Issue Type: Sub-task (was: Task) Parent: OVIRT-2045 > upgrade CentOS CI slaves > ------------------------ > > Key: OVIRT-2223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2223 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Evgheni Dereveanchin > Assignee: infra > > We do update most of the important software on slaves via global_setup yet packages like the kernel and libraries are left behind. With Fedora this is not a big deal since we rebuild those every year yet there's still a bunch of CentOS systems which may need updating. Opening ticket to track the upgrade footprint and test updates if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2223: --------------------------------------------- As most of our slaves are VMs it's probably easiest to rebuild them instead of upgrading as that will conserve disk space thanks to thin template images. This is in place for Fedora 28 but not yet tested on CentOS 7. I can spawn a separate ticket from OVIRT-280 to implement this. For now I've upgraded vm0002 on Staging and ~170 packages got updated including java and python libraries as well as other stuff. Put it online so that we can see if any incompatibilities are detected before upgrading the rest to move OVIRT-2045 forward > upgrade CentOS CI slaves > ------------------------ > > Key: OVIRT-2223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2223 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > We do update most of the important software on slaves via global_setup yet packages like the kernel and libraries are left behind. With Fedora this is not a big deal since we rebuild those every year yet there's still a bunch of CentOS systems which may need updating. Opening ticket to track the upgrade footprint and test updates if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

20 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Daniel Belenky] Install python-six during global-setup [Barak Korren] Make mock_runner use curl instead of wget [Barak Korren] Fix proxied configuration for FC27 and FC28 [Daniel Belenky] Move project functions to a shared lib [Daniel Belenky] Utilize stdci_project groovy lib in CQ ------------------------------------------ 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 a7893b590e5e42588471579d90d6a0c69f5b04b2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a7893b590e5e42588471579d90d6a0c69f5b04b2 Commit message: "Utilize stdci_project groovy lib in CQ" > git rev-list --no-walk 16730ba6637684961f7acf86a07cce81c0dd19f8 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3477170584904239158.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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 906, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2224) standard-enqueue issues warning about projects with V2 jobs
by Barak Korren (oVirt JIRA) 20 Jun '18

20 Jun '18

Barak Korren created OVIRT-2224: ----------------------------------- Summary: standard-enqueue issues warning about projects with V2 jobs Key: OVIRT-2224 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2224 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra The standard-enqueue job looks at merged patches, and issues a warning to Gerrit if the project the patch was merged into does not have an STDCI V1 build-artifacts job and therefore the patch cannot be submitted to any change queues by it. The warning is misleading if the project has a V2 job because then the change can be submitted to the queues by the V2 job despite the lack of a V1 build job. We should make standard-enqueue STDCI V2 aware and not issue warnings to projects with STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

20 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: 260 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #260 [Gal Ben Haim] upgrade_from_release_suite_master Update pre-reposync ----------------- Failed Tests: ----------------- All tests passed

1 1

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

20 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/277/ Build Number: 277 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #277 [Gal Ben Haim] upgrade_from_release_suite_master Update pre-reposync ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves
by eyal edri (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2223?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2223: ---------------------------------- Any way we can automate this upgrade? are we using an Ansible playbook for it? On Wed, Jun 20, 2018 at 1:02 PM Evgheni Dereveanchin (oVirt JIRA) < -- Eyal edri 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) > upgrade CentOS CI slaves > ------------------------ > > Key: OVIRT-2223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2223 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > We do update most of the important software on slaves via global_setup yet packages like the kernel and libraries are left behind. With Fedora this is not a big deal since we rebuild those every year yet there's still a bunch of CentOS systems which may need updating. Opening ticket to track the upgrade footprint and test updates if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2223) upgrade CentOS CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 20 Jun '18

20 Jun '18

Evgheni Dereveanchin created OVIRT-2223: ------------------------------------------- Summary: upgrade CentOS CI slaves Key: OVIRT-2223 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2223 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra We do update most of the important software on slaves via global_setup yet packages like the kernel and libraries are left behind. With Fedora this is not a big deal since we rebuild those every year yet there's still a bunch of CentOS systems which may need updating. Opening ticket to track the upgrade footprint and test updates if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

2 1

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2216: -------------------------------- Assignee: Dafna Ron (was: infra) > Cannot find a valid baseurl for repo: base/7/x86_64 > --------------------------------------------------- > > Key: OVIRT-2216 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2216 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: ost_failures, ost_infra, ost_race > > vm deployment in lago fails with: > Cannot find a valid baseurl for repo: base/7/x86_64 > This is the 3ed time I have seen this and I think we may have network lag that is causing a time out. > [~ederevea] can you please take a look? > https://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-4.2_change-queue-tester/2431 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2222) Package retention policy for tested repo
by Ehud Yonasi (oVirt JIRA) 20 Jun '18

20 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2222?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2222: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Package retention policy for tested repo > ---------------------------------------- > > Key: OVIRT-2222 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2222 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > > There is a know issue with the space left under /src/resources > in order to help save space, i am going to add a retention policy for repo packages. > the retention rules are to keep only latest version of that package and packages under 14 days old. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0