- Infra - oVirt List Archives

[JIRA] (OVIRT-2200) OST network-suite-4.2 does not run in check-patch
by Eitan Raviv (oVirt JIRA) 14 Jun '18

14 Jun '18

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)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

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)

1 0

[JIRA] (OVIRT-2199) Set content security policy at Jenkins startup
by Daniel Belenky (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2199?page=com.atlassian.jira.… ] 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)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1578
by jenkins＠jenkins.phx.ovirt.org 14 Jun '18

14 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1578/displ…> ------------------------------------------ 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

1 1

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2001: ------------------------------------- Add HOWTO run STDCI V2 jobs manually with the 'standard-manual-runner' job. > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2001: ------------------------------------- Issue when 'git describe' returns the wrong tag when running from jenkins. This is because jenkins adds its own tag after cloning the source and the way around it is to use the '--match' option for git describe. > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92236, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 92236,1 (ovirt-engine-nodejs-modules) 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/92236/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8204/

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
by Barak Korren (oVirt JIRA) 14 Jun '18

14 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Summary: Create FAQ/Knowledge Base/HOWTO pages for STDCI (was: Create FAQ/Knowledge Base for STDCI) > Create FAQ/Knowledge Base/HOWTO pages for STDCI > ----------------------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 01a6c0f (ovirt-ansible-v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jun '18

14 Jun '18

Change 01a6c0f (ovirt-ansible-v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/01a6c0f54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2398/

1 0