[JIRA] (OVIRT-1831) Make `global-setup.sh` check if packages are installed before trying to install them
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1831?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1831:
--------------------------------
Component/s: (was: oVirt CI)
Jenkins Slaves
> Make `global-setup.sh` check if packages are installed before trying to install them
> ------------------------------------------------------------------------------------
>
> Key: OVIRT-1831
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1831
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Slaves
> Reporter: Barak Korren
> Assignee: infra
>
> The way '{{global-setup.sh}}' works currently is that it tries to install all the packages it needs in a single yum command and then runs in a loop and checks if the packages were installed properly.
> If the packages are already installed this takes a negligible amount of time on CentOS slaves, but on Fedora it seems to take much longer and as much as 2 minutes.
> We should try to make '{{global-setup.sh}}' faster by making it not try to install packages before checking if they are there, but instead check first and only try to install the missing ones.
> Note that if we'll install multiple packages in a single command, we'll still need to verify they were properly installed after the yum/dnf command finishes.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
6 years, 9 months
[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Daniel Belenky (oVirt JIRA)
Daniel Belenky created OVIRT-1836:
-------------------------------------
Summary: Optimize options normalization methods in stdci_dsl
Key: OVIRT-1836
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Daniel Belenky
Assignee: infra
Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner.
We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away.
Since runners and pipelines care about different sets of options, we need to split the options handling functions.
This will enable us to compose much more efficient pipelines in the API.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
6 years, 9 months
[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Daniel Belenky (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1515571288-12694-334
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jir... ]
Daniel Belenky updated OVIRT-1836:
----------------------------------
Epic Link: OVIRT-400
> Optimize options normalization methods in stdci_dsl
> ---------------------------------------------------
>
> Key: OVIRT-1836
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Daniel Belenky
> Assignee: infra
>
> Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner.
> We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away.
> Since runners and pipelines care about different sets of options, we need to split the options handling functions.
> This will enable us to compose much more efficient pipelines in the API.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
------------=_1515571288-12694-334
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jir... ]</pre>
<h3>Daniel Belenky updated OVIRT-1836:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Optimize options normalization methods in stdci_dsl</h3>
<pre> Key: OVIRT-1836
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Daniel Belenky
Assignee: infra</pre>
<p>Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. Since runners and pipelines care about different sets of options, we need to split the options handling functions. This will enable us to compose much more efficient pipelines in the API.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1515571288-12694-334--
6 years, 9 months
[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1835:
--------------------------------
Component/s: (was: oVirt CI)
Jenkins Slaves
> Create an automated update mechanism for slaves
> -----------------------------------------------
>
> Key: OVIRT-1835
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins Slaves
> Reporter: Barak Korren
> Assignee: infra
> Labels: slaves
>
> While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.
> Some things we'd like such a mechanism to provide:
> * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed).
> * Test updated slaves before putting them back to production use
> * Allow rolling back failed updates
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
6 years, 9 months
[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1515569110-24537-319
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1835:
-----------------------------------
Summary: Create an automated update mechanism for slaves
Key: OVIRT-1835
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.
Some things we'd like such a mechanism to provide:
* Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed).
* Test updated slaves before putting them back to production use
* Allow rolling back failed updates
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
------------=_1515569110-24537-319
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1835:</h3>
<pre> Summary: Create an automated update mechanism for slaves
Key: OVIRT-1835
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra</pre>
<p>While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.</p>
<p>Some things we'd like such a mechanism to provide:</p>
<ul><li><p>Require a minimal amount of manual work (Best case scenario – nothing more then merging a repository update patch would be needed).</p></li>
<li><p>Test updated slaves before putting them back to production use</p></li>
<li><p>Allow rolling back failed updates</p></li></ul>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1515569110-24537-319--
6 years, 9 months
[JIRA] (OVIRT-1835) Create an automated update mechanism for slaves
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1835?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1835:
--------------------------------
Epic Link: OVIRT-403
> Create an automated update mechanism for slaves
> -----------------------------------------------
>
> Key: OVIRT-1835
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1835
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: oVirt CI
> Reporter: Barak Korren
> Assignee: infra
> Labels: slaves
>
> While we already have an automated mechanism for controlling the YUM/DNF repo configuration on slaves, and we also already have a way to install or update components that are critical to the CI system (Both are provided by '{{global-setup.sh}}'), we're lacking a mechanism that can apply general system updates, and more importantly, kernel updates to slaves.
> Some things we'd like such a mechanism to provide:
> * Require a minimal amount of manual work (Best case scenario - nothing more then merging a repository update patch would be needed).
> * Test updated slaves before putting them back to production use
> * Allow rolling back failed updates
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
6 years, 9 months
Planned restart of production services
by Evgheni Dereveanchin
Hi everyone,
I will be restarting several production systems within the following hour
to apply security updates.
The following services may be unreachable for some period of time:
- resources.ovirt.org - package repositories
- gerrit.ovirt.org - code review
- jenkins.ovirt.org - CI master
It will not be possible to submit/review patches, clone repositories or run
CI jobs during this period. Package repositories will also be unreachable
for a short period of time.
I will announce you once the maintenance is complete.
--
Regards,
Evgheni Dereveanchin
6 years, 9 months
[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Gal Ben Haim (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jir... ]
Gal Ben Haim commented on OVIRT-1834:
-------------------------------------
The issue was solved, and we are working on a 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#100075)
6 years, 9 months