June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2200: ------------------------------------- Just some more thoughts about this - we could maybe solve this by "exploading" directory symlinks in our code as if they were symlinks to each and every file in the directory. That way all the other symlink handling code will just work. But we need to be careful about this, as we can have directory symlinks to directories with directory symlinks in them... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2200: ------------------------------------- [~dbelenky(a)redhat.com] not sure about the priority for this, we've seen that links to directories have a tendency to become directories with links sooner or later anyway... As you say its not a very easy fix, we need to go into the symlink resolution algorithms in usrc.py and add directory support. We have other things we want to do and other bugs we're not solving so well need to consider carefully if and when we're going to solve this. In the meantime there are various workarounds that could be used... > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2200: -------------------------------- Component/s: STDCI DSL > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: STDCI DSL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2200: -------------------------------- Issue Type: Bug (was: By-EMAIL) > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2200?page=com.atlassian.jir... ] Daniel Belenky commented on OVIRT-2200: --------------------------------------- [~bkorren(a)redhat.com] seems like something we've saw before with the original change-resolver. The current design doesn't resolve changes when the symlink is to the containing directory rather then to the file itself. Fix shouldn't take too long but not easy also. Should we give this higher priority? > OST network-suite-4.2 does not run in check-patch > ------------------------------------------------- > > Key: OVIRT-2200 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eitan Raviv > Assignee: infra > > Following my conversation with Barak, we found that when a patch is > pushed to OST/network-suite-master, there are tests results only for > network-suite-master on check-patch job, although it is expected that > network-suite-4.2 would be run as well. > See for example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ > Can you guys please fix? > Thanks > Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch

by Eitan Raviv (oVirt JIRA)

Eitan Raviv created OVIRT-2200: ---------------------------------- Summary: OST network-suite-4.2 does not run in check-patch Key: OVIRT-2200 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2200 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Eitan Raviv Assignee: infra Following my conversation with Barak, we found that when a patch is pushed to OST/network-suite-master, there are tests results only for network-suite-master on check-patch job, although it is expected that network-suite-4.2 would be run as well. See for example: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1208/ https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1173/ Can you guys please fix? Thanks Eitan -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2199: ---------------------------------- Labels: jenkins standard-ci stdci-summary (was: ) > Set content security policy at Jenkins startup > ---------------------------------------------- > > Key: OVIRT-2199 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, standard-ci, stdci-summary > > STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. > The required policy is: > {code:java} > sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; > {code} > Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2199: ------------------------------------- Summary: Set content security policy at Jenkins startup Key: OVIRT-2199 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. The required policy is: {code:java} sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; {code} Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2199: ---------------------------------- Epic Link: OVIRT-403 > Set content security policy at Jenkins startup > ---------------------------------------------- > > Key: OVIRT-2199 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2199 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > STDCI summary requires some content security policy to be set so that Jenkins won't add blocking headers to the summary HTML. > The required policy is: > {code:java} > sandbox allow-scripts; default-src 'self' https://cdnjs.cloudflare.com; img-src 'self'; style-src 'self' https://cdnjs.cloudflare.com; > {code} > Documentation can be found [here|https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

7 years

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1578

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1578/dis...> ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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 6953f4671b4f06efddbd388f2ec1ea81f5ba746d (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6953f4671b4f06efddbd388f2ec1ea81f5ba746d Commit message: "add ovirt-appliance to standard pipelines" > git rev-list --no-walk 6953f4671b4f06efddbd388f2ec1ea81f5ba746d # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins1422341312358250813.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-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 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

7 years

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018