[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because
ovirt-imageio-common is not installed
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1873:
----------------------------------
I think it was agreed to drop fcraw support from CI due to its instability, any need for this ticket or we can close it?
> Vdsm fcraw builds fail because ovirt-imageio-common is not installed
> --------------------------------------------------------------------
>
> Key: OVIRT-1873
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> We require the package:
> $ grep ovirt-imageio-common automation/check-patch.packages.fcraw
> ovirt-imageio-common
> Here are few failing builds, we have more:
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/cons...
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/cons...
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/cons...
> *00:03:25.311* =================================== FAILURES
> ===================================*00:03:25.311*
> _________________________ test_import[vdsm.kvm2ovirt]
> __________________________*00:03:25.312* *00:03:25.312* name =
> 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312*
> @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def
> test_import(name):*00:03:25.313* try:*00:03:25.313* >
> importlib.import_module(name)*00:03:25.313* *00:03:25.313*
> check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314*
> /usr/lib64/python2.7/importlib/__init__.py:37: in
> import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ *00:03:25.315* *00:03:25.315* from __future__ import
> absolute_import*00:03:25.315* *00:03:25.315* import
> argparse*00:03:25.315* from contextlib import
> contextmanager*00:03:25.315* import itertools*00:03:25.315*
> import sys*00:03:25.316* import threading*00:03:25.316*
> *00:03:25.316* > from ovirt_imageio_common import
> directio*00:03:25.316* E ImportError: No module named
> ovirt_imageio_common*00:03:25.316* *00:03:25.316*
> ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1
> failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ==========
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-1834:
----------------------------------
[~gbenhaim(a)redhat.com] is there a different card for tracking the proposed long-term solution?
> Jenkins failure - perhaps bad permissions
> -----------------------------------------
>
> Key: OVIRT-1834
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tes...
> *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01*
> hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at
> hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at
> hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01*
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at
> org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01*
> at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01*
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01*
> at hudson.model.Run.execute(Run.java:1724)*10:53:01* at
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at
> hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01*
> at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by:
> hudson.plugins.git.GitException: Command "git clean -fdx" returned
> status code 1:*10:53:01* stdout: Removing
> basic-suite-master/LagoInitFile*10:53:01* Removing
> basic-suite-master/extra_sources*10:53:01* Removing
> basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing
> basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing
> basic-suite-master/test_utils/constants.pyc*10:53:01* Removing
> basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing
> exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01*
> Removing mock_script_sid.x4jv1R*10:53:01* Removing
> mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning:
> failed to remove .pki/*10:53:01* warning: failed to remove
> deployment-basic-suite-master/default/uuid*10:53:01* warning: failed
> to remove deployment-basic-suite-master/default/id_rsa
> ...
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for
repo: base/7/x86_64
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-2131:
----------------------------------
Maybe its time to close again the external repos, i.e - revert https://gerrit.ovirt.org/#/c/91150/.
but needs to wait for https://gerrit.ovirt.org/#/c/91647/ first.
> Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
> --------------------------------------------------------------
>
> Key: OVIRT-2131
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: cq-issue-traking, ost_failures, ost_infra
>
> test failed. looking into it
> '11:12:55 [basic-suit]
> 11:12:55 [basic-suit] - STDERR
> 11:12:55 [basic-suit] + HUGEPAGES=3
> 11:12:55 [basic-suit] + yum update -y iptables
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] One of the configured repositories failed (Unknown),
> 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only
> 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem.
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
> 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer
> 11:12:55 [basic-suit] distribution release than is supported by the repository (and the
> 11:12:55 [basic-suit] packages for the previous distribution release still work).
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled
> 11:12:55 [basic-suit] yum --disablerepo=<repoid> ...
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum
> 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it
> 11:12:55 [basic-suit] again or use --enablerepo for temporary usage:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] yum-config-manager --disable <repoid>
> 11:12:55 [basic-suit] or
> 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid>
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable.
> 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands,
> 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much
> 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice
> 11:12:55 [basic-suit] compromise:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30)
> 11:12:55 [basic-suit] Error while running thread
> 11:12:55 [basic-suit] Traceback (most recent call last):
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
> 11:12:55 [basic-suit] queue.put({'return': func()})
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
> 11:12:55 [basic-suit] host.name(),
> 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
> 11:12:55 [basic-suit] Error while running thread
> 11:12:55 [basic-suit] Traceback (most recent call last):
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
> 11:12:55 [basic-suit] queue.put({'return': func()})
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
> 11:12:55 [basic-suit] host.name(),
> 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
> 11:12:57 [upgrade-from-release-suit] Finish: creating root cache
> 11:12:57 [upgrade-from-release-suit] Finish: chroot init
> 11:12:57 [upgrade-from-release-suit] INFO: Installed packages:
> 11:12:57 [upgrade-from-release-suit] Finish: run
> 11:12:57 [upgrade-from-release-suit] Init took 208 seconds
> 11:12:57 [upgrade-from-release-suit] ============================'
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for
repo: base/7/x86_64
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jir... ]
Dafna Ron updated OVIRT-2131:
-----------------------------
Summary: Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 (was: Cannot find a valid baseurl for repo: base/7/x86_64)
> Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
> --------------------------------------------------------------
>
> Key: OVIRT-2131
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: cq-issue-traking, ost_failures, ost_infra
>
> test failed. looking into it
> '11:12:55 [basic-suit]
> 11:12:55 [basic-suit] - STDERR
> 11:12:55 [basic-suit] + HUGEPAGES=3
> 11:12:55 [basic-suit] + yum update -y iptables
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] One of the configured repositories failed (Unknown),
> 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only
> 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem.
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
> 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer
> 11:12:55 [basic-suit] distribution release than is supported by the repository (and the
> 11:12:55 [basic-suit] packages for the previous distribution release still work).
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled
> 11:12:55 [basic-suit] yum --disablerepo=<repoid> ...
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum
> 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it
> 11:12:55 [basic-suit] again or use --enablerepo for temporary usage:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] yum-config-manager --disable <repoid>
> 11:12:55 [basic-suit] or
> 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid>
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable.
> 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands,
> 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much
> 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice
> 11:12:55 [basic-suit] compromise:
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64
> 11:12:55 [basic-suit]
> 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30)
> 11:12:55 [basic-suit] Error while running thread
> 11:12:55 [basic-suit] Traceback (most recent call last):
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
> 11:12:55 [basic-suit] queue.put({'return': func()})
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
> 11:12:55 [basic-suit] host.name(),
> 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
> 11:12:55 [basic-suit] Error while running thread
> 11:12:55 [basic-suit] Traceback (most recent call last):
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
> 11:12:55 [basic-suit] queue.put({'return': func()})
> 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
> 11:12:55 [basic-suit] host.name(),
> 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
> 11:12:57 [upgrade-from-release-suit] Finish: creating root cache
> 11:12:57 [upgrade-from-release-suit] Finish: chroot init
> 11:12:57 [upgrade-from-release-suit] INFO: Installed packages:
> 11:12:57 [upgrade-from-release-suit] Finish: run
> 11:12:57 [upgrade-from-release-suit] Init took 208 seconds
> 11:12:57 [upgrade-from-release-suit] ============================'
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by Gal Ben Haim (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jir... ]
Gal Ben Haim commented on OVIRT-2108:
-------------------------------------
As stated, it will require building lago for ppc64.
It's difficult to evaluate the amount of time that is needed for this task,
but for sure it's not something immediate.
> Enable ovirt-system-tests for ppc64le
> -------------------------------------
>
> Key: OVIRT-2108
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: OST
> Reporter: sbonazzo
> Assignee: infra
>
> We're using ppc64le hosts in oVirt CI infrastructure under oVirt management.
> It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-2131) Cannot find a valid baseurl for repo:
base/7/x86_64
by Dafna Ron (oVirt JIRA)
Dafna Ron created OVIRT-2131:
--------------------------------
Summary: Cannot find a valid baseurl for repo: base/7/x86_64
Key: OVIRT-2131
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra
test failed. looking into it
'11:12:55 [basic-suit]
11:12:55 [basic-suit] - STDERR
11:12:55 [basic-suit] + HUGEPAGES=3
11:12:55 [basic-suit] + yum update -y iptables
11:12:55 [basic-suit]
11:12:55 [basic-suit]
11:12:55 [basic-suit] One of the configured repositories failed (Unknown),
11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only
11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this:
11:12:55 [basic-suit]
11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem.
11:12:55 [basic-suit]
11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer
11:12:55 [basic-suit] distribution release than is supported by the repository (and the
11:12:55 [basic-suit] packages for the previous distribution release still work).
11:12:55 [basic-suit]
11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled
11:12:55 [basic-suit] yum --disablerepo=<repoid> ...
11:12:55 [basic-suit]
11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum
11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it
11:12:55 [basic-suit] again or use --enablerepo for temporary usage:
11:12:55 [basic-suit]
11:12:55 [basic-suit] yum-config-manager --disable <repoid>
11:12:55 [basic-suit] or
11:12:55 [basic-suit] subscription-manager repos --disable=<repoid>
11:12:55 [basic-suit]
11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable.
11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands,
11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much
11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice
11:12:55 [basic-suit] compromise:
11:12:55 [basic-suit]
11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
11:12:55 [basic-suit]
11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64
11:12:55 [basic-suit]
11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30)
11:12:55 [basic-suit] Error while running thread
11:12:55 [basic-suit] Traceback (most recent call last):
11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
11:12:55 [basic-suit] queue.put({'return': func()})
11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
11:12:55 [basic-suit] host.name(),
11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
11:12:55 [basic-suit] Error while running thread
11:12:55 [basic-suit] Traceback (most recent call last):
11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
11:12:55 [basic-suit] queue.put({'return': func()})
11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host
11:12:55 [basic-suit] host.name(),
11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1
11:12:57 [upgrade-from-release-suit] Finish: creating root cache
11:12:57 [upgrade-from-release-suit] Finish: chroot init
11:12:57 [upgrade-from-release-suit] INFO: Installed packages:
11:12:57 [upgrade-from-release-suit] Finish: run
11:12:57 [upgrade-from-release-suit] Init took 208 seconds
11:12:57 [upgrade-from-release-suit] ============================'
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months
[JIRA] (OVIRT-1466) Switch to deploying JJB via PIP
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1466?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1466:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Switch to deploying JJB via PIP
> -------------------------------
>
> Key: OVIRT-1466
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1466
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: JJB
> Reporter: Barak Korren
> Assignee: Barak Korren
> Labels: jjb, standard-ci
>
> Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions.
> Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip.
> We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 7 months