[JIRA] (OVIRT-1763) Increase entropy for hosts

Wednesday, 15 November 2017

This is a multi-part message in MIME format...

------------=_1510753169-31571-405
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jir...
] 

Evgheni Dereveanchin commented on OVIRT-1763:
---------------------------------------------

And I think the difference in speed is caused by this part:

1) successful build 3834 taking 5 minutes to install packages - running in RAM:
02:49:59 [upgrade-from-release-suit] +++ df --output=avail /dev/shm
02:49:59 [upgrade-from-release-suit] +++ sed 1d
02:49:59 [upgrade-from-release-suit] ++ avail_shm=24589620
02:49:59 [upgrade-from-release-suit] ++ [[ 24589620 -ge 15000000 ]]
02:49:59 [upgrade-from-release-suit] ++ mkdir -p /dev/shm/ost
02:49:59 [upgrade-from-release-suit] ++ echo
/dev/shm/ost/deployment-upgrade-from-release-suite-master
02:49:59 [upgrade-from-release-suit] +
run_path=/dev/shm/ost/deployment-upgrade-from-release-suite-master

2) timed out build 3795 taking 15 minutes to install packages - running on disk:
15:29:24 [upgrade-from-release-suit] ++ local avail_shm
15:29:24 [upgrade-from-release-suit] +++ df --output=avail /dev/shm
15:29:24 [upgrade-from-release-suit] +++ sed 1d
15:29:24 [upgrade-from-release-suit] ++ avail_shm=14540900
15:29:24 [upgrade-from-release-suit] ++ [[ 14540900 -ge 15000000 ]]
15:29:24 [upgrade-from-release-suit] ++ echo
/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master
15:29:24 [upgrade-from-release-suit] +
run_path=/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master

Logging into the node where build 3795 was running I see 24GB free on the RAM drive when
no jobs are running. Not really sure if anything should be on the RAM drive by the time
that check is made, based on this we can take action and either clean it up, change the
check or increase the timeout. [~bkorren(a)redhat.com], do you know any details about RAM
drive specifics for OST?

...
 Increase entropy for hosts
 --------------------------

                 Key: OVIRT-1763
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763
             Project: oVirt - virtualization made easy
          Issue Type: Bug
            Reporter: Dafna Ron
            Assignee: infra

 we had a failure in ost that was really hard to debug:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/
 There are no failures in the logs and the test itself was terminated by a timeout.
 It took the vms a long time to download packages and install and didi seems to think that
this is due to limited entropy on the physical host. 
 we need to review this issue and increase the entropy on the hosts.  

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100071)

------------=_1510753169-31571-405
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jir...
]</pre>
<h3>Evgheni Dereveanchin commented on OVIRT-1763:</h3>
<p>And I think the difference in speed is caused by this part:</p>
<p>1) successful build 3834 taking 5 minutes to install packages &ndash; running
in RAM: 02:49:59 [upgrade-from-release-suit] +++ df --output=avail /dev/shm 02:49:59
[upgrade-from-release-suit] +++ sed 1d 02:49:59 [upgrade-from-release-suit] ++
avail_shm=24589620 02:49:59 [upgrade-from-release-suit] ++ [[ 24589620 -ge 15000000 ]]
02:49:59 [upgrade-from-release-suit] ++ mkdir -p /dev/shm/ost 02:49:59
[upgrade-from-release-suit] ++ echo
/dev/shm/ost/deployment-upgrade-from-release-suite-master 02:49:59
[upgrade-from-release-suit] +
run_path=/dev/shm/ost/deployment-upgrade-from-release-suite-master</p>
<p>2) timed out build 3795 taking 15 minutes to install packages &ndash; running
on disk: 15:29:24 [upgrade-from-release-suit] ++ local avail_shm 15:29:24
[upgrade-from-release-suit] +++ df --output=avail /dev/shm 15:29:24
[upgrade-from-release-suit] +++ sed 1d 15:29:24 [upgrade-from-release-suit] ++
avail_shm=14540900 15:29:24 [upgrade-from-release-suit] ++ [[ 14540900 -ge 15000000 ]]
15:29:24 [upgrade-from-release-suit] ++ echo
/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master
15:29:24 [upgrade-from-release-suit] +
run_path=/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master</p>
<p>Logging into the node where build 3795 was running I see 24GB free on the RAM
drive when no jobs are running. Not really sure if anything should be on the RAM drive by
the time that check is made, based on this we can take action and either clean it up,
change the check or increase the timeout. [~bkorren(a)redhat.com], do you know any details
about RAM drive specifics for OST?</p>
<blockquote><h3>Increase entropy for hosts</h3>
<pre>     Key: OVIRT-1763
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763
 Project: oVirt - virtualization made easy
         Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra</pre>
<p>we had a failure in ost that was really hard to debug: <a
href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/...
There are no failures in the logs and the test itself was terminated by a timeout. It took
the vms a long time to download packages and install and didi seems to think that this is
due to limited entropy on the physical host. we need to review this issue and increase the
entropy on the hosts.</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100071)</p>

------------=_1510753169-31571-405--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011